Open BranDougherty opened 1 year ago
I like all of the changes except the approach to ui_sniperline
. In my opinion forcing users to check 2 boxes in 2 different areas of the launcher in order to enable sniper line is still not intuitive. What I like about the sniper line in 1.7.1 is that you can toggle it with ALT+F2 (as long as server allows it?) while you are playing, and this is a behavior that I would keep, especially since we have all the functionality to do it this way.
So, what I would recommend is:
/toggle ui_sniperline 0 1
command to ALT+F2. Ideally it would have some intuitive label like "Toggle sniper line (if server allows it)". I think this may also require changes to the configs in base repo.Let me know what you think, I'm also fine with keeping your changes if people prefer your approach.
This PR adds support + UI for the
sv_stationaryguns
andui_sniperline
cvars.The
ui_sniperline
andsv_sniperline
relationship is not obvious for users so I changed their descriptions to try and make it easier to understand. Unfortunately adding theui_sniperline
setting resulted in a small awkward scrollbar on my screen, but I'm not sure what to do about it, and we need to have UI for this cvar somewhere.The
sv_stationaryguns
cvar controls whether stationary guns are allowed to be spawned in maps and shot by players. IMO for a singleplayer experience, having stationary guns enabled by default makes sense.I also ran into issues with the launcher not starting the server properly. This happened because the node.js stream interface chunks
'data'
events, and we were searching for the[NET] ...
string only within one chunk. So on the off chance the string spanned two chunks, we would miss it. Consider this a stop-gap measure while proper IPC is implemented.While this PR is not very ambitious, I'm not familiar with the technologies used in the launcher so please give this a careful review.