One is to stop the script ( Ctrl Z), get the PID of the script and send SIGKILL to the process group. Local Handle = Tool.You have few options. Script in the Tool, directly descending the Tool If Child:IsA("ObjectValue") and Child.Name:lower() = "creator" then Humanoid.ChildAdded:Connect(function (Child) Let's assume that tags are added to the Humanoid Increment stats of players who tagged the humanoid Local Humanoid = script.Parent:WaitForChild("Humanoid") You can hard code the Humanoid's name here, since it shouldn't change Script in the NPC, directly descending the model Your tools should only be concerned with carrying out their specific functions, not handling data where it shouldn’t be. You should handle death states and incrementing of data from the Humanoid itself, whether you have a module system or each NPC has a script. In terms of handling death counts, I would advise against using the solution that 12904 proposed. It’s completely up to you how you go about it. You can also create your own tagging system just as easily and not use ValueObjects. That was fully ported in Lua - what was deprecated was the KOs count on a user’s profile being incremented from those creator tags.Ĭreator tags still work, though that’s up to the developer how to modify. The creator tag system was quite literally a tagging system that was intended to tag humanoids to be able to determine who was involved in a Humanoid’s damaging (or death). I head the creator aka tag system doesnt work anymore and was deprecated in 2015
0 kommentar(er)
