Best Practice for Structuring a Combat System

[candid flint]

Hello, I’m currently working on a combat system and was wondering whether it’s better to split it into multiple ModuleScripts. For example, having a CombatServiceClient module placed in ReplicatedStorage, a CombatUtils module in ReplicatedStorage for shared utilities (such as handling cooldowns, helper functions, etc.), and a CombatServiceServer module in ServerStorage so it can’t be decompiled (I don't know any others was to prevent this).

At the moment, everything is implemented in a single module, and honestly, it’s already starting to look quite messy.

[void zodiac]

its fine

idk y ur putting server scripts in serverstorage tho

i never did that gbefore

[slow onyx]

only client scripts can be decompiled

[frosty sun]

you just can't avoid the hackers

just deal with it

and make a good system

[slow onyx]

explain the me how hackers steal server scripts

[void zodiac]

https://media.discordapp.net/attachments/866609423157428224/1127883598947692584/SPOILER_tenor.gif

[last dome]

** You are now Level 5! **

[frosty sun]

why do you want a server script

and basically you can spy the remotes to know what the server is doing

you spy remotes, equip a pet for example and not you got the remote to equip a pet

they're going to know what is going on on the server too

no point

just do safety checks

from there you just can't do anything

[slow onyx]

did you even read the ops first message

he said he put his module in serverstorage so it cant be decompiled

why the fuck would you not just leave it in serverscriptservice like every normal person

if a hacker got access to serverscriptservice then you might aswell just delete ur game

[slow onyx]

I hope you rank up in rl tho @frosty sun

[simple slate]

they don’t

they recreate them based on game and remote and localscript structure

[candid flint]

Another module that's gonna process server validation.

[candid flint]

I can leave module in sss as well lol

[slow onyx]

idk why you would put it in serverstorage

[deft sphinx]

assuming they didn't get copies of too much server code

[deft sphinx]

to my knowledge any replicated code can be decompiled, that means localscripts, modulescripts, and scripts with client runcontext

scripts with legacy or server runcontext are not replicated so cannot be decompiled

[deft sphinx]

if you say so but for those who know, ya you should split your code so client doesn't get any server code - or at least not much of it, e.g avoid runservice:isserver()

if you're starting out though it doesn't matter

coz you probably won't make a popular game anyway and roblox knows it

if they didn't why else would they require id verify or purchase before allowing you to publish games

... and prevent kids and adults working on the same project at the same time

[void zodiac]

ok

[candid flint]

@deft sphinx
to my knowledge any replicated code can be decompiled, that means localscripts, modulescripts, and scripts with client runcontext scripts with legacy or server runcontext are not replicated so cannot be decompiled

Alright, thank you so much! I appreciate it

[simple slate]

Any client script or module script placed within places that the client can access can be decompiled, including things placed in replicatedstorage workspace etc etc

[candid flint]

That’s what I said in my post

[slow onyx]

why would you place a module which you need server sided place in server storage tho

[candid flint]

why not?

[slow onyx]

jsut leave it in sss like a normal person