I'm currently collecting some data. If some of you members and minors wouldn't mind helping out, that'd be great.

All's I'm asking is that when the server crashes, jot down in a .txt file the models that were in the server and the player load.

example:
Four Players:
SarkRagnar
SnowRagnar
Ulf
Elder

Just record that from every crash. Don't combine it all, I'll do that on my own. And yes, record your own model.

Thanks in advance guys, I'd really appreciate the help.

i'll also note some interesting extra activity, purely for reference:
such as if there were a lot of entering and leaving...
if there was a lot of spamming...
if it was during heavy ffa or 1v1..
(all subjective, but of interest)

good stuff..


oh btw, if i'm on with someone else, say beforehand so no overlap in recording, hehe

quote:

---

Originally posted by Dante:


oh btw, if i'm on with someone else, say beforehand so no overlap in recording, hehe

---

Good call dante.

just ask, "anyone record that crash?", lol.

this is good, instead of endlessly speculating about player models etc, we're actually going to be more scientific about it..

hey on a related note for unter...
remember minor speculation that the sitebar was stressing things a bit? this seems a good time to see if that's kinda true...note before and after effects of sitebar being implemented?

Dont think its that, didnt happen till after stats were put into the server. Might also be a mix of the sidebar and ranking system put into it who knows it might be a fault with the scripting that you set together for the rune stats so thats a posbility also.

"Beware the leader who bangs the drums of war in order to whip the citizenry into a patriotic fervor, for patriotism is indeed a double-edged sword.

-Julius Caesar

How about the scripting to do the scoreboard in the arena. It updates itself causing the server to think of the calculations and pixel drawing instead of the game at hand.

Midknight

Originally posted by Midknight:
It updates itself causing the server to think of the calculations and pixel drawing instead of the game at hand.

Interesting, Mid; the scoreboard is a so-called “simulated proxy”, however; which means the clients take care of it.  Except for the one-off initialization, the server is score-board dumb.

With the new set-up we'll be able to access a gold mine of previously inaccessible information: the server crash logs.  It may well confirm the inevitable: protection faults or fatal collisions and the like; but at least we'll have some bones to chew on.

hey got an idea after watching some stuff happen...more and more multifactorial these problems seem:
often some crashes, if not due to collision effects, can be preceded by spawns..

no, not the playersarkspawn i mean, but in ffa carnage, and indeed on few occassions with only 2-3 people, the fact that many people are slain same time then respawn can create a mess?
this is after seeing rov's sweetleaf go down half a dozen times in ten minutes, where bigass weapons cause almost instant death and the spawn turnover rate is extremely high; and extremely mind-numbing...
it could just be that arena maps as such are inherently prone by this factor? ..

ps also found out about some kind of spamming new to me but which changes pings, please remind me next time i'm on vent..

That's right;

I think I know of a way that the RAKmod is vulnerable... remind me as well.