Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This was done due to a multitude of issues caused by admins trying out QA commands, destroying their server permanently, some then even blaming SLG for a 'bug' towards their angered playerbase.
I am unfortunately not surprised by the reason, though I'm still disappointed they blamed SLG for nothing.
Disabling these commands is very stupid and takes away from server ownership.
if someone breaks their server because they used these commands its on them, SLG shouldnt have a say in how we server owners use our servers.
with that said how do we bypass the permissions block on a dedicated server that WE own.
I understand, but our stance hasn't changed. Most games don't even show or list such commands at all - for very good reasons, which have been already explained.
Eco has tons of useful commands available for admins and is easily moddable to create your own. Of course you also can create suggestions on our feedback tracker for other commands with a common use for admins to be implemented.
Developer commands however are specifically made for efficient usage in our work environments and not intended for usage on save games that are played normally.
//EDIT: Removed two posts made between me reading and answering that grossly violated the Steam Community Guidelines and locked the thread.