How should I handle firing automatic weapons?

Help and Feedback Scripting Support
#1

right now I’m working on an FPS gun system (very original1!!) but I’m wondering how I should handle firing of the weapon?

I was originally thinking that I could just check for "InputHeld" with UIS and just run a gunfire event, and then the server would constantly fire depending on the gun’s type.

but now that I think about it, I don’t think this’ll work, because I would have to constantly some how get where the camera is looking with only one input

I have thought of just spam firing the gunfire event on the client, and then the server could handle it. but how would I accommodate for the fire rate? and the gun firing type? I don’t know if I’m missing something obvious or doing this very wrong but I’d still like some help

NOTE: my gun stats are handled in a module script inside of serverstorage. i would like to keep it inside of serverstorage for the sake of security and other things, but this makes getting the stats impossible on the client

#2

this should work

local firerate = 10 -- Bullets Per Second
local mouseheld = false

coroutine.wrap(function()
while mouseheld do
task.wait(1/firerate)
print("shoot!")
end
end)()

mouse.Button1Down:Connect(function()
mouseheld = true
end)

mouse.Button1Up:Connect(function()
mouseheld = false
end)
#3

I can’t get the firerate dynamically for each gun because the stats of each gun are handled inside of serverstorage

also using a coroutine for this doesn’t seem like the best use

#4

on a side note is this needed? the reason I want to keep it in serverstorage is because it’s a module and I want to avoid exploiters.

#5

there’s multiple ways to get the Stats inside ServerStorage

like using RemoteFunction

client

local getstatsevent = replicatedstorage.GetStats

local FireRate = getstatsevent:InvokeServer()
print(FireRate)

server

localgetstatsevent = replicatedstorage.GetStats

localgetstatsevent.OnServerInvoke = function()
return replicatedstorage.FireRate.Value
end
#6

I thought of doing this but at the same time I wonder if it’s efficient? especially if the player continues to equip different weapons

#7

It’s okay to use modules and put it in ReplicatedStorage or basically anywhere else… because i believe when you require() a module script, it’ll be saved in it’s current state which means any future change done SHOULDN’T affect it. BUT exploiters can use getgc() which is REALLY complicated to get rid off

1 Like
#8

keep in mind getgc() will always be able to change tables inside ANY localscript so, if you theoratically put it (the settings module) in serverstorage and moved it to a localscript (through event communications) it will still be affected

1 Like
#9

so it would just be easier in the end to put the gunstats inside replicatedstorage? it seems like it’s the same result for exploiters no matter what

#10

If it’s a modulescript then yes, WHEREVER you put it won’t stop exploiters from changing it using getgc() which like I said… returns EVERY SINGLE table in the game (including Enum even)

And as for effectiveness, i would say using coroutine.wrap (the method i showed) would be efficient since Gun Systems like ACS and FE Gun Kit used it

1 Like
#11

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.