Re-enabling backpack not working

Help and Feedback Scripting Support
, ,
#1

  1. What do you want to achieve? Keep it simple and clear!
    I need a solution/fix to this problem.

  2. What is the issue? Include screenshots / videos if possible!
    Basically, when I punch a player in my game I set their toolbar to become completely disabled by firing a client event and disabling the backpack and then re enabling it after a certain amount of time.
    So in this video it gets re enabled without waiting the timeAmount: https://gyazo.com/c9046eee69db1ae3fb44b26baabf3e02

    And in this video it gets re enabled perfectly waiting the perfect timeAmount: https://gyazo.com/3d5e20805e7bd634e9427bf1474b6cbf

  3. What solutions have you tried so far? Did you look for solutions on the Developer Hub?
    Yes, I have looked for solutions couldn’t find any :confused:, but I also have noticed that the first time you punch your toolbar gets disabled perfectly and re enables perfectly but the second time and each time on it doesn’t work perfectly.

This is the script involved with disabling then re-enabling the backpack:

local coreGui = game:GetService("StarterGui")
script:WaitForChild("DisableBackpack").OnClientEvent:Connect(function(timeAmount)
	coreGui:SetCoreGuiEnabled(Enum.CoreGuiType.Backpack,false)
	wait(timeAmount)
	coreGui:SetCoreGuiEnabled(Enum.CoreGuiType.Backpack,true)
end)

Sometimes it works perfectly and waits the designated time period but other times it disables then immediately re enables completely ignoring the timeAmount variable :confused: If someone has a solution please please let me know. Thank you!

#2

That would suggest to me that timeAmount is nil, meaning wait is just as assuming you want to wait the smallest amount of time possible.

Check your code for firing the client event, and make sure that it’s definitely receiving a number every time. Maybe have it print the value of timeAmount each time it fires so you can check its receiving the right data.

Either that, or its being fired several times, causing the first event’s re-enable code to run directly after the second one has disabled it. Again, printing to the output will tell you if it’s firing multiple times, and whether you need to add a debounce.

1 Like
#3

Alrighty, I’ll be sure to do that! Although I know that the timeAmount variable is being given because it works sometimes. What I think is that it’s being fired multiple times which I will check right now, thank you!

#4

Ok, so basically it doesn’t get fired multiple times and the timeAmount variable is printed perfectly how it should be. What I think is that the way the system works is when you punch another character and it finds the “Block” bool value it destroys it and fires the client and basically my friend and I tested this in game when I perfect blocked him it worked perfectly and his tool bar got disabled then re-enabled and when he starts to perfect block me my tool bar doesn’t gets re-enabled too quickly completely ignoring the timeAmount variable.

#5

Also, timeAmount wouldnt be nil it just sometimes it waits half the time other times it doesn’t

#6

Also, if this helps I have provided the code below where the client gets fired:

local c = Player.Character
local e = game.Players:GetPlayerFromCharacter(c)
if enemy:FindFirstChild("PerfectBlock") then
    enemy:FindFirstChild("PerfectBlock"):Destroy()
    c.HumanoidRootPart.Anchored == true
    e.PlayerGui.DisableGuis.DisableBackpack:FireClient(e, 2.975)
    wait(2.975)
    c.HumanoidRootPart.Anchored = false		
end

Also, when I was printing the timeAmount variable it stayed consistent even though the wait(timeAmount) wasn’t waiting the same amount. Again, what I have noticed is the first time the event is fired on one player it works perfect for that player and if it’s fired on another it doesn’t work at all. Or it could just be completely random! I honestly have 0 clue :frowning:

#7 
local coreGui = game:GetService("StarterGui")
script:WaitForChild("DisableBackpack").OnClientEvent:Connect(function(timeAmount)
	coreGui:SetCoreGuiEnabled(Enum.CoreGuiType.Backpack,false)
	wait(timeAmount or 2.975) -- If 'timeamount' is nil it will wait 2.975
	coreGui:SetCoreGuiEnabled(Enum.CoreGuiType.Backpack,true)
end)

You can use a simple ‘or’ statement to account for if “timeAmount” is nil

#8

Alrighty thanks, I tried it out and it still doesn’t work :confused: The thing I have been noticing is that the first time the client gets fired it works 100% fine, works perfectly but each time after that it doesn’t wait 2.975 or timeAmount. I also printed the timeAmount variable like @cxmeels told me to do and it prints 2.975 :confused: it’s so weird…

#9

Do you think this could be an engine bug? Like it should be waiting the correct time amount and it is when its first fired but all other times after that it isn’t…

#10

All I can suggest really is trying a custom wait implementation:

local function wait(waitTime)
    waitTime = type(waitTime) == "number" and waitTime or 1
    
    local RenderStepped = game:GetService("RunService").RenderStepped
    local now = os.time()
    
    while os.time() - now < waitTime do
        RenderStepped:Wait()
    end
end
#11

Honestly, I’m pretty sure it’s an engine bug I’ve tried 3 different ways of disabling it while waiting the 2.975 seconds and it works the first time and the next it doesn’t. I just made it so if you equip a tool while stunned it un-equips so yeah, thank you, and thank you as well @det3rr

1 Like