Difference between revisions of "Inc/dec"
(→Post 2.4) |
m (Fixed typos) |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | |||
These operators, inc(increase) and dec(decrease), are some of the most useful but are infrequently used. They work by either decreasing or increasing a memory location by 1. | These operators, inc(increase) and dec(decrease), are some of the most useful but are infrequently used. They work by either decreasing or increasing a memory location by 1. | ||
− | == Example == | + | ==[[Operators]]:== |
+ | {{Store Commands}} | ||
+ | |||
+ | === Example:=== | ||
50 inc | 50 inc | ||
Line 22: | Line 24: | ||
stop | stop | ||
− | It has also been used | + | It has also been used effectively as an inter-gene signal and method to "freeze" values. |
==Pre 2.4== | ==Pre 2.4== | ||
Line 28: | Line 30: | ||
==Post 2.4== | ==Post 2.4== | ||
− | All memory locations can be modified with inc/dec, but inc/dec now cost nrg. Cost is equal to 1/10th of a store command. | + | All memory locations can be modified with inc/dec, but inc/dec now cost nrg. Cost is equal to 1/10th of a store command. Stuff like value freezing will now cost the bots a set amount of nrg per turn. Such "cheating" methods such as for example, increasing repro(300) some fifty times, or constant use of inc/dec, will now cost the bots a reasonable amount of nrg. |
==Value freezing using inc/dec== | ==Value freezing using inc/dec== | ||
− | This technique allows you to "freeze" values or to raise/lower a number to a value and then keep it there. This is best used for when you need a value at a constant number, but without the cost of | + | This technique allows you to "freeze" values or to raise/lower a number to a value and then keep it there. This is best used for when you need a value at a constant number, but without the cost of continuously storing it. |
' Basic method to demonstrate freezing | ' Basic method to demonstrate freezing | ||
Line 49: | Line 51: | ||
stop | stop | ||
− | + | Warning inc/dec now cost nrg limiting the effectiveness of such constant usage. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Latest revision as of 20:43, 14 February 2014
These operators, inc(increase) and dec(decrease), are some of the most useful but are infrequently used. They work by either decreasing or increasing a memory location by 1.
Contents
Operators:
Store Commands:The following commands are not supported in versions earlier 2.46: |
Example:
50 inc
adds 1 to *50. When more are used simultaneously the effects are cumulative.
For Example:
50 dec 50 dec 50 dec
Subtracts 3 from *50. One of the more popular uses of this is for birth tie removal.
cond start .tie *.robage 1000 mult add inc .deltie *.robage 1 sub 1000 mult add inc stop
It has also been used effectively as an inter-gene signal and method to "freeze" values.
Pre 2.4
Not all locations can be handled with them, memlocs 1-8(more?) can not be inc/dec. This is to ensure that the bots are required to expend some energy.
Post 2.4
All memory locations can be modified with inc/dec, but inc/dec now cost nrg. Cost is equal to 1/10th of a store command. Stuff like value freezing will now cost the bots a set amount of nrg per turn. Such "cheating" methods such as for example, increasing repro(300) some fifty times, or constant use of inc/dec, will now cost the bots a reasonable amount of nrg.
Value freezing using inc/dec
This technique allows you to "freeze" values or to raise/lower a number to a value and then keep it there. This is best used for when you need a value at a constant number, but without the cost of continuously storing it.
' Basic method to demonstrate freezing ' Will keep .tieloc at -1 permanently cond start .tieloc *.tieloc dup div mult inc .tieloc dec stop 'More complex method demonstrates freezing 'at a value with .ploc=7 cond start 'When *.ploc = 7 dec by 1 .ploc *.ploc 7 sub 1000 mult add dec .ploc inc stop
Warning inc/dec now cost nrg limiting the effectiveness of such constant usage.