AntiCheat Plugin
-
On top of that, it’s not like w0dk4 released the whole source full-front.
-
Testing the anti-cheat plugin goes very well so far. I installed it back on Tuesday and the server is 2x-3x more stable for the past 3 days now, but maybe it’s just coincidence, I don’t know.
There are some issue reports but we haven’ tested the deeply, and they are quite rare (except the jumping issue) so the problem might be elsewhere:
- jumping between certain systems killed the player and displayed the ‘player was killed by an admin’ or people just appeared on the location where the F1 jumphack would place you with half hull gone (they didn’t attempt to do the F1 jumphack). But with disabled speedmod check it seems ok now. The speeds checks were set to 110% of the original values. I’ll try to get more details (in which systems it happens etc.)
- a player reported they can’t buy a scanner (gets kicked) - but only one player had a problem with that, could be a cheater, I have to investigate more
- some people reported reduced firing range of some capital ship turrets (with range over 1500) - didn’t test myself yet
- some people reported that some mining clouds only drop 1 unit of whatever you can mine there instead of the normal amount. Igiss tried to support mining in Discovery Mod by increasing the amount of units dropped by asteroids. Again I haven’t tried myself yet with and without the plugin activated in a certain area.
- some people reported more lagging at the client’s side
And that’s all so far. As I said most of them have to be tested yet to ensure the problem doesn’t lie elsewhere. So far I would say good job working well. Oh and I have to try the Justice Beam Mod.
-
I have no idea why, but Freelancer Server crashes stopped appearing in the event log for some reason. Only perflib error entries are there in the time of each crash. I’m planning to reinstall the server (under 32bit version of Win) soon so I’ll post them later. Right now I can only say each crash is followed by massive (2GB) VM allocation of the flserver.exe process right before it crashes. Looks like some unsolved memory leak to me. But that’s not related to the AC plugin, on the contrary, our server is much more stable with AC plugin installed.
Now I am almost sure that the reduction of units dropped by asteroids is caused by the AC plugin, would it be possible to switch it off in the next versions? We have some mining player factions and they are crying…
The RefireRateTolerance in percents would be also nice, we have some chain guns with high refire rate and it could cause problems there. Setting RefireRateTolerance to 2 could help there a bit, but then the guns with refire rate 2 would be allowed up to 4, which is quite a lot as well…
-
I’ll have a look at the issues… at the moment I have limited time though.
Anyways, you can disable the item spawn protection in the flhook.ini (itemspawncheck or something) for now, but that would again allow any sort of spawn cheat (there are really bad spawn cheats possible).
-
Sorry jase, no ideas, it runs on discovery RP server and there are a lot of caps there. No problems.
On another note, possible exploit:
Excuse me pls sir I want to tell you something about your Anticheatsoftware.
Ok I want to be true, try to cheat and im sorry for that but now comes the big surprise i already had the money after get kicked from your software!
I cheat more money with Gamewiz 32 and after that i use the /givecash command to give it to another char it worked. I was scared and happy at one time I transfered the 270k to Hans_Westerman my Char which is
sanctioned from you.
So pls dont ban me for trying to cheat and pls pls pls fix that i like playig here and dont want to see any newbie with a Battleship cause he can cheat it.
yours sincirly ManuelMaybe banning instead of kicking after the cheat detection? Can’t give you more details on how he did it though, don’t know them…
-
The FLServer cheat detection (which is still mostly used when the player is docked) only kicks in when the player undocks.
Im not sure if I will ever include realtime money cheat protection when the player is docked since its tedious. Therefore, the givecash plugin should be overworked, i.e. only allow transactions while in space, or, before a transaction, call the flserver anti-cheat functions on the sending player.
-
The FLServer cheat detection (which is still mostly used when the player is docked) only kicks in when the player undocks.
Im not sure if I will ever include realtime money cheat protection when the player is docked since its tedious. Therefore, the givecash plugin should be overworked, i.e. only allow transactions while in space, or, before a transaction, call the flserver anti-cheat functions on the sending player.
Looks straight forward to fix. I’ll have a look and see what I can do.
-
Additional a feature 2 disable the give / send cash for certain systems
- as FLShell does - would be nice.
(Prison )
- as FLShell does - would be nice.
-
is there a way to disable FLserver cheat detection?
lol, im noty sure, but if one one is gunna post a response, this thread is going to be put in the private area for server owners. not exactly a wise idea to have a public discussion on how to disable anti-cheat when there are still a number of cheaters about
-
I think he meant the 1.1 FLServer cheat detection and how to disable it as a server admin.
To make it short: There is no functionality for that. FLHook requires FLServer with v1.1. And I dont see any use for such a function. If you wanna cheat on your own server, fire up an 1.0 server
-
Just out of curiosity… I haven’t had the time to actually play with FLHook’s plugin version on a server and try to fire at its A/C plugin, but I wondered how the software reacts to cheats: does it ban the cheater? kick him? nullify the effects of the cheat?
-
- Fix for an FLServer bug that would cause a servercrash every ~4000 logins (or ~2000 logins and ~2000 deaths)
If you have a lot of crashes at the 0x93b01 offset in content.dll, this will help you!
Could you please share this? Very annoying crashes ;D
- Fix for an FLServer bug that would cause a servercrash every ~4000 logins (or ~2000 logins and ~2000 deaths)