A Few Suggestions

Jump to navigation Jump to search

That is some very good codesize saving advice. This nano was based off a relatively poor performing robot in the first place.

The onBulletHit being wrong is possible, it was just getEnergy last time. However that looked like an error to me, since it was suppose to be detecting enemy energy drops, and I wanted to remove the possibility of

With my compiler, 1/0.0 has the same byte size as Double.POSITIVE_INFINITY.

As for the d0, note my comment "since I use this twice in the following, I am not sure which one is called first, if I figure it out I can shave another byte off". I assume its the most deeply nested one, but I could be wrong.

Chase07:07, 28 April 2013

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

Return to Thread:Talk:ExclusionNano/A Few Suggestions/reply (2).

 

BulletHitEvent.getEnergy() gets the enemy energy AFTER the bullet hits and its energy drops. So I shouldn't need to adjust by the bullet power. Sure I might miss a bullet fire, but at the time I was low on codesize.

But after all the reductions I can actually fit that in.

Chase02:45, 29 April 2013