[Skorpion1976]

the only glitch so far I saw was this:

campaign change to c5m1. after approx. 30 seconds after we left the safe area I saw the loading screen for the parish. I thought it reloaded the map for all, but this just happened to me lol. All the others said I was "gone" but they kept playing. Then after map change from 1 to map 2 I had the "server disconnect" msg in the middle of the screen and a countdown for 2 seconds, but got connected again and could continue. Are these side effects related to the "old" version of your plugin ? I can´t narrow the cause down as I installed your plugin today, yesterday the revamp/sdk/l4dt plugins, but yesterday I didn´t play after installing these 3. So it could be an issue of one of the others. But nothing serious from what I experienced.

[dacomb]

Originally Posted by lexantis maybe you haven't played much publics, unfortunatelly much of the players there have a bad habit of rage quitting for every possible reasons

Originally Posted by fpsbrian Sometimes no reason at all LOL

I suppose I should have ended my last post with /sarcasm.

:P it's funny you guys thought I was serious.

[Skorpion1976]

The plugin (old one) ADDS the scores from all campaigns continuosly.
After some hours you see something like 18000 vs 16500...
I use team order 0, didn´t change anything in the code.

[AtomicStryker]

Server is not being reset properly. Probably bots remain on it after all Players have left?

Valve really screwed up 'game end' mechanics in L4D2..

[Skorpion1976]

It doesn´t happen often that the server is empty, but if so there are always bots remaining, I guess it´s because of set sb_all_bot_teams 1. If 0, server hibernate...widely known issue
Yesterday there were permanently players on it and the score from finale was transferred to the next campaign . If I put these 2 lines in my server.cfg, would that help with the "collecting points problem" ?

sm plugins unload l4d2scores.smx
sm plugins load l4d2scores.smx

[Downtown1]

Why would it keep track of the scores anymore if you are using the new version against SourceMod 1.4? Don't use the pre-1.4 versions as they will be more buggy in principle.

[Skorpion1976]

Never change a running system. I don´t just grab the plugins and put them on the server... anyone could do that. As you can imagine, downtown, it takes time to maintain a server, backup, restore, configure, compile, TESTING, reacting to log errors... Currently all my plugins work absolutely fine with SM 1.3.0. So you´d have to donate TONS of money to make me rethink my decision. The only little issue I have is the already mentioned "score collecting" one. To circumvent this I was thinking of this piece of code inside the existing OnMapStart():

public OnMapStart()
decl String:mapname[64];
GetCurrentMap(mapname, sizeof(mapname));    
//new
if (StrContains(mapname, "m1", false))
    { 
        ResetCampaignScores();
    }

This should check if there is a "m1" in the mapname and then it calls atomics Reset code. Without this the plugin would add the campaign score from just finished campaign to the score from this new campaign. So I guess that this NewMission code probably doesn´t get called because the game itself handles this in a way the plugin is not expecting it. I really have no clue, just guessing

[AtomicStryker]

Make it OnNewMission() instead of ResetCampaignScores().

[Skorpion1976]

You´re right, as it IS a new mission... o_O Thanks

[dacomb]

Just noticed an error log file from last night... the error only happened once so perhaps it's not a big deal but here it is anyway.

L 01/23/2010 - 19:58:47: SourceMod error session started
L 01/23/2010 - 19:58:47: Info (map "c2m5_concert") (file "errors_20100123.log")
L 01/23/2010 - 19:58:47: [SM] Native "KillTimer" reported: Invalid timer handle a0b0236 (error 3)
L 01/23/2010 - 19:58:47: [SM] Displaying call stack trace for plugin "l4d2scores.smx":
L 01/23/2010 - 19:58:47: [SM]   [0]  Line 732, l4d2scores.sp::OnNewMission()
L 01/23/2010 - 19:58:47: [SM]   [1]  Line 766, l4d2scores.sp::L4D_OnClearTeamScores()
L 01/23/2010 - 19:58:48: Error log file session closed.