New BattlEye features for server admins

[.kju [PvPscene]]

I guess $able cannot determine if the code is from the mission or an addon/runtime code, can you $able?

[[KH]Jman]

There appears to be a character limit on the say command which is quite low. If the text is too high it disconnects BERcon.

[$able]

Hi
I am getting kicked from my Dedicated server used this from 1st post
What did I mess up ?

See the following scripts.txt example:
Code:
1 createVehicle
1 setVehicleInit
3 serverCommand
4 godmode
7 Bo_Mk82
6 #shutdown

That was only an example. It doesn't mean you should use it (especially with kicking).

[nuxil]

Meh, am not happy with this.

How can you be unhappy.. its not something thats forced down your throat.. its a option free to have enabled
this can be usefull for server runing other missions than Domi

[$able]

You haven't messed up anything, the code is from a FSM in Domination which checks if an user is logged in as admin and then adds extra admin tools (like spectating and admin dialog).

Meh, am not happy with this. Many missions use those commands on the client side and it just shows the heart of the problem. There should be some kind of trusted environment where execution of all scripting commands is possible, for example from mission scripts/folders as you can't manipulate MP missions.

Xeno

There won't ever be a trusted environment, because you can directly change existing scripts or inject code in memory without even dealing with PBOs or the signature check system (there are hacks that do exactly that).

If there are problems, just scan for more specific strings (for example, you can even add a space after "serverCommand" so "serverCommandAvailable" isn't picked up) or disable kicking. There is a reason this is fully customizable.

[Xeno]

How can you be unhappy.. its not something thats forced down your throat.. its a option free to have enabled
this can be usefull for server runing other missions than Domi

Read again what I wrote. It's the wrong approach to the problem and not related to Domina, Warfare or whatever mission.

There won't ever be a trusted environment, because you can directly change existing scripts or inject code in memory without even dealing with PBOs or the signature check system (there are hacks that do exactly that).

I'm aware about that for a long time already
The question remains, why is it so easy to inject code ?

If there are problems, just scan for more specific strings (for example, you can even add a space after "serverCommand" so "serverCommandAvailable" isn't picked up) or disable kicking. There is a reason this is fully customizable.

Then please change your example above or add a better explanation because otherwise we will see lots of players getting kicked in the next time because some server admins simply take what they find as example without even thinking about it or knowing what's going to happen.

Xeno

[nuxil]

sorry. i misread.

but you should know. there is no such thing as a trusted enviourment. even that would be exploited.
btw. wasnt the command #servercommand Kick etc etc disabled/ignored is patch 1.56 or later by bis,i may be wrong. if thats the case. no need to look for thouse commands.

[Dwarden]

this is optional tool for administrators, not much different from CVAR checkings in PunkBuster ...

hence if You wise enough all You need is logging and analyze the result post mortem
and then ban the BEGUID of clear offenders

only if you have mission and locked content environment t
then You can use kick on the commands which You know aren't needed for missions You run

[Tonic-_-]

Like Dwarden said, it's optional.

I myself would much rather log common things such as 'Bo_mk82' or something that is widely used in missions and then for the other stuff that we obviously won't be using in our missions like 'Loki' or 'Gerk Menu' just simply kick for it.

[kylania]

Just because it's "optional" doesn't mean it shouldn't be improved or clarified.