I've noticed some different errors, causing server crashes

[Slaytanic_pb]

738:739:740:models/weapons/p_weapons2.mdl: 0
(2681561585988519400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000.0, 0.0, 0.0) [ 0.0 0.0 0.0]

This happened on wicardoven, something about the model string being too long. This too happened on wicardoven.

PM Got a velocity too high on 0

This happened on the_keep

WARNING! weapons/bow/stretch.wav is causing runtime sample conversion

The last strange bug I've noticed is on b_castle.

When you kill an ice armor archer, and it drops a quiver, the server crashes (this happened 2 maybe 3 times). It left a complaint about the quiver somehow, can't remember the message, but I'm left to believe that it didn't like having nothing to put in the quiver.

 

[Thothie]

Oh, if yer going to freak out over every error you see in that console, you should really quite playing while yer ahead.

*sigh* I remember once upon a time I wanted to fix every little error that pops up in there, but once I got ahold of the thing, I realized a lot of them are inevitable just due to the way the game works (or almost works).

There's also still a memory leak or two, or some such, causing straaaange random stuff that I can't do much about.

weapons/bow/stretch.wav is about the only thing in there I can do anything about, and it's not real important.

When you kill an ice armor archer, and it drops a quiver, the server crashes (this happened 2 maybe 3 times). It left a complaint about the quiver somehow, can't remember the message, but I'm left to believe that it didn't like having nothing to put in the quiver.

If the game actually crashes, on the other hand, it'd be good to know about... If you are the one running the server, check the msc/log_msdll.txt. I'll make a note to look into the item it drops (do you actually see the quiver? If not, it maybe the item is named wrong, but I'm surprised this is the first I've heard of it.)

 

[Slaytanic_pb]

Well...

Well, the point of reporting these errors is to see if anything can be done about them to increase server stability. I know that this game isn't perfect and there are going to be crashes, but it would be good to see less of them. If by error reporting I can help you figure out what's going wrong, then I help not only you, but the whole community. In the future I want to regularly send more of these reports in better detail to see what can be done. It is a little frustrating admining one of the few 24/7 servers (Revolution) and seeing the server crash when you're near the boss, at the boss, or just finished the boss. If it was just me playing, it wouldn't feel so bad, but it's the other players that I'd like to see enjoy playing on the server more if it crashed less.

I hope you welcome the idea of sending in reports to see what can be done. Even if I send in a months worth of crash data and you are only able to fix one problem, I'd feel it would be worth the time to send the reports in.

 

[Thothie]

Yeah... Report all ya want - I often (really often) miss stuff, and a new pair of eyes is always welcome... Just saying, that console is never going to be clean. It's a demand of the old MSC team: to fix all errors from the console as a development goal, and after fiddling with this thing for almost two years, I realize what an utterly stupid request that was. >_> They'll never all be gone. I suspect the same will be true with MS:S as well. Sometimes you just have to do things the engine doesn't like.

It would be useful to know if you actually saw those frost quivers before the server went down though.