Just give a fair warning that modding is unsafe
Just give a fair warning that modding is unsafe
RUltimately by allowing for modding of any sort you run that risk, he should disable the ability to enter official/unmodded/different mod configuration servers while modded, give a fair warning to the user explaining the potential problems with mods, and disable modding support by default
RProviding a safe and secure place to download scripts is a better idea IMO
RUltimately you cannot and should not be responsible for third party content
Ralso happy birthday
HYes i'm very aware of those. I'm currently doing this to make a new open source game engine that i would personally use but also let others use if they want
Rthen even more so, dont be safe
Hyes
Heven unity games are so easily hacked
Hand can be turned back to source
RLOL yeah just the nature of the beast
HIL2Cpp is another thing tho, it's preventing turning back to source
Hbut hacking is still possible
Hjust no more reselling the game source
Rbut its turning into into C++
Hyeah
HImplementing something like that would take ages xD
RYeah'
Rthats why you dont
Hyeah
SDon't trust anyone.
SThat's how you should implement multiplayer
SNot set his position to whatever he said (typical scp:sl game)
Pyou shouldn't care about your game being turned back to source. anyone passionate enough will be able to read the assembly itself and lift it up to usable code no matter what the language or obfuscation.
Pif you are distributing anything that can make a user's machine do something, that user will be able to replicate what that does.
L^
Lwell in some countries its illegal to reverse engineer like that, but in most, its legal and people will
Pin those countries using a IL decompiler would also be illegal 
Pas it's exactly the same
Liirc i think it is yeah, reverse engineering code even clean room isnt really considered legal, as you dont own rights to said software to do so, but im no legal expert, ive just heard stories of people being arrested for this
SCompany gave you assembly.
SIt's your choice to run it, or read it.
Preading assembly is fine
Pbut in almost every case you don't have a license to transform it
Pso you don't have a license to turn IL to C# (unless you do obviously, as is the case for open source)
Petc
CNobody even has to read assembly with (like probably 2009 and up) tools.
CIDA and Ghidra can both decompile (not just disassemble) binaries of nearly all flavor.
CC/C++ vs C# for RE protection is largely just people squabbling over semantics in my opinion (as someone who did a ton of old Xbox/Xbox 360 RE and has experience in other RE projects).
CClean room is explicitly legal in most places. ReactOS and Wine would have been squashed by Microsoft had any part of their operations been illegal. :)
Lkeyword most
Li meant some countries
Las said in my first message
CI guess some random country might present a legal issue.
CBut we are all likely outside their jurisdiction. :))
CSo long as you do not distribute their code in any form, only send patches or use clean room documentation you are pretty much clear. Your own patches are your own IP.
HTrue. Which is why i'm using C# even though I know it's super easily decompiled or even turned back to source
S
Pyes it's not published yet
Pyou have to build it yourself for now
R