Literally woke up today, did not change any of my code, and when I start up my game I get a million prompts saying
What does this even mean and how do I fix this.
roblox gotta fix they’re code, happened to me too today
8 Likes
I noticed this error when I was trying to debug a touched event. For some reason it worked in regular play mode, but when I made a test server with 2 players, the touched event just wouldn’t fire. I put some print statements inside the touch script to see what was going on:
this was the original script
local touchpart = script.Parent
local touchedevent = game.ReplicatedStorage.TouchedBindableEvent
touchpart.Touched:Connect(function(part)
if part.Parent.Humanoid then
touchedevent:Fire(part.Parent)
–Sends player model
end
end)
the part.Parent should be player model which should have a humanoid in it, but it wouldnt detect a humanoid for some reason so i put prints outside the if statement and it detected:
print(part) - this printed “LeftHand”
print(part.Parent) - this printed “jubileejazz”
print(part.Parent.Humanoid) - this threw the error
“Property “Animator.EvaluationThrottled” is not currently enabled. (x6)”
From this error im guessing when the player is moving and animated, its body parts temporarily become a descendant of “Animator” and not “jubileejazz”, due to some kind of background process. Roblox in an attempt to not break any old games probably forced the engine to pretend like the Animator doesn’t exist, so the name of “Animator” probably is set to “jubileejazz”, hence part.Parent prints the player name, but indexing into Animator to find “Humanoid” breaks
That’s just my guess, but if that is the case, somebody probably did some sloppy coding and made indexing into bodypart.Parent return an “Animator” object named after the player, instead of pointing to the actual player object. For whatever reason, the EvaluationThrottled property of Animator is named “Humanoid” so indexing into Animator[“Humanoid”] pulls out EvaluationThrottled and errors.
I think it is a fairly common convention to check if a touched event is fired by a player by using an
seeing if part.Parent.Humanoid exists, so maybe that is why your game kept giving the error
temporarily solution: I just changed the if statement to check for
if part.Parent.HumanoidRootPart then
print(“hello”)
end
and this works
5 Likes
so it most likely is a roblox bug then…
3 Likes
I am able to replicate the issue. This occurs when you are creating animations using the new Animator class during runtime and debugging the code. Whats strange is that if you create the animations during AnimationController then the error does not exist.
But as we know AnimationController:LoadAnimation and related animation methods are deprecated and not recommended.
So hopefully roblox can fix this
4 Likes
I just started using the HumanoidRootPart’s position, and it started giving me this error many many many times. It doesn’t seem to effect anything it is just annoying.
1 Like
Yeah, Ive been getting this issue too.
Im currently making a combat system and theres Dummies, Theres no animation for the dummies nor will i plan adding one soon, all the dummy move to random spots ontop of baseplate.
The moment i kill any of said dummies, it just throw this error for some reason.
Really do hope roblox fix this issue
4 Likes
Sorry if i’m late, but you need to do if part.Parent:FindFirstChild("Humanoid") then
1 Like
Ran my code, no bug. went to bed. woke up. open studio. bug appears. has to be roblox!
13 Likes
Some part of Roblox’s engine code must be trying to use a property that is technically already implemented but randomly disabled for unknown reasons.
If you want to silence this strange, pretty unhelpful error message, set the "AnimatorIsThrottledPropertyEnabled " DFFlag to true using Roblox Studio Mod Manager or something similar.
25 Likes
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.