[Feature]: Player Warnings for ns2 pls
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reading the attached update_warn_beta.sh script and the LinuxGSM code that handles the Natural Selection 2 server update and send commands. The issue asks for warnings before an update and a way to wait while players are in a round, but it does not identify the relevant files or define how to detect an empty server. Done means the warning and update behavior works for NS2 while allowing an active round to finish.
Written by the indexing model from the issue text.
Description
Priority
priority: high
User story
i made a player warn script for ns2 but it don't check if server is empty.
Game
Natural Selection 2
Linux distro
Ubuntu 26.04
Command
command: send
Problem statement
lgsm player Warnings not aviable
Scope and impact
scope: single game
Further information
I’ve created an "update_warn" script to notify players that the server is about to be updated and restarted. However, I’m not sure how to configure the script so that it checks whether the server is empty before the update—that way, players can finish their current round. :P
update_warn_beta.sh Could you delete the file from "user-attachments" after you’ve read it? I’m not really sure how to delete it myself, lol!
Alternatives considered
You can use the command ./ns2 server send in conjunction with sh_csay color message (for colored, centered text) or sh_say (for a message in the general chat); however, this requires the "Shine" administration modification.
https://github.com/Person8880/Shine/wiki/Base-Commands#commands
- Dominant language
- Shell
- Stars
- 4.9k
- Forks
- 866
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 100
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GameServerManagers/LinuxGSM
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
distro: Debian distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
GameServerManagers/LinuxGSM#5241 ·
Maintainers usually reply within 1 day
-
command: monitor distro: Ubuntu engine: spark game: Natural Selection 2 info: query reproducible: unable severity: critical type: bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
GameServerManagers/LinuxGSM#5238 ·
Maintainers usually reply within 1 day
-
engine: null game: Teamspeak 3
Difficulty 3/5 Half a day Newbie friendliness 66/100
GameServerManagers/LinuxGSM#5237 ·
Maintainers usually reply within 1 day
-
command: install command: monitor command: start priority: medium scope: all servers type: feature
Difficulty 3/5 1-2 days Newbie friendliness 68/100
GameServerManagers/LinuxGSM#5204 ·
Maintainers usually reply within 1 day
All issues in GameServerManagers/LinuxGSM
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100