Difference between revisions of "Talk:Geomancy/Version History"
(Excellent questions: No, yes, no) |
m (wording fix) |
||
Line 5: | Line 5: | ||
Just interested, did you add the 'snapping' to your precise prediction? And to clarify, you <i>reach</i> the 8,4 or 0 2 ticks before they fire? Have you made a test bot that prints out the enemy velocity that it uses to aim with, ie. the tick before the bot fires, to make sure it lines up correctly? [[Wave Surfing]] is difficult to wrap your mind around, I'm just going over the mistakes I think I'd be most likely to make =) --[[User:Skilgannon|Skilgannon]] 21:33, 12 July 2009 (UTC) | Just interested, did you add the 'snapping' to your precise prediction? And to clarify, you <i>reach</i> the 8,4 or 0 2 ticks before they fire? Have you made a test bot that prints out the enemy velocity that it uses to aim with, ie. the tick before the bot fires, to make sure it lines up correctly? [[Wave Surfing]] is difficult to wrap your mind around, I'm just going over the mistakes I think I'd be most likely to make =) --[[User:Skilgannon|Skilgannon]] 21:33, 12 July 2009 (UTC) | ||
− | I didn't add the snapping to my precise prediction yet, but watching the factors as they are surfed, the impact seems to be minimal. I reach the 8, 4, or 0 | + | I didn't add the snapping to my precise prediction yet, but watching the factors as they are surfed, the impact seems to be minimal. I reach the 8, 4, or 0 mark two ticks before they fire, and maintain it the turn before they fire. I tested the timing with the new method AdvancedRobot.setDebugVariable, and confirmed that it was lining up correctly. I haven't set up a grapher yet to see what it makes my profile look like, but that's another way I could confirm that it was doing its job. -- [[User:Synapse|<font style="font-size:0.8em;font-variant:small-caps;">Synapse</font>]] 21:40, 12 July 2009 (UTC) |
Revision as of 22:43, 12 July 2009
Just keep in mind that their movement is going to be delayed by 2 ticks, once for them to read yours, then change, and the next for you to read their changes. But so far it sounds good =) --Skilgannon 16:35, 5 July 2009 (UTC)
I hadn't thought of that, but of course you're right. Building that delay into the design will allow me to use a tighter tolerance on detection. -- Synapse 19:45, 5 July 2009 (UTC)
Just interested, did you add the 'snapping' to your precise prediction? And to clarify, you reach the 8,4 or 0 2 ticks before they fire? Have you made a test bot that prints out the enemy velocity that it uses to aim with, ie. the tick before the bot fires, to make sure it lines up correctly? Wave Surfing is difficult to wrap your mind around, I'm just going over the mistakes I think I'd be most likely to make =) --Skilgannon 21:33, 12 July 2009 (UTC)
I didn't add the snapping to my precise prediction yet, but watching the factors as they are surfed, the impact seems to be minimal. I reach the 8, 4, or 0 mark two ticks before they fire, and maintain it the turn before they fire. I tested the timing with the new method AdvancedRobot.setDebugVariable, and confirmed that it was lining up correctly. I haven't set up a grapher yet to see what it makes my profile look like, but that's another way I could confirm that it was doing its job. -- Synapse 21:40, 12 July 2009 (UTC)