Jimbo's E2 Manager - Garry's Mod

I have noticed servers have been removing E2 from servers as they can be used to exploit massively. I really like E2 so I wish it make it more manageable by the staff. So I have made this tool to be able to do just that. This code allows the user of the manager to be able to find all of the E2's and are able to see the ops, The owner of the E2 and the E2 name. While being able to see who owns the E2 and the Ops it also allows you to TP to the E2 and the Owner and also remove the E2. I had made this for a Server I was a developer for and they didn't seem to care. It has been sitting doing nothing on my Hard-drive doing nothing. I have also tried making the GUI look nice. Feel free to change the code but do not reupload anywhere else. This may have been already made so I have wasted my time but if it hasn't enjoy. Also, if you want some help I might be able to help or if you need a new feature added I maybe able to assist. To open the menu either type "!e2menu" in chat or "e2menu" in console. New features: CPU Usage Ops and CPU Usage update in real time! Entity Index for Compatibility! Workshop [video=youtube;Tzti0jJgw5w]https://www.youtube.com/watch?v=Tzti0jJgw5w[/video] [url]http://steamcommunity.com/sharedfiles/filedetails/?id=949980208[/url]

It's a good idea, my only issue is the UI, but I don't know shit about graphic design, so don't take my work :v: E: I meant color scheme.

Could this make use of expression2's "halt expression" feature seen in the remote uploader of E2? Otherwise cool!

It's really nice! Consider making it a workshop addon, the instructions for that can be found [URL="https://wiki.garrysmod.com/page/Workshop_Addon_Creation"]here[/URL].

I have just updated the code. It is now able to Halt the E2. This allows you to keep the E2 but make it so it does not remove it. It also allows the user to view the E2 in the E2 Editor. Any Problems contact me on Steam.

[QUOTE=Jimbo_;51506125]I have just updated the code. It is now able to Halt the E2. This allows you to keep the E2 but make it so it does not remove it. It also allows the user to view the E2 in the E2 Editor. Any Problems contact me on Steam.[/QUOTE] Incoming morality arguments. I'm sure some people don't want others looking at their code.

[QUOTE=VeXan;51506149]Incoming morality arguments. I'm sure some people don't want others looking at their code.[/QUOTE] I debated to not add in downloading. But seeing how easy it is to just right click it with the tool itself to copy code. I decided to add it.

"I have also tried making the GUI look nice." Where the credits at boi?

Might want to add a column for CPU time as it's more reliable to tell if an e2 really is processing a lot.

Updated Addon! New features!

[QUOTE=VeXan;51506149]Incoming morality arguments. I'm sure some people don't want others looking at their code.[/QUOTE] You loaded your code on [B]my[/B] server, I have the right to inspect it before allowing it to run on my box or at any point thereafter.

[QUOTE=iamgoofball;52384247]You loaded your code on [B]my[/B] server, I have the right to inspect it before allowing it to run on my box or at any point thereafter.[/QUOTE] In my experience, server admins are less interested in inspecting the code, and more interested in copying the E2 and claiming it as their own. In fact, the only time I recall a server admin being interested in my E2 code for a reason other than stealing it, was when I used wirelink to interface with some spacebuild weapon, which accidentally triggered an exploit where the weapon would tick more often than it should have (and therefore, charged and fired more quickly.) Even then, instead of just taking my code without asking, they politely asked me what I was doing, and I explained it to them. IMO there are enough tools available that server admins don't need to see the code to know who is breaking a rule. It is the ignorance of these tools (as well as their inability to use E2 themselves) that causes server admins to ban E2.

[QUOTE=Jcw87;52387827]In my experience, server admins are less interested in inspecting the code, and more interested in copying the E2 and claiming it as their own. In fact, the only time I recall a server admin being interested in my E2 code for a reason other than stealing it, was when I used wirelink to interface with some spacebuild weapon, which accidentally triggered an exploit where the weapon would tick more often than it should have (and therefore, charged and fired more quickly.) Even then, instead of just taking my code without asking, they politely asked me what I was doing, and I explained it to them. IMO there are enough tools available that server admins don't need to see the code to know who is breaking a rule. It is the ignorance of these tools (as well as their inability to use E2 themselves) that causes server admins to ban E2.[/QUOTE] This is why I limited it to SuperAdmin which is usually the Owner and Trusted Staff members. Meaning abusive ones wont be able to copy the code without a lot of hassle. It will also notify you when someone downloads your code.

[QUOTE=Jimbo_;52389987]This is why I limited it to SuperAdmin which is usually the Owner and Trusted Staff members. Meaning abusive ones wont be able to copy the code without a lot of hassle. It will also notify you when someone downloads your code.[/QUOTE] Server owners are usually the problem.