Server ignoring "nextlevel" and loading the next map from mapcycle.txt
Hey, I think it might be a bug, idk how/when it started to happen, but even setting nextlevel to some map through my plugin or manually, it try to get the next map from mapcycle.txt. It's messing with my warmod plugin when in a Bo3/Bo5.
It just happens when the match ends, if you use changelevel it works fine. To test it, put only de_cache in mapcycle.txt, set nextlevel to de_dust2, set mp_maxrounds to 2 and kill the bots to go faster. When the match ends you will see over the scoreboard "Loading Dust 2 in ...", after the countdown, it will change to de_cache. Can someone confirm this issue or at least point something im doing wrong? This is what pop up on the console right when the map is changing: HTML Code:
Going to intermission... |
Re: Server ignoring "nextlevel" and loading the next map from mapcycle.txt
Sm_setnextmap
|
Re: Server ignoring "nextlevel" and loading the next map from mapcycle.txt
Disable nextmap.smx
|
Re: Server ignoring "nextlevel" and loading the next map from mapcycle.txt
Quote:
|
Re: Server ignoring "nextlevel" and loading the next map from mapcycle.txt
Quote:
https://sm.alliedmods.net/new-api/nextmap/SetNextMap SetNextMap as well as: https://sm.alliedmods.net/new-api/console/ServerCommand ServerCommand "changelevel" - I ask about CSGO specifically, as you need to include the workshop path for workshop maps: changelevel workshop/XXXXXXXX/de_cache |
Re: Server ignoring "nextlevel" and loading the next map from mapcycle.txt
Quote:
|
Re: Server ignoring "nextlevel" and loading the next map from mapcycle.txt
Quote:
|
Re: Server ignoring "nextlevel" and loading the next map from mapcycle.txt
Quote:
|
Re: Server ignoring "nextlevel" and loading the next map from mapcycle.txt
I fixed the issue changing my
HTML Code:
ServerCommand("nextlevel %s", map); HTML Code:
SetNextMap(map); |
Re: Server ignoring "nextlevel" and loading the next map from mapcycle.txt
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. |
All times are GMT -4. The time now is 20:25. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.