Categories

• Scripting Helpers Discussion, Suggestions and Ideas
  

  A place to talk about all thing Scripting Helpers and to submit your ideas for the website

  179
  Topics
  993
  Posts

  A

  @Vortex_Vasne Can you tell me the main idea/genre?

• Commons
  

  Post about anything within the site rules here. Basically off-topic.

  285
  Topics
  1866
  Posts

  

  @partytonic im not sure why you have a while loop for the humanoid health. I would just use the Died event. Secondly I would not have a script per NPC. Instead have a module with the code that will be shared.

• Cool Creations
  

  Made something cool? Let us see it!

  169
  Topics
  1153
  Posts

  

  ==============================
  while wait() do
  if script.Parent.Parent.Name == "Backpack" then
  local Chararacter = script.Parent.Parent.Parent.Character

  if Chararacter then local UpperTorso = Chararacter:FindFirstChild("UpperTorso") local Weapon = Chararacter:FindFirstChild(script.Parent.Name) if UpperTorso and not Weapon then local WeaponOnLeg = Instance.new("Model") WeaponOnLeg.Name = script.Parent.Name WeaponOnLeg.Parent = Chararacter Handle = script.Parent.Handle:Clone() Handle.Name = "Handle" Handle.Parent = WeaponOnLeg local LegWeld = Instance.new("Weld") LegWeld.Name = "WeldOnLeg" LegWeld.Part0 = UpperTorso LegWeld.Part1 = Handle LegWeld.C0 = CFrame.new(1,-1.42,0) LegWeld.C0 = LegWeld.C0 * CFrame.fromEulerAnglesXYZ(math.rad(-250),math.rad(-271),-20.5) LegWeld.Parent = Handle end end else if Handle.Parent then Handle.Parent:Destroy() end end end

  i think it works on r15 and r6 make sure you put this on script not localscript on the sword or gun you made. pretty simple Enjoy!

• Tutorials
  

  User-created tutorials for various topics related to ROBLOX

  140
  Topics
  708
  Posts

  

  Whenever you have a problem, you should debug it first before asking on the site/Discord. This can be done using print debugging and by using the Lua debugger.
  Here's an example of some code that won't work, and in here, our goal is to create a part for each player with the part's name set to the player they belong to's name.

  --serverscript spawn(function() --this is created just as an example for debugging. you shouldn't create a new thread/"spawn" this function just for this Instance.new("Part").Parent = workspace end) local foo = require(game.ReplicatedStorage.SomeModule) for _, player in pairs(game.Players:GetPlayers()) do foo(player) end --modulescript "SomeModule" wait(20) local part = workspace.Part return function(plr) part.Name = plr.Name end

  Here, the part in workspace doesn't seem to be renamed when we want it to be renamed. To start debugging, you should first check that the script's Disabled property is false and if not, make it false. Now, you should step through the code to see what's going on. (Note that this can be achieved by using print, but using the Lua debugger is easier.) You should set a breakpoint on the top of your script on line 1 (for the purposes of this tutorial, line 1 will mean the line which is the highest) by either clicking to the right of the line number or by pressing F9. Once you start the game, you should notice that it opens the script with a yellow arrow on the breakpoint marker you made. You can either press the Step In (steps normally but if the line calls a function, it "goes into" the code in the function too), Step Over (goes through each line as it's ran), and Step Out ("goes out" of a function). When we use the step over feature, you should notice that the yellow line disappears when we require the module. If we start the game again and step into the require, you'll notice that it doesn't go into the module's code and actually goes to Instance.new("Part").Parent = workspace

  An important thing to know when debugging is how the functions and methods you use in your code actually work. In this case, we use spawn to set the parent. When you create a new thread with spawn, it only runs once a yielding function is executed like wait. In the module, we call wait and thus it runs the code we put and passed to spawn.

  Afterwards, we find that the yellow arrow disappears again. To debug this further, put a breakpoint in line 1 of SomeModule. Now we can restart the game and press the Play button once we hit the breakpoint in the script to go to the breakpoint in the module. The module seems to stop running code when we run wait(20). Although this is obvious in our code we set up, it may not be very obvious in actual code what is yielding long enough to seem like it's freezing (eg: web/api calls).

  We should remove the random wait we put in our code for no actual reason because this is a bad solution which is unreliable and may wait longer than needed, For example, if some other code runs during that wait and doesn't let Instance.new("Part").Parent = workspace run, there'd be an error. We should instead take advantage of the events and methods Roblox provides. In this case, we should replace

  wait(20) local part = workspace.Part

  with

  local part = workspace:WaitForChild("Part")

  Note that you might see repeat wait() until workspace:FindFirstChild("Part") used. This is known as busy waiting and is usually bad practice as WaitForChild exists and this is inefficient.

  Once we step through it again, it all seems to work. In order to simulate a real scenario, start a test server with 0 players. Then, click 1 player and press the same button again to have a new player join the server. You'll find that the code just makes a part in Workspace and doesn't rename it. You can't use the debugger in a test server, and thus we should use print to debug instead. (Note that I haven't tested any of these claims and these are just from memory. I can't create a Test Server on Linux, so this is the best I can provide.)

  If we modify our serverscript from

  for _, player in pairs(game.Players:GetPlayers()) do foo(player) end

  to

  for _, player in pairs(game.Players:GetPlayers()) do print(player.Name) foo(player) end

  we can see what players we processed. Repeating what we did earlier with test servers, we find that it prints nothing. We can add a print before the for loop to find when it runs. When we start the test server, we find that it prints that it ran the for loop before we added any players. We can solve this with the use of events like below and delete our for loop.

  game.Players.PlayerAdded:Connect(foo)

  We find that, for a single player, it works, but with two players, it doesn't and the name of the part is only set to the second player who joined. In order to show another feature of the debugger, I'll make the code think that two players joined by doing

  --game.Players.PlayerAdded:Connect(foo) foo({Name = "Player1"}) foo({Name = "Player2"})

  to make the function foo think that two players have joined. We can set a breakpoint in the code for the function foo and open the Watch window. You can open this by going to View at the top and enabling it. The Watch window has three sections: My Watches, Local, and Global. These names are self explanatory so I won't be going into them. We want to be looking at the part's name, so we should set a watch for part.Name. When we step through the function, we find that setting to part.Name doesn't actually create a new part and just overrides the old name when we get to handling Player2. With this information, you can find that you can replace

  return function(plr) part.Name = plr.Name end

  with

  return function(plr) local part = Instance.new("Part") part.Name = plr.Name part.Parent = workspace end

  and delete our code that created a part earlier.

  Although this tutorial might be hard to follow just with text, you should get an idea of how the debugger works and you should experiment with it yourself.

• Collaboration Requests
  

  Post here if you wanna work with people to try and get stuff done but never end up finishing anything together

  Discord API

  197
  Topics
  1024
  Posts

  

  If your looking for an experienced builder with 2-3 years experience, I'm someone you should consider. An example of my building skills/experience is in this game I've created.
  link: https://www.roblox.com/universes/configure?id=1469282684#/#basicSettings
  It's my most recent build, and an idea of how qualified I am at building.