Using Command('/map newmap') corrupts Nextmap var?

[y0uRd34th]

The function Command() corrupts the serverside nextmap variable.
I came up with it when working on a !nextmap script. After I implemented a !votemap <map> command it did not work any longer. I changed the Command('/nextmap') to Command('/map <map>'). The map changes, but when I use !nextmap it always jumps back to one map. (The second in the mapslist)
Using it as admin works /:

I have absolutely no idea why, I hope you understand what I wrote

[Hacktank]

Im pretty sure that if you do /map bla ingame it will do the same thing to you.

if targetmap = nextmap then command('/nextmap') else command('/map '+targetmap);

[Gizd]

/map doesn't change map rotation so you're like playing same map as before.

[y0uRd34th]

Okay, thanx. Then I just stay with !nextmap for now

[Gizd]

You can go pro and find next map with same name on mapslist and do some magix to skip to there(the only I can think of at this moment is editing mapslist and reloading it).

[y0uRd34th]

Yeah, I tried it with changing the NextMap variable myself with the way you said, but didn't work to modify. It would work with another var which holds the next map