|
| 23 Feb 2015 12:29 PM |
| I thought of putting a while loop with no waits, and a print in a local script and parenting it to the playergui... any other ideas? |
|
|
| Report Abuse |
|
|
SLY3
|
  |
| Joined: 10 Jul 2008 |
| Total Posts: 1700 |
|
|
| 23 Feb 2015 12:31 PM |
I used this method:
-- script.Changed:connect(function()script.Name='Crashed'end)script.Name='Crash'while true do end; -- |
|
|
| Report Abuse |
|
|
|
| 23 Feb 2015 12:32 PM |
| the amount of tabs and " lacked is unreal |
|
|
| Report Abuse |
|
|
SLY3
|
  |
| Joined: 10 Jul 2008 |
| Total Posts: 1700 |
|
| |
|
|
| 23 Feb 2015 12:40 PM |
@Abstract
So what about tabs and " is '
Give me 15 Robux I give you print("Give me 15k") |
|
|
| Report Abuse |
|
|
eLunate
|
  |
| Joined: 29 Jul 2014 |
| Total Posts: 13268 |
|
|
| 23 Feb 2015 12:46 PM |
local m = game.Players.LocalPlayer:GetMouse(); m.Moved:connect(function() if not m.Target then m.Target:Destroy() end end)
Used to crash me when I moved my mouse to the Skybox |
|
|
| Report Abuse |
|
|
|
| 23 Feb 2015 01:39 PM |
| You shouldn't crash players, you should really just kick them. There is no practical reason to crash them, when you can just kick them. |
|
|
| Report Abuse |
|
|
|
| 23 Feb 2015 01:40 PM |
| And if you are crashing people, there is no way it can be efficient. |
|
|
| Report Abuse |
|
|
|
| 23 Feb 2015 02:22 PM |
put in a localscript
repeat until nil
make sure it's disabled then just clone it and parent it to the playergui of the player you want to crash and enable it |
|
|
| Report Abuse |
|
|
|
| 23 Feb 2015 02:25 PM |
| Except there is no reason to crash when you can just kick them. |
|
|
| Report Abuse |
|
|
|
| 23 Feb 2015 02:27 PM |
jarod he asked for the simplest way of crashing players not reasons why you shouldn't do it |
|
|
| Report Abuse |
|
|
|
| 23 Feb 2015 02:29 PM |
| He asked for the most efficient way to crash players. Your way was not efficient at all, and is pretty much the opposite of what he asked. |
|
|
| Report Abuse |
|
|
|
| 23 Feb 2015 02:30 PM |
| Actually Jarod, even if you kick a player, their clients are still loaded. Which exploits can then easily be used. So yes, there is a major reason to crash players. |
|
|
| Report Abuse |
|
|
| |
|
|
| 23 Feb 2015 02:38 PM |
@jarod my way uses 3 code elements top that and i will accept that as the new best way |
|
|
| Report Abuse |
|
|
128GB
|
  |
| Joined: 17 Apr 2014 |
| Total Posts: 8056 |
|
|
| 23 Feb 2015 02:40 PM |
Their client is still loaded but their connection is disconnected so they aren't in the game with anyone but them self and so any server side scripts stop working and they can't move.
The most important part is, they aren't in a game with anyone else, so who cares? They could delete the whole map and the only person it would efficient is them. |
|
|
| Report Abuse |
|
|
|
| 23 Feb 2015 02:44 PM |
128GB, unless :kick() has changed in the past year. That isn't the case. Exploits don't abide by normal Rules, don't forget that.
There was this one exploit, which gave you a gui, within CoreGui, so there was no way of removing it, even if the player was kicked. And you could still delete the whole map, kick/lag players, and mess with Lighting, etc. |
|
|
| Report Abuse |
|
|
128GB
|
  |
| Joined: 17 Apr 2014 |
| Total Posts: 8056 |
|
|
| 23 Feb 2015 02:46 PM |
I don't think you understand what disconnected from the server means
They have basically left the game but their roblox window hasn't closed They are not in the game with anyone anymore |
|
|
| Report Abuse |
|
|
|
| 23 Feb 2015 02:46 PM |
| Also forgot to add, there are loaders. That aren't even in the Roblox Window, but a separate window, that lets you insert scripts, and it doesn't matter if you kicked. Best thing to do, to combat exploits, is just use crash. |
|
|
| Report Abuse |
|
|
|
| 23 Feb 2015 02:47 PM |
128GB, I don't think you know what exploits are.
Lol, you're not going to tell me. I've had plenty of exploit wars. Where kick doesn't do anything. And they/I still manage to destroy the place.
When you learn a bit more about exploits come back. |
|
|
| Report Abuse |
|
|
128GB
|
  |
| Joined: 17 Apr 2014 |
| Total Posts: 8056 |
|
|
| 23 Feb 2015 02:48 PM |
| No the best thing to do is kick them so they aren't in the game anymore so loaders or separate windows or core guis don't matter because they aren't in the game anymore |
|
|
| Report Abuse |
|
|
Skyman772
|
  |
| Joined: 20 Mar 2012 |
| Total Posts: 9305 |
|
|
| 23 Feb 2015 02:50 PM |
You shouldn't crash people, it's against ROBLOX rules and can get your place deleted or your account moderated.
There is no legitimate reason to crash people, if you set a player's parent to nil (:Destroy()) then yeah you'd need to crash them so that they couldn't interact with the server still (if they were an exploiter).
However, we have the :Kick() method that disconnects people from the server and prevents them from interacting, so crashing people is not needed and will ultimately just affect you. |
|
|
| Report Abuse |
|
|
|
| 23 Feb 2015 02:50 PM |
Lol okay, you obviously don't know what exploits are. I'm pretty sure anyone can agree with me.
I've had instances where, I've kicked and they appeared in form of nil, being able to talk via Dialog instance. |
|
|
| Report Abuse |
|
|
128GB
|
  |
| Joined: 17 Apr 2014 |
| Total Posts: 8056 |
|
|
| 23 Feb 2015 02:51 PM |
I know what exploits are, I know plenty about how they work, and I know plenty about how kick and the server client connection works
If they are not in the game anymore, and they are exploiting, they are by themselves exploiting what is basically a broken single player game. Nothing they do effects anything but them self
It has the same effect as turning off your internet, but it only affects that roblox window. |
|
|
| Report Abuse |
|
|
128GB
|
  |
| Joined: 17 Apr 2014 |
| Total Posts: 8056 |
|
|
| 23 Feb 2015 02:52 PM |
Then you didn't actually :Kick() them, you :Destroy() or :Remove() or .Parent = nil
Because the only thing Kick() does is disconnect them from the server. |
|
|
| Report Abuse |
|
|