Ok ... Just checked the extend map thingie ...
The extention time is added to both mapTime and timeleft
Scenario 1:
maptime is the standard 900 secons and timeleft is 600 (300 secs passed)
- No teamswitch has occured
extending the map by 15 minutes
maptime is now 1800 and timeleft is 1500, finishing the map with no more extension
- Teamswitch will occur when time left is 900
Result: one team will play CT 300+600 and the other one 900 secs = Fair
Scenario 2:
maptime is the standard 900 secons and timeleft is 200 (700 secs passed)
- Teamswitch was done after 450 seconds
extending the map by 15 minutes
maptime is now 1800 and timeleft is 1100, finishing the map with no more extension
- Teamswitch will occur again when time left is 900
Result: one team will play CT 450+900 = 1350 and the other one 250+300 secs = 550 secs ... Might not seem fair ... but what is a good solution?!
And what if the map is replaced by another map after 400 secons ... then no teamswitch will occur at all!
I dont think this can be 100% fair ... but it will give some fairness if maps are played the standard time which they are 95% of the times on our server ... guess most servers have the same ...
Leaving the plugin as it is ... unless someone comes up with a better suggestion ... But to start to calculate something else than timeleft<=maptime/2 for trigger for mapchange will just be akward in my opinion ... the fairness can always be set aside with another map vote ...
Thanks for raising the question though ...
Conclusion
Plugin will not crash when extending the map ... some extra switching might be done if extension is done after halftime.
Works as designed ;)
We sure will be using it on our servers even if it might not get approved for not handling this in more detail ;)
__________________
--- Growing older is mandatory --
----- Growing up is optional -----