Need advice on how to plan an efficient way to handle a possibly very highly intensive server system

[junior tapir]

Hello, this is my first time posting here. I’m not asking for any specific coding help, I’m just looking for someone with enough experience to give me advice for how to plan out this possibly very highly intensive server-side manager system for my game.

The system would handle collision detection for every unanchored part in my game. I’m thinking of something similar to the hit detection system that Natural Disaster Survival has, where if a part hits you at a high enough speed you would take damage.

I want to scale this system for a very large map and this system would not only detect collision and call possible damage for any player, but also for any object(parts) in the game. So basically, if any unanchored object in my game moves at a high enough velocity I want to monitor it for any possible collision with another object, and if it collides with another object(thinking about collision detection using parts in bounds) I want to compare the hit object’s resistance with velocity of the projectile-like object that hit it(would also consider the mass of the projectile-like object), and if the energy/velocity is greater enough than the resistance of the hit object then I would apply an impulse(impulse is based on difference of velocity and resistance) to the hit object and damage it too(also based on velocity and resistance ← for any part, calculation would be different for a player’s HP). For a player, they would get damaged via humanoid HP, and for an object(part) it would get damaged via storing the max hp ← most likely mass, subbed by the damage – or current hp(if already damaged) subbed by the damage – the hp for any part (that is damaged) would be stored in a globally accessible table.

There are various possible problems related to resource management, but one of the biggest ones is applying a monitor to any part that is moving at a great enough speed. Keep in mind, I plan to have thousands of parts within my game, and the map would also be huge too.

I also thought of managing this via a server chunk system. A possible solution I had to monitoring these parts would be to use clients that would send info to the server if a part within their loaded range is moving at a high enough velocity and the server would then handle this part. I plan to have the game host up to 100 players though, with a huge map and a ton of objects...

[neon basin]

tl;dr you're trying to improve performance on something that doesn't exist yet? so it can .. not do anything even faster? start with a working example, performance comes second.

oh you just want collisions, so yea roblox doesnt expose much of the physics api but .touched is the closest thing you're gonna get

each object you are tracking collisions on would probably be suitable for an actor and .touch:connectparallel so only events that do anything run on the main thread

[junior tapir]

I’m trying to figure out a good plan to make this system before making it. It’s not wise to code a system without properly planning it. The system could possibly need to monitor 200 objects at once.

[tawdry sinew]

keep track of active(moving) objects

cleanup object references that you dont need anymore

im not sure how intensive creating a connection is but you could disconnect the connection that searches if it hits a humanoid and create it when it starts moving again

[junior tapir]

Yeah I feel like a major problem is how to efficiently keep track of all moving objects. There would be 1000s of objects in the game that could be actively moving or not, and I would have to loop through this constantly to figure out which ones are moving to track

Idk how the server could handle a loop through 1000s of objects constantly to see if there are any with a high enough velocity to track