[EKS]

This plugin allows the last round to be finished even if the timelimit has expired

Some mapextend plugins are gonna mess with this plugin!, and not make it work.

Credits:
Ops in #AMXmod @ Quakenet for alot of help ( + AssKicR & CheesyPeteza )

[Brad]

Sneeee-ap! Good job. I've been wanting exactly this.

[v3x]

Hmm, cool.

Didn't know we were allowed to approve our own plugins

[EKS]

Why else would BAILOPAN allow it to be done ?

[eFrigid]

Originally Posted by EKS Why else would BAILOPAN allow it to be done ?

Lol, Well anyways nice job!

[versus666]

Nice work, I tried a month ago to do the same, but I didn't understood the explaination about some flags in the SET_TASK fonction to be able to finish my work.
Your way is simple, but nevertheless brilliant.

Anyway, I wonder if you realise you swapped L29 and L38-39.

I explain, if I understood your code well:

You test the 'near end of the map' ('d' flag in set_task with 10 seconds) then IF it's true you grab the value of mp_timelimit, and then you SHOULD add it (a kind of addition which act like a reset) to the mp_timelimit, like you do on L38.
But you don't.
Instead, you set mp_timelimit to 0, which effectively end the map, 10 seconds before when it should, bypassing the code cheking the end of the round.

Game over.

Else, may I borrow (a bit of) your code, with credit to one of my plugin, a kind of Task Scheduler 'JustinHoMi-style' ?


PS: If it happends I'm wrong, accept my apologies, but I'm pretty sure I'm not.

[Brad]

You are wrong.

By setting mp_timelimit to 0, that tells the server to NOT have a time limit as opposed to saying time has run out. 0 is forever. He sets it to 0 so the current round can finish and then resets it to it's original value immediately after that round, thus ending the map.

[versus666]

Ok, I see my error...Quite tricky
But any value instead of the old one would fit, as much as it's less than the original timelimit, isn't it ? I get it just there for the 'au cas où', a kind of 'academic-style'...

[Brad]

I'm assuming you're referring to resetting the time limit back to it's original value. The reason for setting it exactly back to the original value is that if you didn't do that, you could possibly be affecting the time limit in the next map. It was done that way because that's how it should have been done.

[versus666]

But shouldn't the timelimit be specified in the server.cfg, which is executed on each mapchange ?
What's why I feel strange to set back the previous value. For me it's a sort of safety mesure without reason.
But hell, it works, that's the important point.