Nuclear Dawn > General Discussions > Topic Details
ᵡᴳḽᴰ >>Stickz<< Oct 6, 2013 @ 2:29pm
Tag Restriction
is there any chance the tag restriction for quickjoin could be removed? servers that have different resources or spawn times are currently removed from quickjoin which isn't fair. this may also apply for if a server is on a custom map.

at the very least could the spawntimes tag be fixed? (like in a warmup round for instance) the server tag is applied and will not remove until the server is rebooted. thus pushing people away from the server via quickjoin.

ohh and also servers that try to bypass this unfairness, they have to change their port every 2-3 days. it will get blacklisted so people can't join.
Last edited by ᵡᴳḽᴰ >>Stickz<<; Oct 6, 2013 @ 2:33pm
Showing 1-4 of 4 comments
< >
psychonic  [developer] Oct 8, 2013 @ 3:05pm 
Originally posted by xG:D >>Stickz<<:
at the very least could the spawntimes tag be fixed? (like in a warmup round for instance) the server tag is applied and will not remove until the server is rebooted. thus pushing people away from the server via quickjoin.

Make sure that you're resetting them back to their exact values. The engine is very picky with the automatic tag application.

For nd_spawn_wave_interval, this is "12.0". Even "12" might make it keep the tag applied.
For nd_spawn_min_time, this is "6.0".

If those variables are set to those exact values and the "spawntimes" tag is still being attached, please let me know.
ᵡᴳḽᴰ >>Stickz<< Oct 8, 2013 @ 3:38pm 
the spawntimes tag is only applied to nd_spawn_min_time, not nd_spawn_wave_interval. however, both of those values are as specified and will not correct themselves (if changed) unless you reboot the server. i've tested this 3 times to be sure before posting it.

i've got other tags that correct themselves instantly when changed... but the spawntimes are being extremely stubborn.
Last edited by ᵡᴳḽᴰ >>Stickz<<; Oct 8, 2013 @ 3:41pm
psychonic  [developer] Oct 8, 2013 @ 5:30pm 
Originally posted by xG:D >>Stickz<<:
the spawntimes tag is only applied to nd_spawn_min_time, not nd_spawn_wave_interval. however, both of those values are as specified and will not correct themselves (if changed) unless you reboot the server. i've tested this 3 times to be sure before posting it.

This sounds like it is maybe related to the tag being tied to two variables. I'll look into it.
psychonic  [developer] Dec 6, 2013 @ 10:16am 
These will be two separate tags in the next update, but the Play Now penalty will not stack.
Showing 1-4 of 4 comments
< >
Per page: 15 30 50