In the first reply in Brevis I included some hints and code that should make it a lot easyer to prevent overlaping actions.
It's hard to just start off writing everything on one line, if you just write a bot with normal conditions you can gradualy make sure all conditions are mututaly exclusive. (You can also just use Sanger I think, but the examples I saw for that had a strange syntax, maybe I didn't stare at it hard enough)
Either way if you try to make mutualy exclusive conditions it can get hard to find your way when you reach a certain size, so if you insert this code before your bot :
cond
*.actions 1 >
start
100 *.actions add inc 'Keeps track of how many times it has happened.
*121 122 *.actions 10 mult add store
'Some variables to help understand why genes are being triggered at the same time
*.actions 111 store
*.robage 4 mod 112 store
*.memval 113 store
*.eye5 114 store
1 142 store
stop
cond
*142 0 >
start
1 .repro store 'Use this if you want to hunt for rare bugs.
stop
cond
*.actions 0 !=
start
0 .actions store
stop
And insert these 3 lines in all your other genes.
cond
'Your condition
start
'Your action
*121 122 *.actions 10 mult add store
*.thisgene 121 store
.actions inc
stop
Then you'll be able to see what genes where triggered in the memmory locations above, and you can choose to impose a slow repro death to any bot that peforms 2 actions at the same time. This makes it a lot easyer to debug, ig you have a ton of overlaps you can just disable the repro death thing, if you have fe it makes it esy to see what bots are breaking the rules.
Then once you have everything working and the repro thing never occurs you can build the conditions into the action taken, without removing the conditions.
This way you're also making sure you didn't make any type o's or missed a mult or and add or something, in your SG'fied conditions.
And once you have all that in place you should be able to safely cut and paste everything into one store. (I also did that over several steps, things can go wrong for no apparent reason at times)
Either way this should be very usefull for making large SS bots without Sanger. I know I would never have gotten brevis to work without the debug code and constant testing for every step I took. But then again I'm also kinda sloppy when coding, so maybe I need mre help than others