[joao7yt]

Originally Posted by asherkin You probably updated SourceMod and accidentally re-uploaded nextmap.smx, which you would have disabled earlier because it doesn't work very nicely with CS:GO. But it's ok, go ahead and blame us for it.

Sorry if I went harsh, wasn’t my intention. I was just reporting a behavior I had. And every time I update sourcemod I remore the plugins folder... I’m almost certain that it wasn’t behaving this way before. That huge warmod plugin has been used for a long time by many and til now no one have complained about it when running a Bo3/5. And I believe on its page was not saying to you to remove nextmap from plugins.

Anyway, if nextmap has always been working this way, I really think “nextlevel” should get more priority than “cyclemap.txt”, don’t you think?

[asherkin]

Originally Posted by joao7yt Sorry if I went harsh, wasn’t my intention. I was just reporting a behavior I had. And every time I update sourcemod I remore the plugins folder... I’m almost certain that it wasn’t behaving this way before. That huge warmod plugin has been used for a long time by many and til now no one have complained about it when running a Bo3/5. And I believe on its page was not saying to you to remove nextmap from plugins. Anyway, if nextmap has always been working this way, I really think “nextlevel” should get more priority than “cyclemap.txt”, don’t you think?

The nextmap plugin's specific purpose is to set the nextlevel cvar (which is what most games use to decide the next map to load) to what is specified in the mapcycle / set by endmap vote / rtv.
sm_setnextmap exists to override that logic to force whatever map you want explicitly.
If you want to use nextlevel to control the next map, the only real answer is to remove the nextmap plugin as you're going against why it exists.
There hasn't been a behaviour change in how any of this works in as long as I can remember.

[joao7yt]

Originally Posted by asherkin The nextmap plugin's specific purpose is to set the nextlevel cvar (which is what most games use to decide the next map to load) to what is specified in the mapcycle / set by endmap vote / rtv. sm_setnextmap exists to override that logic to force whatever map you want explicitly. If you want to use nextlevel to control the next map, the only real answer is to remove the nextmap plugin as you're going against why it exists. There hasn't been a behaviour change in how any of this works in as long as I can remember.

That's fine, tks. I use "SetNextMap(map);" since it's safer than just input the sm_setnextmap. Changed my code here