[Release] EssentialMode base

Nyets comrade, for Arstozka!

I guess I’ll adress this however none of you have read my update posts related to this.

So let me quote that real quick:

Added convar: es_enableDevTools enabled by default. Set to 0 if you want them disabled

Link: [Release] EssentialMode base

So this was mentioned that it was enabled by default, as to why this would be enabled by default: “A lot of people don’t even know how to set these and I get questions daily regarding convars.”

So just search next time please. It can easily be disabled if you don’t want it, neither does it really matter as that steamid is mine. I haven’t joined a single random server in the past month and neither would I try and abuse it.

1 Like

Looks like the strange version quoted here was in version 4.6.1 - It was changed for 4.6.3

1 Like

With all due respect surely it can never be a good idea to put this sort of “backdoor” in a widely used piece of code, whatever its intended purpose is. We only have your word regarding how you would use this functionality and what if your Steam account were to be compromised? It then opens up all of these servers to whoever is in control of your account.

This is a framework people are supposed to copy and either learn from as they build their own framework, or edit this one so that it fits their needs. If you take someones FREE code and then complain because the developer customized the code for themselves, then this server stuff is not for you.

It’s not “tucked away” or hidden in anyway, or there to ‘backdoor’ your server. It took maybe 6 seconds to find everything that related to dev, _dev, and self.group because essentialmode is literally ~8 scripts that you can search all at once in any basic text editor. You don’t even need that, he literally commented the lines relating to the dev code. If you don’t like whats in the code, then just remove it, its what your supposed to do with the files anyway.

1 Like

So? Disable it. It’s a convar that you can easily change, and my account wont be hacked. Kinda dumb assumption on anything.

1 Like

You’re right, if you don’t like it remove it, or even better don’t use it; which I won’t. I’m only warning people of the potential problem, I’m not saying don’t use it no matter what. I just think it’s important to let people know exactly what this script allows.

You say “So?”, I’m pointing out a security vulnerability in your code. You say your account won’t be hacked, that is a very naive assumption to make and something you can never be sure of.

In my opinion it is bad programming practice, why not put something in that allows the owner of the server to quickly give you temporary permissions to help you debug it? Rather than hard coding in your own steam ID (which has a suspicious concatenation in it which still hasn’t been properly explained) and giving it elevated privileges.

https://pastebin.com/A9TyxU3c

Still continuing to receive errors after numerous fresh installs of EessentialMode and FiveM. Essentialmode is listed to start before es_admin. I attempted to use your website for support, but I am not receiving the email confirmation.

Anything I am doing wrong?

EDIT: I should add that I have couchDB working and it appears to be working. When a player joins the server, it adds a new user thing. Whenever the console is done loading, it says “Everything is ok!” or whatever.

ehm you should do

setadmin [id] [permission-level]
setgroup [id] [group]

not setadmin [id] [group]

1 Like

It isn’t hard-coded. It checks a web server for a steam id. So even if my account was hacked I would just remove it. You’re way to afraid for literally nothing.

The first “version” of this debug mode was more of a joke and wasn’t meant to exist. So I immediately removed it once I noticed it. Later on I implemented it back in in a better way. Which is the current implementation.

1 Like

Yeah that’s great for everyone who keeps their code up to the date with the latest version of essential mode, but not so great for those who don’t update and are left vulnerable to someone using your Steam account maliciously. That’s why it’s not good practice. I’ve made my point and I hope some lessons are learnt.

I only support updated versions, not my problem. There’s nothing to be “learned” as nothing was done incorrectly.

4 Likes

If other’s don’t update their scripts, that’s their issue, not @Kanersps.

My point is, it wouldn’t be an issue (for anyone) at all if this wasn’t coded in the way it has been; that’s why I say it’s bad practice.

Why not just remove the line yourself if it bothers you so much?

I’m not using the script, I’m only saying something so others know the potential implications.

The bottom line is this:

It can easily be disabled if you don’t want it

