OOP Combat System/State Combat System

[ZensStarz (ZenDolla)]

I decided that I got bored of the combat I was working with. It wasn’t necassarily bad, but the feeling wasn’t there persay. I didn’t enjoy it the way I thought I would’ve. So, I want to remake the combat completely, from the framework to the small little features that make combats unique, but the issue is, I don’t know how I should go about this, if I should attempt OOP Combat, where to start with it, either having the main combat as one class, or have combat features split in smaller children of the bigger class known as combat. Or learn how to use a state manager (which, I have no idea how to do). If I could get some assistance with this, I would appreciate it so much.

Kind of understand a state manager, just don’t know how practical it’d be to script.

[dthecoolest]

OOP is good if you componentize it. This means following single responsibility principle where one script only does one thing so you can keep track and make changes easily. Although don’t worry even if something goes wrong with organization you will usually either way start from scratch in order to clean it up. It is also good for standalone systems which can be shared easily since it is common place.

Script Structure and Communication Advice

Consider OOP composition based programming. Similar to your diagram, one main script and many components into it. You will find that even the components require information from other components which is solved by passing the variables from component → main module scripy → component Also consider ECS: Example structure with systems and components: For cross server there will basically have to need two versions server and client. The advantage of both ECS and OOP composition is that you …

ECS from my understanding is ““Kind of”” like OOP but more stricter with componentizing everything. Here is an example of a status effect system with it:

How would i implement a modular status effect system?

I highly recommend ECS. However, on a side note you could achieve the something with OOP as long as you use components, one module script only does one thing with a single responsibility principle. Here are some code examples to illustrate Entity creation of player with pure data local npcEntity = world:Entity() npcEntity :Set(HumanoidComponent(Instance.new("Humanoid"))) npcEntity:Set(PoisonComponent(5)) --You can add infinite amounts of components hence modular npcEntity:Set(StunComponent(10…

@ZensStarz

state manager

You can use a finite state machine. From my understanding it’s just an if statement check most of the time.

I have used it in here in order to replicate humanoid states and play animations even though the humanoid is platform standing where normally animations are disabled.

PhysicsCharacterController | Mover Constraints based character controller

Just a small project that I initially made in 2-4 + hours purely for learning purposes that I wanted to share since I see not a lot of example projects for character controllers here on the dev forum the only one other being @EgoMoose platformer controller. However soon later found out it was a lot of fun to play with and thought to modularize it further into a full blown project. Objectives: Similar to default humanoid controller movement running Humanoid autorotate Controllable fric…

[ZensStarz (ZenDolla)]

@dthecoolest

OOP is good if you componentize it. This means following single responsibility principle where one script only does one thing so you can keep track and make changes easily.

I had to go through the posts to understand what you mean at first, but i finally got a decent understanding, but somehow that made me a little more, but its probably a simple answer. What you are considering is for me to keep everything split and have them handle what they need to handle, e.g Damage Interpretation, Stun Handler, Animation Handler, VFX/Visual Effects (Honestly dont know how I would further split combat systems.)

And also with this question, from the way you explained ECS could simply be a way to further organize this, so if I made all of the states attributes, I could split it up into their own if statements for certain things to happen accordingly?