did you yourself do it voo or you put zuckenberg's doll to code it?

wd!

when you are done voodoo let me know so we can set it up

That was quick, nice job

zuckenberg ? is it that guy robbing time to billions of people to useless status and wall maintenance ?
no. I got an army of nerds enslaved by my dolls so i can pretend I've coded it!

to bigd, that's not that quick as it's not cooked yet

and i made no progress yesterday as i spend the couple of hours i manage to dedicate to this refactoring the code.
that was an ugly mess so i wanted to clean it and minimise its footprint.
hmm does this sentense made sense to anyone?

anyway, i hope we'll have a server ready for this week-end.

sidenote to myself: stop addind a "make it a mess, then" in front of the famous "make it right, then make it fast".
so you'll save time for your wife...


edit:
-mb, you might start setting up an empha sumo bar like server and adjust settings already, then you'll just have to upgrade binary and add the few required settings... there's to adjust score_limit + scoring which leads me to a second point.
-what should be scoring policy for this server?
also you might keep a sumo somewhere in the server name...

If we keep normal scoring for sumo, 300 points is too much for a kill. My opinion is to remove any other scoring. You only get points for assassinations.

I think it's risky to lower the number if somebody else kills your target, because this might be beyond your control -> your target might be a noob or someone bad intented to mess you up

I suggest the following scoring system:
1. basescore: 100
2. modifiers:
a. 30 bonus for every next target (eg.: 160 for the third target) during the round.
b. +/- 10 bonus according to target rank relative to your rank. Eg.: I'm #1, target is #5, we both have the other one as a target; he would be my third kill, I would be his first kill. If I kill him I get a 100 + 2 * 30 - 40 = 120 points, if he kills me he gets 100 + 40 = 140 points.
The rank would probably be the rank from the current match or maybe from a ladder (that would be more complex).
3. limitscore: 1000-1500.
4. maybe another 100 bonus for winning the round.

I also suggest something for the target picking system (if it's not too hard to implement ): the higher your rank, the more players get you as target. Eg.: 8 players in the match, #1 rank is targeted by 3 players, #2 by 2 players, #3-5 by 1 player. This could be a competitive setup for tournaments .

the score is a normal score for sumo, and the killing targets are a bonus of 300 points increasing in 100 if you kill them in a row. There won't be score_limit and the rounds will be 10.

here is the post

Leaving players are not handled yet

Testing required

I've edited settings names to fit changes:

Regular sumo scoring really shouldn't be included, or it should be minimized more, because otherwise, regular kills and zone points can still make a huge difference. The best "Assassin" won't necessarily be the winner.

So if someone admin kills his target does he get extra points?

no i am joking

WD VOO!!!

Edit: 3

You have to kill 10 players to get the same score as killing your target. Believe me, if ur a good assassin you win the match.

I don't really like your suggestion emmy, it's way too complicated but we can try both methods. I mean we implement my way first and then we implement yours, and we let people decide.

Maybe it's complicated to code, but not complicated for the player: he only has to know that the more and higher ranked targets he kills, the more points he gets.
It's like saying the current sumo bar zone conquer score is complicated at this moment: you get 7 points, then 8, then 9, then 10, then 12, then 15, then 20, then 30, then 60. But it's actually only one formula, 60 / nr. conquerers.
But I agree, it can be tried later on.

This would be interesting but it means to rank players first and that's actually the trickiest part, not tricky to code but to get something meaningful for a specific game mode ...
Ladders are usually computed from the outside based on ladderlog.txt. This means scoring have to be handle from scripting or there's to provide a rank.txt file to be reloaded each time the ladder is recomputed ...
That's still feasible from scripting as you can set internal scoring to 0 and fully handle tha from the outside based on CYCLE_TARGET_KILLED ladderlog's entry and that would probably be the best way to achieve that.
This piece of code works from within the game and that's really convinient (though I'm still debugging an ugly bug hidden somewhere leading to a crash between rounds. It seems I'm not cleaning things up in the proper order)

Seems I fix this damn bug. MB, that's cooked now, we can setup a server and hopefully, no more hidden bug will crashed it!

gogogogo