If people are really that paranoid that @Kanersps is going to hax0r their server, it can be disabled. If people don’t bother to look into what scripts can do, that’s again not his fault. Even more so because it’s a completely optional thing.

1 Like

i need help im getting this error:

Loaded System.Buffers, Version=4.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 into ScriptDomain_234936983
InvokeNative: execution failed: type must be object, but is array
Error running call reference function for resource essentialmode: Execution of native 000000008e8cc653 in script host failed.
stack traceback:
[C]: in upvalue ‘_in’
citizen:/scripting/lua/natives_server.lua:190: in function ‘PerformHttpRequestInternal’
citizen:/scripting/lua/scheduler.lua:233: in function ‘PerformHttpRequest’
server/classes/player.lua:198: in function ‘CreatePlayer’
server/player/login.lua:10: in local ‘ref’
citizen:/scripting/lua/scheduler.lua:277: in function citizen:/scripting/lua/scheduler.lua:268
Error running call reference function for resource esplugin_mysql: citizen:/scripting/lua/MessagePack.lua:830: missing bytes
stack traceback:
[C]: in function ‘error’
citizen:/scripting/lua/MessagePack.lua:830: in method ‘underflow’
citizen:/scripting/lua/MessagePack.lua:465: in field ‘any’
citizen:/scripting/lua/MessagePack.lua:860: in field ‘unpack’
citizen:/scripting/lua/scheduler.lua:338: in upvalue ‘Callback’
server.lua:28: in local ‘ref’
citizen:/scripting/lua/scheduler.lua:277: in function citizen:/scripting/lua/scheduler.lua:268
[ERROR] [MySQL] Check the error above, an error happens when executing the callback from the query : “SELECT * FROM users WHERE identifier=@identifier; {identifier=steam:110000104353179}”
Error running system event handling function for resource LockDoors: citizen:/scripting/lua/scheduler.lua:39: Failed to execute thread: server.lua:17: attempt to call a nil value (method ‘Split’)
stack traceback:
server.lua:17: in function ‘stringSplit’
server.lua:6: in upvalue ‘handler’
citizen:/scripting/lua/scheduler.lua:124: in function citizen:/scripting/lua/scheduler.lua:123
stack traceback:
[C]: in function ‘error’
citizen:/scripting/lua/scheduler.lua:39: in field ‘CreateThreadNow’
citizen:/scripting/lua/scheduler.lua:123: in function citizen:/scripting/lua/scheduler.lua:92
Error running system event handling function for resource mxhandcuff: citizen:/scripting/lua/scheduler.lua:39: Failed to execute thread: sv_handcuffs.lua:38: attempt to call a nil value (method ‘Split’)
stack traceback:
sv_handcuffs.lua:38: in function ‘stringsplit’
sv_handcuffs.lua:4: in upvalue ‘handler’
citizen:/scripting/lua/scheduler.lua:124: in function citizen:/scripting/lua/scheduler.lua:123
stack traceback:
[C]: in function ‘error’
citizen:/scripting/lua/scheduler.lua:39: in field ‘CreateThreadNow’
citizen:/scripting/lua/scheduler.lua:123: in function citizen:/scripting/lua/scheduler.lua:92
Error running system event handling function for resource RappelHeli: citizen:/scripting/lua/scheduler.lua:39: Failed to execute thread: server.lua:17: attempt to call a nil value (method ‘Split’)
stack traceback:
server.lua:17: in function ‘stringSplit’
server.lua:6: in upvalue ‘handler’
citizen:/scripting/lua/scheduler.lua:124: in function citizen:/scripting/lua/scheduler.lua:123
stack traceback:
[C]: in function ‘error’
citizen:/scripting/lua/scheduler.lua:39: in field ‘CreateThreadNow’
citizen:/scripting/lua/scheduler.lua:123: in function citizen:/scripting/lua/scheduler.lua:92
Sending heartbeat to live-internal.fivem.net:30110

i dont know what to do :frowning:

1 Like

You’re completely right. I figured if it was wrong, it would tell me instead of allowing a permission level value be “Owner”…

Thanks,
Caesar