JZap

Approved JZap 1.0

No permission to download

mikec

Master Of All That I Survey
Retired Staff
Trusted Member
Jul 12, 2014
296
152
28
Los Angeles, California, USA
mikec submitted a new resource:

JZap - Zap all stuff owned by a player from the server with one hit.

Type /jzap to activate.

Shoot or hit a structure or deployable object, and the owner will be identified. Hit it again to zap everything owned by that player. Or type /jzap again to cancel.

RCON admin permissions are necessary.
Read more about this resource...
 
  • Like
Reactions: Jakkee

maughanorama

Member
Member
Nov 27, 2014
181
10
18
50
ill install tomorrow, cant wait to test it, getting bored of having to use instako to remove banned players houses ...
 

maughanorama

Member
Member
Nov 27, 2014
181
10
18
50
works excpet it does dnot give the playername it always says ?Private?, it does give the steamid but thats a bit hard to find the user quickly by the steam id
 

DreTaX

Probably knows the answer...
Administrator
Jun 29, 2014
4,093
4,784
113
At your house.
github.com
works excpet it does dnot give the playername it always says ?Private?, it does give the steamid but thats a bit hard to find the user quickly by the steam id
The reason why Its happening because you are using cracked. Mike is using steamapi to check for the player's name, which I think just makes Its slower, just like when people were using Owner plugin on Magma. Anyways, you could ask him to convert It to use ini files which will make It faster. Though, I have a feeling he made It on purpose.

Sent from my Samsung Galaxy S4
 

mikec

Master Of All That I Survey
Retired Staff
Trusted Member
Jul 12, 2014
296
152
28
Los Angeles, California, USA
I tried to get it to use the Rust++ userCache for name lookup, but without some additional help from Fougerite, I can't make it work. In 1.0.8 there is a new class for storing all Player info and you will be able to use that to get a player's name by SteamID, and SteamID by name (and even partial matches), The player has to have connected to the server at least once. It will fallback to SteamAPI if there is no stored info. The new lookups won't be affected by cracked servers, except when falling back to Steam API.
 

mikec

Master Of All That I Survey
Retired Staff
Trusted Member
Jul 12, 2014
296
152
28
Los Angeles, California, USA
IPM does not need help from Fougerite to access RustPP.Core.userCache to lookup Name by SteamID, and has no need to keep its own ini file for that purpose. The only problem Jint has is that the keys are 64bit ints, and Javascript cannot use a 64bit int reliably. Python support 64bit ints, and so can use them as keys to the name in userCache (a Dictionary<ulong, string> class).
 

MasterPeace

Retired Staff
Retired Staff
Feb 2, 2015
269
69
28
45
Poland
I don't remember errors. It was something with player names or IDs or something like that. Maybe that there was no player ID in datastore? I don't really remember.
 

DreTaX

Probably knows the answer...
Administrator
Jun 29, 2014
4,093
4,784
113
At your house.
github.com
Yes. I store the playernames under their id. It requires users to join atleast once. No worries though. 1.0.9 will allow me to use our new usercache. I will connect wiper and all my other plugins to that.

Sent from my Samsung Galaxy S4