[0.13.15] achievements are locked and no one used /c

[TyphoonNL]

so yeah, earlier today i had an achievement and a few hours later i rejoined after playing a different game and it said that it is disabled
i checked the log to see if my co-admin cheated but he didn't
also i am running vanilla

how can the achievements be disabled? i don't have mods and none have cheated

EDIT: i really want to see a feature how it was disabled and who cheated/disabled by mod
EDIT2: uploaded the map, it says its disabled by command but i never used /c with this map

[Loewchen]

Please upload the map.

[TyphoonNL]

uploaded

[Xelephant]

Hmm i just tried and joined your server, commands are not restricted or disabled. If you use a headless, are you using "--allow-commands admins-only" as an argument?

If i use that argument on mine the commands are disabled just fine.

[Klonan]

If someone can use a comman, they can use a comman to clear the chat history,

So far there haven't been any other reports, and there is no way of knowing exactly what caused the achievements to be disabled,
So for now i will move it to 1/0 magic, if it happens again please make a new bug report with steps to reproduce the issue

[TyphoonNL]

Hmm i just tried and joined your server, commands are not restricted or disabled. If you use a headless, are you using "--allow-commands admins-only" as an argument?

If i use that argument on mine the commands are disabled just fine.

last 2 maps ago i used that, but now i use --allow-commands restrict (thats what it shows when you type factorio --help)
but if you say commands are not restricted then there is clearly a bug because it should be restricted

Code: Select all

/home/factorio/vanilla/bin/x64/factorio --config /config/config.ini --port 34197 --start-server /saves/Xerologic-v3.zip --server-settings /data/server-settings.json --autosave-interval 15 --autosave-slots 3 --latency-ms 225 --allow-commands restrict

this is how i start the headless server

[TyphoonNL]

alright, i asked a non-admin to do a command and he can even though its restricted to admins
and there are only 2 admins on my server
so there is clearly a bug with the headless server

some moderator(s)/devs should join my server and test /c and then /kick

EDIT: non-admins can't kick but they can use /c ? dafuq is that?

2016-08-09 15:32:43 [CHAT] <server>: kucky81 can you do a /c command to see if a non-admin can cheat?
2016-08-09 15:33:33 [COMMAND] kucky81 (command):
2016-08-09 15:34:05 [CHAT] <server>: any errors?
2016-08-09 15:34:11 [CHAT] kucky81: no
2016-08-09 15:36:00 [CHAT] <server>: ok, thx
2016-08-09 15:36:14 [CHAT] <server>: there is a bug then
2016-08-09 15:36:23 [CHAT] Minidodo: kucky, try /c game.player.print(game.speed)
2016-08-09 15:36:35 [CHAT] <server>: even though the commands are restricted to admins, everyone can use commands
2016-08-09 15:36:50 [COMMAND] nik12111 (command):
2016-08-09 15:36:56 [CHAT] Minidodo: i think there is no warning, because there isn't any command
2016-08-09 15:37:31 [COMMAND] kucky81 (command): game.player.print(game.speed)
2016-08-09 15:37:38 [CHAT] Minidodo: what is the output?
2016-08-09 15:37:48 [CHAT] kucky81: 1
2016-08-09 15:37:52 [CHAT] Minidodo: bad.
2016-08-09 15:38:07 [CHAT] Minidodo: then there is an bugg, what Typhoon is thinking..
2016-08-09 15:38:28 [CHAT] kucky81: can only the first player do cheats?
2016-08-09 15:38:40 [CHAT] Minidodo: no, only admins
2016-08-09 15:38:45 [CHAT] <server>: no, it should be admins only
2016-08-09 15:39:03 [CHAT] Minidodo: then try... /kick Minidodo
2016-08-09 15:39:11 [CHAT] Minidodo: that should not work.
2016-08-09 15:39:25 [KICK] nik12111 failed to kick player Minidodo (not an admin).
2016-08-09 15:39:31 [KICK] kucky81 failed to kick player Minidodo (not an admin).
2016-08-09 15:39:35 [CHAT] Minidodo: better than nothing xD
/admins
TyphoonNL
Minidodo (online)

[Klonan]

Code: Select all

/home/factorio/vanilla/bin/x64/factorio --config /config/config.ini --port 34197 --start-server /saves/Xerologic-v3.zip --server-settings /data/server-settings.json --autosave-interval 15 --autosave-slots 3 --latency-ms 225 --allow-commands restrict

