Open BlackYuzia opened 5 years ago
Issue-Label Bot is automatically applying the label type: feature request
to this issue, with a confidence of 0.69. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
Wow, Why this is feature request? :c
I missed up or bot just helps developers answer me :smile:
User Story
I try install 3 the same game servers (CS:GO). I create user, next I create different folders for server.
Each server has its own folder in which are configs and server files.
In each of the server configs I registered unique settings (like a port, slots, sourcetv port, client port, gslt token etc).
Let me remind you that each server has a separate folder, as well as a separate config.
When, I try run server
I get some weird results. One (of the three) server was run (active). Other (2) was shutdown. I think this is my mistake.
I try run check console of server.
I check console servers (./csgoserver console) [I did it three times]
When I check ports of server, I get three times the same port (25015).
Next time, when I stoped all servers and run second server first and next other both, I get three the same ports (but not 25015 is it 26015).
So, bug can be -> When you try run two or more servers from one user, you get the same ports. OR, If I right. You just get one tmux window from and for third config/setup files (csgoserver).
Basic info
Further Information
This can be bug with
tmux[Same tmux window name] or bug with ports [lgsm setup settings from firstcsgoserver.cfg
for all other servers]How I fix it? Just rename csgoserver => csgoserver + number of server.
I'm not sure if this should be so. Perhaps the developers had no other solution than to change the name of the boot file. If so, then a bug with ports is a feature
To Reproduce
Steps to reproduce the behaviour:
mkdir
to create third different folders.linuxgsm.sh
script.linuxgsm.sh
file to third folders.start
command.For fix that:
Expected behaviour
If this is "feature", I was expect message, like
If this is BUG, I was expect NO BUG :D
So, Call it feature. Feature != bug, Fixed! Hey!