there is at leats a partial solution:
use client validation:
for example:
bob is a legit player, and he meet kevin the hacke r in space.
now both bob and kevin have various metrics on each other ship equipment etc....
so bob client is able to check if kevin ROF / damage per hit / damage taken per hit is consistent or not.
if kevin does hack, bob client can detect it (at least some of it like instadamge / rof alteration / godmode).
should bob client detect it, it'll automatically upload detailled log to FDEV server.
if kevin get reported in that way by say 5 different client -> bye bye kevin
this way, fdev server would only have to deal with very suspicious player, most of the job being done by the player themselve, but automatically, this way there is no risk that a player fail to report, report it the wrong way etc....hence the detection process is way faster, and should a player hack, he would get punished rather fast, wich would be a deterrent for further action / hacker
now what happen after 5 detection can be variable, player is banned, stuck in solo until a fdev review the case etc....
but at least he's not ruining legti player
preventing hack is good, but ultimately inneficient / impossible, especially with a p2p model.
however, you can make them useless if a player is punished within the 24h of using it
Last edited:
