Code center > Bugs and fixes
Why aren't you using 2.42?
Numsgil:
Yeah, I agree Elite.
Elite:
OK, I've revamped everything. You can get a link to my new FTP from the main page and can link to the sources and previous versions from there.
Numsgil:
I modified it a bit, but it's good.
EricL:
--- Quote from: Elite ---(3) .fixang, .fixlen and .tielen1-3 don't work
Sharing doesn't seem to work either
Here's an example to demstrate bug (3):
I've attached a simple SG batterybot that is supposed to grab a veggy that you put in front of it and drain it's energy using sharing. It doesn't move or fight etc. - all it does is grab veggies that come near to it's eye5, unfix them and put them behind it using fixang.
In practice, in 2.42.2, it grabs the veggie, unfixes it, but can't move it behind itself, change the length of the tie, or share with the veg.
--- End quote ---
I'm digging into this. Here are some questions that would help me better understand how ties are supposed to work.
Q) Should tmemloc and tmemval be reset to zero if the bot attempts to read from a tie and there are either no ties at all or no value specifed in .tienum? 2.4 does this today.
Q) If there is only one tie, should the tref sysvars be automatically populated or should the bot have to set a tienum and explicitly read from the tie before the tref sysvars get populated?
Elite:
--- Quote from: EricL ---Q) Should tmemloc and tmemval be reset to zero if the bot attempts to read from a tie and there are either no ties at all or no value specifed in .tienum? 2.4 does this today.
--- End quote ---
No, I think you should keep .tmemloc set until changed by the bot. That way you don't have to keep setting it if you accidently read from a nonexistant tie. Maybe that's one of the reasons why symbioticus has been playing up in 2.4
--- Quote from: EricL ---Q) If there is only one tie, should the tref sysvars be automatically populated or should the bot have to set a tienum and explicitly read from the tie before the tref sysvars get populated?
--- End quote ---
Yes, populating the trefvars automatically with the first tie formed would be a very, very good idea as you could then use:
cond
*.trefeye *.myeye =
start
*.tiepres .deltie store
stop
With ease Without loosing a cycle storing the tie phase into .readtie
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version