Does anyone know why, after the ET 1.02 upgrade there’s always the message “Closed!” at the start of the Railgun map.
It wasn’t there before was it ? And it’s not there on all maps, but always on Railgun.
To show what I mean see :
http://user.tninet.se/~bwa507g/pics/closed.jpg
Afaik it’s a script addition to indicate that the track switch has reached it’s “down” position both physically and has been “logged” as such by the script.
At the map beginning it will be sent to it’s “closed” position on spawn and as such, the message you’re seeing is likely the response to that
It’s a debugging thing that QA missed for the 1.02/2.56 release… It’s removed again in etpro, and you can remove it yourself–just extract the map script from pak1.pk3 and remove the ‘wm_announce “Closed!”’ line.
The change has no effect on the client (clients don’t run map scripts at all–this is part of the reason the tug on railgun is so jerky), it’ll need to be made on the server. At any rate, as long as you don’t change the pk3 itself, it won’t have any effect on the pure check–the changed files just won’t be loaded from outside the pk3s.
Can the script file be put outside of the pk3 and where ? Because I thought that if I re-added it to the pk3 file it would be downloaded by clients since it’d be a different version than they’d have ?
Yes, you can (for the stock maps, anyway–it won’t always work for custom maps, and I haven’t made it as far as looking into why.) Just put the modified scripts in …/etmain/maps (or …/etpro/<b_mapscriptdirectory>/maps if you’re using etpro - this will work with custom maps where just putting it in …/etmain/maps doesn’t.)
Nice, thanks! Wasn’t sure that was doable 
Can’t wait until work is over (and it’s still only 8:40 in the morning…)