PAC3 Restrictor

Hey can you fix the autoload issue please?

Does not block autoload

Is there any way to restrict pac3 to certain jobs using this?

Jack, use pacres_cfg "steamid" "basegroup". First argument is user's gmod steamid (i.e. Player:SteamID() ), second argument is group, used as base. You also can create custom group with unique name (not like usergroup) and use it as base.

Is there a donation console command that I can use for the donation system?

Still working. Mysql support doesn't required, but planned on next update.

Does this still work? does it support mySQL?

Could I get a discount please?

Look at description in section "Configuring it with the server console". Console command for this is pacres_cfg (read desc).

Is it possible to add a console command that adds the users steamID with certain options available? example: pacres_addid steamidhere option1 option2 etc........? Other then that I like the addon so far :)

Well as far as I'm aware we are using the most recent stable build from the pac3 github. https://github.com/CapsAdmin/pac3

I have looked for PAC 4 month ago, but haven't see stable version. So its just a test version. But after official release, support for this PAC will be added soon. If you had stable version, write in Steam.

Hey I dev for a server owner who owns this script and we recently updated our PAC3, and the newer version of PAC3 includes Pac4 beta features that pacres doesn't let us restrict. Is there going to be an update soon for this?

Hi, It's able to restrict each usergroup/steamID and things within it. Also it can create default restricts for PAC if none given.

Hi, I have a question. Is this able to restrict a certain user group to using PAC or only things within it?

Good size is 25 mb; halo, fog, sunbeams set to 0 because they can create lags. Models must be lower or equals 100. My co-owner set entity limit to 0 for users and moderators, because entity can scale player model with any size or completely hide player.

What do you recommend restricting each item to in the menu? What would be a good size to restrict to in MB, and so on?

Try make something like this using ugly snippets and small api of PAC. Main reason for creating this - checking outfit size, because player use high poly models(40Mb+) and remove spamming with missing model/material/webaudios. Second reason - restrict count of outfit things and make simple control. I looked for facepunch threads, but there broken count of outfits(autoload,single wear won't checked), hard to config what need to restrict(no require LUA, but newbies make errors even here). I spend many time for this, its well optimized, tested, and installed on my cinema server. I sell restricts for 2.5-5$(small for you, a lot for Russia and me ><) and receive more than 100$ for host upgrade. And I'll stay this price after updates(integrated in PAC GUI, add clientside checking, add settings, make simple antisteal and etc.) I think you understand.

Hey mate, I think its a good idea, although it isnt worth $7.00. People can find this all over the facepunch forums for free. I think It would be a good idea to lower the price.

Paypal willn't accept payments and return back. Support doesn't respond...

I'd recommend https://www.materialui.co/colors if you want it to look sleek and simple, use bright colors to attract attention mainly for buttons and darkish colors for the background.

It's not just colors though, it's the menu arrangement. Inconsistent padding makes it look highly unappealing, as well as the style choices make the menu come across as thrown together, not planned out.

I tested on two different servers, the owners did not make any remarks on the interface. Why $ 7, one reason - it is difficult to implement an effective data acquisition system size, and maximum productivity. Anyway, I'll try to find a good combination of colors in the future ..

I'd say $7 when you make the GUI look appealing