[OneEyedJacks]

Same problems! I downloaded the sma file and compiled myself results are - Here

Although no longer instantly switches map at the end of game which is great, however doesn't go to the selected map.

L 07/31/2021 - 186:46: Number of maps loaded: 355
L 07/31/2021 - 187:49: countVote() executed (3,3, 0)
L 07/31/2021 - 187:49: Frame Stack (3) chose op4_tpark (1)
L 07/31/2021 - 187:50: countVote() executed (4,1, 0)
L 07/31/2021 - 187:50: One Eyed Jacks (4) chose op4_u_boat (1)
L 07/31/2021 - 188:01: checkVotes() executed
L 07/31/2021 - 188:01: op4_pool_day has 0 votes
L 07/31/2021 - 188:01: op4_u_boat has 1 votes
L 07/31/2021 - 188:01: op4_edge has 0 votes
L 07/31/2021 - 188:01: op4_tpark has 1 votes
L 07/31/2021 - 188:01: op4_demise has 0 votes
L 07/31/2021 - 188:01: Extend has 0 votes
L 07/31/2021 - 188:01: None has 0 votes
L 07/31/2021 - 188:01: amx_nextmap was set to op4_u_boat
L 07/31/2021 - 189:45: changeMap() executed
L 07/31/2021 - 189:45: chat time is 10.000000
L 07/31/2021 - 189:45: timelimit is 3
L 07/31/2021 - 189:52: Manually handling chattime
L 07/31/2021 - 189:52: Current Map: op4_bodies

[fysiks]

One Eyed Jacks and I did some interactive debugging and ultimately found that the because Opposing Forces doesn't have an mp_chattime cvar, it was using a default value of 10 seconds which was allowing the server to change the map normally before nextmap could change the map according to the amx_nextmap cvar. This value of 10 seconds was implemented in

I've created an issue and a pull request to fix this.

[DJEarthQuake]

Register_event("30", "changeMap", "a") is what controls the Amxx metamod mapchange. The map picking is done 129 sec before mp_timelimit runs out. If this mp_chattime is too long for whatever reason the metamod instructions are ignored and server just is back to running like metamod is not there and goes off the mapcycle. Now that I can believe!!

[fysiks]

Did you accidentally post in the wrong thread?

[DJEarthQuake]

In retrospect it appears so!

[fysiks]

Originally Posted by DJEarthQuake Register_event("30", "changeMap", "a") is what controls the Amxx metamod mapchange. The map picking is done 129 sec before mp_timelimit runs out. If this mp_chattime is too long for whatever reason the metamod instructions are ignored and server just is back to running like metamod is not there and goes off the mapcycle. Now that I can believe!!

For games that support mp_chattime, it guarantees that that amount of time will elapse between showing the scoreboard and changing the map. The nextmap plugin assumes this logic and adds 2 seconds so that AMX Mod X can change the map before the server's normal functionality does.

[DJEarthQuake]

What if amx_vote_time is real high? I did not see anything to consider that in the base code yet. Have you?

[fysiks]

Originally Posted by DJEarthQuake What if amx_vote_time is real high? I did not see anything to consider that in the base code yet. Have you?

No, but that's not relevant to this thread.

[DJEarthQuake]

Map change was reverting to mapcycle since it was being triggered by: 'frags' or 'flag captures'. Those are not part of mapchooser. Chat time running too long and game using stock mapcycle can be more effectively controlled with a task instead of solely relying on an event.

I've added both frags and flags in with my updated mapchooser/nextmap with rockthevote.