-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wait Period rewrite + Black Mesa Chapter 1-3 EDT improvements #168
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Waiting for players timer will always wait the full period on first map load or if the map change was over 5 minutes ago
I'd rather a consistent behavior. What issue does this solve when premature starting has been fixed?
Waiting for players timer will now reset when the last spawned player disconnects and the map has not started yet
What issue does this solve?
Bringalls
I tend to prefer portals over bringall. One, it does not disrupt players as much, people can (mostly) progress at their own pace (sucks when 1 guy is speedrunning). Second, some play this as their first BM or even HL experience. So I only used them for big map events.
I have not tested this in-game yet, will do that next.
The issue that this solves when premature starting has been fixed is a quality of life change. If a player joins, crashes mid-connection and never rejoins, I would assume a new batch of people are going to join together down the road and we would want to wait longer than the wait period of
This solves a issue with the timer still counting down regardless whether if the last connected spawned player spawns in, disconnects and never rejoins. I was thinking we'd want the timer to reset and wait if there are no connected players.
For sure I agree with this. I've only tried to include |
I'd still rather let players control for this themselves. If they are together, they'll wait for each other (which may take longer than our timer anyway). If it's a random, we're just making them wait for nothing. Restart map is also a thing - in which case the timer should fulfil its primary purpose - load time balancing.
That's fine. One last thing, there's an extra second after timer reaches 0. I would expect it to start a second after "1". |
Code Changelog:
3
seconds when the player count matches the player count of the last mapMap Changelog:
bm_c1a0a
LCS_AM_Airlock_trigger
anddoor_02_btm
bm_c1a0b
lab2_door4
bm_c1a1a
bm_c1a1b
95
on game startchangelevel
block to the end of the levelbm_c1a1c
weapon_glock
to player equipmentbm_c1a1d
bm_c1a1e