Skip to content
This repository was archived by the owner on Aug 3, 2024. It is now read-only.

Commit e11a0ed

Browse files
authored
Merge pull request #15 from Teemsploit2/patch-1
Update README.md
2 parents 84513ce + 6428a9f commit e11a0ed

1 file changed

Lines changed: 10 additions & 3 deletions

File tree

README.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,21 @@ You can find the support server here https://discord.gg/5VAKhPQh8Z<br>
88
</p>
99
<hr>
1010
<p>
11-
12-
How to add a plugin to situation admin
13-
11+
<h1>How to use the script</h1>
12+
Situation admin is very easy to use, first you will need an executor for roblox for this we would recommend either 'SynapseX' or 'Script-Ware' the link for both is listed above once you have installed the executor simply copy and paste the code below into your executor and click 'execute'.
13+
Type 'Help' into the console once executed for a list of commands, currently over 30 commands with more coming soon
14+
```lua
15+
loadstring(game:HttpGet(('https://raw.githubusercontent.com/Teemsploit/SituationAdmin.lua/main/admin.lua'),true))()
16+
```
17+
</p>
18+
<p>
19+
<h1>How to add a plugin to situation admin</h1>
1420
A folder named "situation_plugins" will be created upon execution.<br>
1521
To create a plugin you will need to create a new file such as <command_name>.lua.<br>
1622
Situation admin will treat every lua file within the folder as a function, whatever is inside the file is what is gets ran whenever you execute the command.<br>
1723
The name of the file will be what the command is called for example if the file is named "example.lua" to run the command you would type "command" in the input
1824
</p>
25+
1926
<h1>Warning about a skid</h1>
2027
<p>
2128
There is a skid going around taking our project and needlessly modifying it trying to claim the code has been skidded. He goes by "HoppingShark1437" and he is someone with very little understanding of Lua. Based on past pull requests he has tried to make incompatible changes that conflict with the plugin system, tries to unnecessarily change the splitter by making it work with legacy code even though anyone with half a brain knows to use an up-to-date Lua, and has tried to modify our command lookup from bracket notation to dot notation solely because "it doesn't make sense" (to him anyway) when by changing that, the entire lookup would break.<br>

0 commit comments

Comments
 (0)