this is how i start the headless server

The correct argument is --disallow-commands

[TyphoonNL]

isnt that for disable the commands? /kick is also a command so it should get disabled as well, and i dont want that
also

Code: Select all

[factorio@localhost ~]$ /home/factorio/vanilla/bin/x64/factorio --help

General options:
  -h [ --help ]                 display help
  --version                     show version information
  -v [ --verbose ]              enable verbose logging
  -c [ --config ] PATH          config file to use
  --no-log-rotation             don't rotate log file
  --mod-directory PATH          Mod directory to use

Running options:
  -s [ --map2scenario ] arg     map to scenario conversion
  -m [ --scenario2map ] arg     scenario to map conversion
  --apply-update arg            immediately apply update package
  --create FILE                 create a new map
  --map-gen-settings FILE       Map generation settings for use with --create. 
                                See data/map-gen-settings.example.json
  --start-server FILE           start a multiplayer server
  --start-server-load-latest    start a multiplayer server and load the latest 
                                available save
  --until-tick TICK             run a save until given map tick

Server options:
  --latency N                   multiplayer server latency, in ticks
  --latency-ms N                multiplayer server latency, in milliseconds
  --autosave-interval N (=2)    server autosave interval, in minutes
  --autosave-slots N (=3)       server autosave slots
  --allow-commands arg (=true)  allow (true), disallow (false), or restrict 
                                (admins-only) use of the command console
  --no-auto-pause               don't automatically pause when no players are 
                                connected
  --port N                      network port to use
  --rcon-port N                 Port to use for RCON
  --rcon-password PASSWORD      Password for RCON
  --server-settings FILE        Path to file with server settings. See 
                                data/server-settings.example.json

[factorio@localhost ~]$

its not a command at all, because its not there (i actually used that command and it gave me an error and the server wouldn't even start)

[TyphoonNL]

i started the server with this line:

Code: Select all

[factorio@localhost vanilla]$ /home/factorio/vanilla/bin/x64/factorio --config /home/factorio/vanilla/config/config.ini --port 34197 --start-server /home/factorio/vanilla/saves/Xerologic-v3.zip --server-settings /home/factorio/vanilla/data/server-settings.json --autosave-interval 15 --autosave-slots 3 --latency-ms 225 --allow-commands disallow

and guess what

2016-08-09 16:10:53 [CHAT] Minidodo: kucky, can you use the cmd now?
2016-08-09 16:11:08 [CHAT] Minidodo: ./c game.player.print(game.speed)
2016-08-09 16:11:25 [COMMAND] kucky81 (command):
2016-08-09 16:11:44 [COMMAND] Minidodo (command): game.player.print(game.speed)
2016-08-09 16:11:53 [CHAT] Minidodo: for me there is an output. for you?
2016-08-09 16:11:55 [COMMAND] kucky81 (command): game.player.print(game.speed)
2016-08-09 16:12:19 [CHAT] Minidodo: output 1, right?
2016-08-09 16:12:38 [CHAT] kucky81: yes, wie eben
2016-08-09 16:12:45 [CHAT] Minidodo: -.-
2016-08-09 16:14:10 [COMMAND] kucky81 (command): game.player.print(game.speed)
2016-08-09 16:14:16 [CHAT] kucky81: 1
2016-08-09 16:14:21 [CHAT] Minidodo: any other ideas?
2016-08-09 16:14:47 [CHAT] <server>: can you guys use /kick?
2016-08-09 16:15:14 [KICK] kucky81 failed to kick player Minidodo (not an admin).
2016-08-09 16:15:21 [CHAT] kucky81: no
2016-08-09 16:15:25 [CHAT] <server>: mini?
2016-08-09 16:15:30 [KICK] Minidodo was kicked by Minidodo. Reason: unspecified.

you still can use /c and admins can still kick players

[Xelephant]

The Command restriction works for my server. I tried the following command lines options in a test i did with 0.13.18:

1.
--allow-command disallow = Commands are allowed
2.
--allow-command true = Commands are allowed
3.
--allow-command false = Commands are disallowed for everyone
4.
--allow-command admins-only = only admins can run commands

So the valid argument options are true, false, admins-only.