[2022] Can't use /vomit or /digest

The command for that is /clearstomach as of 9.0, but it might only be available for developer tier users.

Developer commands are only available for developers, yes. Both commands are made for QA quick testing and might not work correctly or in unexpected ways, but I think the modder of your trust could very easily provide a similar command if you for some reason deem that QA command useful for general admin usage, which we don't. (And also wasn't made for that purpose, it never allowed to dump the stomach contents of other people than yourself, for example)

First place very likely would be our discord, where most of the modders are: https://discord.gg/eco

They also have their own official community server which is pinned in our mod channels. The ModKit page on our GitHub might also be helpful, but documentation on things is still in a very early state, given Mod support is still in heavy development.

The restriction of this command is not based on 'cheating', but rather the commands original intention for QA and the fact that it might do things that are unexpected by a user. All commands that were made for this purpose and have never been built for admin use in a safe way are marked this way, no matter if these are especially 'cheaty', especially 'dangerous' or can be used to destroy the server / other players fun; it's solely based on what the command was originally made for. There is only very few commands that became dev commands in a different way than this.

The usefulness of the command for general administration would just be a factor in determining if we ever make that command available as a dedicated admin command ourselves or if we don't. The use cases you mention rather seem like for testing purposes as a user than actual server administration and that is not really the purpose of our admin commands.

I also do use a modification on official server White Tiger that adds a command for our GMs that allows them to force other players to vomit. That is due to that server having constitutional laws that require a specific amount of food SP to be able to craft recipes of specific professions, a higher amount the higher-end the profession is. Given that is a very workaround way for improving on the situation that food quality does not play a role in Eco in the end game in vanilla, this leads to some brand new players getting stuck with their food bonus, not reaching the required values as they didn't understand that they have to eat high quality food. In such cases a GM can a single time per player reset their stomach contents. But as I said, even we use a mod for that.

Given managing communities and owning game servers is my thing for over 15 years now, I am and have always been a strong believer in server admins autonomy that I uphold whereever it comes to it, and it regularly does, given there is more than enough people that would like to see admins to be restricted or non-existing in this and other games.

But from the perspective of a game developer this is not in all cases a desirable thing, especially when it is about content that is not intended for server admins to begin with. These commands in other games are simply hidden, people do not know they exist or need to enable kind of development mode - mostly for singleplayer, if at all available for multiplayer servers that's then mostly going along with a clear warning for any user potentially playing on the server by displaying that the server does have such mode active and taking it out of the regular server lists. (Which we don't have any capability to do currently, so it's not a potential solution at this point) We only show them, as we have the unique thing of Developer Tier with full source code access to the game and a sizable community that makes use of that (more than 700 people, actually, with lots of them being modders that got the source code access for free as a support from us, the access is not only receivable via paying!) and deals with it, so it made sense for us to make these available to them.

If we wouldn't have made this decision, though, we also would not have made these commands available to admins, they would just be hidden, for our own development purposes only and people wouldn't even know they exist.

Unfortunately there is often a difference between having the best in mind for the server and for the actual players - which are what we care about. And it's unfortunately not an uncommon thing that admins use destructive commands without knowing what they do, leading to non-revertable issues (as that's the nature of QA commands), complaining about how the QA command isn't safe for admin use or just pretending it's a game bug and sending players to us. Potential intentional abuse cases of them not included. That's a thing we regularly see even with dangerous non-developer commands and it's not a desirable thing to have. Given the developer commands specifically are not intended for admins though, we have no interest to increase this problem by making them available for admins, especially given we know they will cause issues and are not of the opinion that those are actually needed for administrating servers. (I've been able to do so without for the last four years at least, given their restriction to local servers applied to me as well)

So yes, needing to live with that for commands intended for admins where we did our best to prevent damage as best as possible I do see as upholding admins autonomy. Making available to them developer commands that are neither intended, polished or required for them - I do not.