UPS - Ulysses Prop Share

[Megiddo]

Any other errors around that? Just the one? What else was happening around this time?

[Megiddo]

Another substantial SVN update:

Cleaned out some stuff from the ownership information that helped when we were using NWVars but was just mucking things up now.
Improved our new ownership update process.

This has the potential to create many new bugs so let us know if you find any!

[jay209015]

Any other errors around that? Just the one? What else was happening around this time?

No, only thing I noticed was this error repeated several times.

[Patrik]

I also get the

Code: [Select]

[UPS ERROR] Ownership table is not setup for a ply in onEntRemoved! Could be a b
ad UPS addon installed or bad initialization?   Please report this error to ulys
sesmod.net with information on how you got it.error now, and props some started being owned by map. Just reinstalled server so all addons I got is Wire SVN + Wire extras, PHX3 SVN, ULib + ULX + UPS.

[jay209015]

Lol, you have the same exact setup as me . Ironically same error.

[spbogie]

This is just a hunch, but with the "Ownership table is not setup..." error, did a player join soon before the error occured?

[Megiddo]

Your version as oppose to its counterpart tried and tested version is extremely good in both ways but i propose altering it slightly so your version does both (allow me to elaborate).
On map start it checks all the objects on the map and owns them by the map, giving them the full run of the mill protection i.e. players can use only, then end this script and initiate another one that protects props spawned by the map minimalistic-ally i.e. Players can weld, tool e.t.c. but not remove, standard admin allowances of course apply to both scripts. Finally have a cleanup script directly related to props spawned after map start allowing admins to quickly cleanup any mingebags that decide they want to start spamming using map spawning entities especially as maps like wire construct exist. If this where to come through I would rate this system as a king of all current protectors.

I'm working on this implementation now (I know, only 2 months later ) and here's what I have:

Code: Lua

1. initialMapProtectionInfo = {
2.         ["^func_breakable$"]               = { ACTID_DAMAGE, },
3.         ["^func_breakable_surf$"]          = { ACTID_DAMAGE, },
4.         ["^func_physbox$"]                 = { ACTID_DAMAGE, ACTID_FREEZE, ACTID_PHYSGUN, ACTID_TOOL, ACTID_UNFREEZE, },
5.         ["^prop_physics"]                  = { ACTID_DAMAGE, ACTID_FREEZE, ACTID_PHYSGUN, ACTID_TOOL, ACTID_UNFREEZE, },        
6.         ["^prop_ragdoll$"]                 = { ACTID_DAMAGE, ACTID_FREEZE, ACTID_PHYSGUN, ACTID_TOOL, ACTID_UNFREEZE, },
7.         ["^prop_vehicle"]                  = { ACTID_DAMAGE, ACTID_FREEZE, ACTID_PHYSGUN, ACTID_TOOL, ACTID_UNFREEZE, },               
8.         ["^item_ammo_"]                    = { ACTID_FREEZE, ACTID_PHYSGUN, ACTID_UNFREEZE, },  
9.         ["^item_battery$"]                 = { ACTID_FREEZE, ACTID_PHYSGUN, ACTID_UNFREEZE, },  
10.         ["^item_box_buckshot$"]            = { ACTID_FREEZE, ACTID_PHYSGUN, ACTID_UNFREEZE, },  
11.         ["^item_healthkit$"]               = { ACTID_FREEZE, ACTID_PHYSGUN, ACTID_UNFREEZE, },  
12.         ["^item_healthvial$"]              = { ACTID_FREEZE, ACTID_PHYSGUN, ACTID_UNFREEZE, },  
13.         ["^item_item_crate$"]              = { ACTID_FREEZE, ACTID_PHYSGUN, ACTID_UNFREEZE, },  
14.         ["^item_rpg_round$"]               = { ACTID_FREEZE, ACTID_PHYSGUN, ACTID_UNFREEZE, },  
15. }
16.  
17. extendedMapProtectionInfo = {
18.         ["^func_breakable$"]               = allIdsAndTake,
19.         ["^func_physbox$"]                 = allIdsAndTake,
20.         ["^prop_physics"]                  = allIdsAndTake,
21.         ["^prop_ragdoll$"]                 = allIdsAndTake,
22.         ["^prop_vehicle"]                  = allIdsAndTake,
23.         ["^item_ammo_"]                    = allIdsAndTake,
24.         ["^item_battery$"]                 = allIdsAndTake,
25.         ["^item_box_buckshot$"]            = allIdsAndTake,
26.         ["^item_healthkit$"]               = allIdsAndTake,
27.         ["^item_healthvial$"]              = allIdsAndTake,
28.         ["^item_item_crate$"]              = allIdsAndTake,
29.         ["^item_rpg_round$"]               = allIdsAndTake,
30. }  

First notice that the keys are regular expression strings. If you don't know what these are don't panic. Basically if you don't see the '$' at the end of the string, it means that it will match any entity that begins with that text. So "^prop_vehicle" will match "prop_vehicle_jeep" and so on.

Second, initialMapProtectionInfo is what's allowed on an ent that was created with the map where the other table is what's allowed on an ent that wasn't created by a player after the map initialization (IE, a vehicle from a spawner).

Third, allIdsAndTake will allow any action on the entity and will also give control of the entity over to the first person to take substantial action on it (IE physgun it).

Got all that? Now, are these permissions good defaults?

Remember that UPS is open source, any admin can change these settings at any time, and easily! It should be fairly easy to understand. Script authors can also inject their own information into these UPS tables.

[jay209015]

I found another possible bug with ups. When building a contraption that contains props from more then one player, you can't adv dupe it. It always says error saving the file.

[Megiddo]

I found another possible bug with ups. When building a contraption that contains props from more then one player, you can't adv dupe it. It always says error saving the file.

They need to give you access to dupe it. In this case, since it's a third party addon, they need to give you permission to move the props as well as delete them. All unrecognized tools are checked for move and delete permission.

In other news, I rolled out the map protection update. You can now remove stuff from spawners! Let me know how you guys like it.

[Megiddo]

Any more feature requests or bug reports? I'd like to get a release out the door soon.

[m0nday]

Hi !

Maybe one (or two) more requests 

A new tab with options to deactivate different protections (use / damage / etc.... ) for everyone.

This may have been asked already, I've no read the whole thread x)

And maybe a new button "Clear disconnected clients props", so we don't have to wait for autoremove. (I used rather often this button with SPP.)

Otherwise, this new prop secure is perfect 


[Yay, first post ]

[Megiddo]

Latest commit fixes a couple bugs you guys have been after me about.

Fixed a bug where players would be unable to reclaim props after ownership was cleared on leave.
Fixed a bug with the friends list not properly loading from saved state.
Fixed a bug where prop ownership would not be cleared.
Clearing/deleting props will no longer take place if the player didn't own anything in the first place.
If an admin clears a disconnected player's props it will now immediately remove that player's information instead of waiting for the normal deletion routing.

And maybe a new button "Clear disconnected clients props", so we don't have to wait for autoremove. (I used rather often this button with SPP.)

That feature was already there but bugged out. Should be fixed with this new commit.

A new tab with options to deactivate different protections (use / damage / etc.... ) for everyone.

Sure, I'll see if I can't work it in.

[Chief_runningwater]

When and how do I download this for my server?....

[Megiddo]

When and how do I download this for my server?....

UPS is in closed beta right now, we're not looking for new beta testers. You'll have to wait until release.

[Chief_runningwater]

UPS is in closed beta right now, we're not looking for new beta testers. You'll have to wait until release.

Thanks thats all I wanted to know, also this will be like a replacement for simple prop protection its an add-on like that right?...