What can i do to optimize game so it can handle a lot of players (50-100)

Help and Feedback Scripting Support
#22

I agree with this. You can have the most basic game (baseplate, any roblox starter template) and there will always be stuttering/lag

1 Like
#23

I am not quite sure about raycasting and ā€œheartbeatā€. That is something I would have to look into.

1 Like
#24

ok thx, but now i have another problem with second most laggy part of the game which is projectile system, it uses RunService heartbeat, i also pre-calculated that there shouldnā€™t be option to fire more than 1000 bullets per second, 2500-5000 in air, but it still lags when i spawn those rays

I tried parrarel luau, but itā€™s worse than simply not using it
Also i use task.spawn when casting bullet

#25

Is there anyway you can just minimize the bullets in the air? The less in the air/visible, the less lag you should have.

And if parallel luau is making your game worse, then just leave it out completely.

1 Like
#26

Maybe iā€™ll show math that i did to calculate that

Players * Highest_Fire_Rate * Default_Lifespan

50 * 25 * 4 = 5000

Also, iā€™ll use unreliable remote events to replicate bullets to client, if bullet will be too far, client will simply Parent it to nil

1 Like
#27

I think I can understand the numbers but can you explain what the 50, 25, and 4 represent?

1 Like
#28

50 is max players cap, i donā€™t think server would have it every time, so i aim at 30-50, probably more on private servers or big battles

25 Is how many bullets fastest weapon can fire per second, i donā€™t think that many players will use it due to how much ammo it requires, also probably make it expensive, so most of the time player will fire 1-10 bullets per second

4 is default lifespan for most projectiles, i plan on making them fast, like 50 studs per second or even 100, So 4 should be good for most projectiles

#29

I donā€™t get why you need to like fire remote event each frame if the bullet is pre calculated

1 Like
#30

It isnā€™t, i pre-calculated maximum possible number of bullets in the air

Bullet itself uses heartbeat, also not remote event but unreliable remote event

#31

I just donā€™t understand why you need to gives the position the bullet each frames. If you give the force and the direction when you create it Iā€™m sure you can determine the position of the bullet on the client

1 Like
#32

I donā€™t do that, because i will have to calculate bullet twice, which would be very costly, even if on client, this is why i think sending unreliable remotes is better solution

#33

So what are you sending each frames ?

1 Like
#34

For bullet visuals, i send Id of bullet and position, i realized i can send position as Vector3Int16 to reduce itā€™s size by half

#35

I feel like you are overcomplicating the process.

1 Like
#36

i feel that there might be 5000 bullets in the air at one points, of course itā€™s unlikely, but still there is possibility, and i donā€™t want to make the game lag a lot

1 Like
#37

As I and @26mmiller said, youā€™re doing something wrong if you are firing every frames a Unreliable remote event for visuals. I would just make the calculation of position at FIRST frame and give to clients that, bullet speed,bullet directionā€¦Like that you could even make client prediction

2 Likes
#38

Iā€™ve decided to change a lot of stuff, and cast bullets on client to reduce server load and network load, sending only 2 remotes with number and a vector3

2 Likes