[Velture]

Download link doasn't work.

[asherkin]

Originally Posted by Velture Download link doasn't work.

Yeah, Linode are being a bit slow.
Shouldn't be much longer.

[frank.]

I'm setting up a "multimod" server at the moment. One of the mods is TFDodgeball, and it is spitting out a number of errors. In my server config file, sm_dodgeball_enabled 0 is set. The map being loaded first is not a dodgeball map. When sm_dodgeball_enabled 1 and a dodgeball map are loaded as default, the errors still occur.

The server crashes, and restarts due to the errors. They show up as:

L 06/17/2011 - 208:28: [TFDB] Sigscan for Dissolve failed - Disabling detour to prevent crashes
L 06/17/2011 - 208:28: [TFDB] [CENTITY] Failed to retrieve pointer from GetLoadoutSlot

Alongside it run Vs Saxton Hale, and Prophunt. SDKHooks is installed, as are TF2Items, KAC (well, SMAC), sourcebans, and ultimate mapchooser.

What could be the cause of this, and what could the solution be?

EDIT: My server hosting provider doesn't allow uploads/downloads of .dll files, so we have to through their automated system. I believe the version installed is outdated, and will work when it has been updated to the current version.

EDIT2: Now with the addon installed, backblasting with the flamethrower on any map crashes the server.

[baijiaqing]

Same as above.
Needs fixing

[asherkin]

Originally Posted by baijiaqing Same as above. Needs fixing

Fixed gamedata has been pushed, if you are running a release version of SourceMod it'll automatically update next time your server restarts.

[Velture]

ammo regeneration doasn;t work.

[clutchh]

Originally Posted by Velture ammo regeneration doasn;t work.

This.

Also causes a crash when someone dies.

[Velture]

also fire couses dmg to players.

[snelvuur]

yeah had a crash to on this, i assume something needs a update.. lets wait a bit i assume ash has it already busy as it is.

[asherkin]

It needs the CEconItemView changes from TF2Items. As I'm sure a lot of you have seen they aren't exactly perfect yet, so I figured it was better to only be testing it in one extension.