MB, you need to update the binary with last things I've committed to sty+ct and had the following settings :
CYCLE_TARGET_MODE 1
CYCLE_TARGET_SCORE 300
CYCLE_TARGET_SCORE_DEPLETE -100
CYCLE_TARGET_TIMEOUT .0
CYCLE_TARGET_MAX 999

These are zappy's settings.

When will you get it done MB ? We is waiting ^^.

more bugfixes right out of bed (ouch!) after kyle has setup a server and report me crashes. That's actually not the best moment for me to get things fixed the right way but well, let see ...
anyway, 1 new setting too:
CYCLE_TARGET_START_TIME <float>
-.5 is the default which means targets are first assigned half sec before start...

kyle pointed an issue with standard sumo map (with pod) so i'll add an extra setting to handle that too. Probably just setting a max distance to find a target which will allow to handle pod while it's easy and straight forward to implement.

last point, that might be useful to be able to desactivate targets once there's too few cycle alive, to avoid the last head to head for example Of course, that will be an extra setting too.

I hope to test these things soon

well while me and kyle were setting up the server i used my sumo bar map config file with it would that have caused the bug ?

no, that was really in the target management code. nothing to see with the map...

server is up making debug recordings, so if it crashes please let me know

yeah voodoo, when the last 2 are alive, they shouldn't be assigned each other as targets. It has no sense.

List of stuff that needs to be fixed:

limit_score: set it to the max you can
score_suicide: i've thinking about it and some people might suicide in purpose not to let you get the points. So i'd set it to -300 so nobody does it
map: the current map is a normal sumo one, it needs to be sumo bar.
server name: make it a lil more coloured and remove the (kvm) that's just ugly.
server crashes: no idea why but it also needs to be fixed, but youa re working on it right voody?


I think that's it.

yeah, I'm still chasing bugs there. That's not a really complicated piece of code but if you look at it, you'll see it's not really short ...
I've committed last required options.

Please include TESTING or TEST or SERVER CAN CRASH within the name to warn players. Also what's the name again ? I can't find it ? Is it on MB's server or Kyle's one ?

Its called Crazy Tronners Assassin Club

Its located in my servers

hmmm, it keep crashing outside of target code, in part that are related to memory debugging code.

Or I really messed up thing and I corrupt memory within target code.
Or there's some hidden issues out there...
That will be tricky.

please try to go there and crash the server so I can investigate

MB you can try to switch to empha sumo settings...

What I've experienced yesterday was I think 15 normal rounds, everything worked fine. Then there was one round, my target got killed. I didn't recieve a new target. When that round got reset, the server crashed. Maybe there's some target assignment bug?

That bug was fixed. The last one was trickier. I've use a workaround and it seems to work. Testing needed !!!

For the record, that was some weird interaction between armagetron memory management (in debug mode), stl memory management and threading during authentication (specifically when authentication happens while arena was cleaning cycles which typically occurs when a second player with auto login enable join the server, leading to round being stopped and authentication being immediate ...). I'm not sure this bug was there while not in debug mode nor if it was there on every stl implementation, etc. cause I did not face it on my comp. So workaround is fine. So far so good.

I didn't get a second word of that line but still I find it awesome that you take your free time to write this, thanks again voo

Also! Here's a short piece of commands which are still needed.

I might add more if I find something

Pieces needed for what?

Noticed something when playing yesterday. Sometimes the targets would be A's target is B and B''s target is A. C's target is D and D's target is C. So when A killed B, A was left without a target. Wouldn't it be better if the targets completed a loop? A -> B -> C -> D - > A.