Crazy Ideas

Fragment of a discussion from Talk:Yatagan/Source
← Thread:Talk:Yatagan/Source/Crazy Ideas/reply (15)

Jump to navigation Jump to search

Ok, that doesn't work because the absoluteBearing has been fully initialised and doesn't just use the e.getBearingRadians() value, so it goes in circles. Oh well, I was hoping for some more codesize there!

Try it again with a pair of parentheses around e.bearing + heading. That should fully initialize absolute bearing. If it doesn't, then there must be something else going on.

What were you planning to do with the extra space?

Nope, the problem is in the distancing, see the change I made that fixes the behaviour.

I'm not sure what to do with the space, but I'm sure we can think of something. Perhaps better bullet power selection for rambots or something like that.

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.

I think I figured out a way to get those bytes back--at a loss of targeting accuracy.  We'll see if it's worth it.

I highly doubt you'd be able to fit anti-ram in 3-4 bytes.  But, it seems that almost every time I say that, you prove me wrong.  :)

Return to Thread:Talk:Yatagan/Source/Crazy Ideas/reply (18).

Ooooh, that is ugly ugly ugly. But this is nano, the king of ugly, so it would only be fitting if the king was ugly too. I'm not sure what we'd gain from rambots would make up for this, but it's worth a try I guess.

I'm not really worried about rambots; Yatagan already does fine against them. Let's just enter this version as it is, and see if the performance loss is substantial.

I'm not sure why, but it stayed at 249 bytes.

Retrieved from "http://robowiki.net/wiki/Thread:Talk:Yatagan/Source/Crazy_Ideas/reply_(15)#Crazy_Ideas_3151"