Help Structuring a Combat Game

[knotty terrace]

Hello, I would just like some guidance on how I should structure my combat game and/or some references I can use.

My game will be an arena fighter like ABA and Shonen Unleashed for reference.

A general idea I made so far is having a base handler that uses sub-class managers like the combat manager that acts like a service for getting starting the moves and abilities when needed, and a sub-module for handling stunning since I've heard stunning via client would make a more responsive feel.

But after that, I'm generally confused on how I should handle the character's and structuring and organizing moves and abilities.

Sorry for the vague questions but I've been overcomplicating this process a lot and overall confused on where to start since I haven't created much progress for a little while now

[cerulean tapir]

attributes

saves the day

[coral finch]

Every abilities should has their own module

I'd split between configurations,utilities, and a goodsignal to maintain communicating

[fair kiln]

+considering every exploit possible(gona be a pain ngl)

[wintry robin]

simplest 😭

[knotty terrace]

Thanks for putting the time into this

I have a problem of over-engineering and over-complicating things so I just needed help narrowing down my scope of what I should do

Thanks for the comprehensive rundown of what to do

[knotty terrace]

for all systems, it just boils down into different scripts working with one another

So I can create custom modules that acts as services or raw data

Examples include:

• CooldownService
• Hitbox Service
• Character Service
• Character Data (code that stores information for each character)
• Move Data (Code that stores information for a move/ability)
  -etc.

My main problem was thinking of a framework/structure to tie all these components into one another

[wintry robin]

The point of this is so it’s as easy as possible to add new stuff right

[knotty terrace]

Yes

[wintry robin]

I’ve made systems like that for casting abilities, but they are much simpler

[knotty terrace]

And thats fine

I have a problem of over analyzing and over engineering my code

Causing me to not finish games and have development issues due to that mentality

[wintry robin]

I got the if it works it works mimdsey

[knotty terrace]

That's fine but you should still keep in mind of things you add later

[knotty terrace]

Scalability will be your issue with that mindset

[knotty terrace]

but as a quick tl;dr

He was explaining his process of organizing his game and how he structures his code

"ClientCombatManager that handles inputs local stun, local movement lock and playing animations/VFX instantly so everything feels snappy"

[wintry robin]

I usually make a broad system, like attaching to parts together. Then test it with the use I’ve thought of an store the system just incase I need it for something else

[knotty terrace]

He creates a central module that handles the main inputs for the client, applies stun, and plays VFX

[wintry robin]

Why is walkspeed on client? So if an exploiter sets theirs high you can just reset it?

[knotty terrace]

Make the game feel smoother

Player's can already do that if they're exploiting

There would be no input delay from activating a move

So the gameplay can be more exact

[wintry robin]

Because client and server take the players ping in time to communicate