Bots and Simulations > Tips and Tricks

how to make a bot go at the simulations max velocity all the time!

(1/3) > >>

fulizer:
with varing max velocity is a problem if you go faster than it you waste energy, if you go slower than it you are inferior to the bots that go fatser than you.
so all you have to to is add this to your dna
[div class=\'codetop\']CODE[div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']*.maxvel .up store
making your bot go at the top speed without wasitng any energy and it gives your bot a large advantage over those who dont
I do not know if this has been done but some newer people (even newer than me) can use this to a good effect.

EricL:
The assumption that storing values above *.maxvel in a movement sysvar wastes nrg is incorrect.  It is a general rule in the simulator that bots only get charged for the resultant action, not the action attempted.  The simualtor code limits the magnitude of the vector sum of the bot attempted accelerations and thus the action portion of the cost equation to the max velocity (which then gets multiplied by the movement cost and the cost multiplier to determine the actual cost).  Bottom line, bots storing huge values in movement sysvars are not charged more than that needed to accelerate to maxvel.

I should also point out here that there is a hard limit on voluntary movement costs, restricting them to values between -100 and 100 (costs can be negative if the cost multiplier is negative).  This limit is very old code.  It predates the cost multiplier.  No matter what the result of the cost calculation above, no matter how high the cost multipler or the user-specified movement cost, the actual cost applied is capped at 100.  

I would very much like to remove this restriction if there are no objections.   It is one of the few places where costs have a hard cap.  It is also one of the few places where the will of the cost multiplier is overridden.

Numsgil:
It was restricted to limit a killer info shot attack that caused the enemy to fly backwards at full speed (this was before my time, I think Carlo added it actually).  I think 100 is a bit low in the modern program, and the charge-for-the-action-not-the-attempt fixes the original issue with that the cap was meant to fix.  So yeah, removing it is fine.

fulizer:
oh fair enough
but a bot like this still gets the advantage over those that dont

EricL:

--- Quote from: fulizer ---but a bot like this still gets the advantage over those that dont
--- End quote ---
That's a pretty niave statement, like saying "bigger is always better".  Always moving at maxvel is only advantageous if it's advantageous.  It depends entirely on environmental conditions.

Navigation

[0] Message Index

[#] Next page

Go to full version