[Feature]: Player Warnings for ns2 pls

Open
#5,240 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
bash, shell
Domain
backend, cli

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

command: send distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
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

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GameServerManagers/LinuxGSM

All issues in GameServerManagers/LinuxGSM

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.