Installation Process
Last updated
Last updated
This is the process you will go through to conduct the installation for the customer. If you need clarification on certain features, then please refer to our .
Make sure that the customer has downloaded pac and put the folders in the root of his resource folder. You can’t download it for them. If you don’t check this and don’t have the files, you will be stuck.
Go to the server.cfg and ensure pac. Ensure only pac.
After pac is started, run the command pac install in the server console then restart the server.
Go to your panel->Admin->Users and search the user. Then open their server settings and import the share token basic-config.
You can use a different config based on your initial assessment of their server. If you believe a more complex config would suit the server better, use advanced-config. Please note that more complex configs will require you to test them to the best of your ability.
5. Put the discord webhook links into the appropriate fields on the settings page that they sent you and save.
6. Go to the server.cfg again and set the ACE permissions for them and their staff, then restart the server. You will also need to confirm whether the server uses a different admin menu, and ensure that proper bypass permissions are set for staff so that they do not get banned for using other admin menus to spectate.
7. Check if the customer uses vMenu, if yes go to the settings (text GUI) of the customer and remove the “mpleaderboard” line.
8. In the settings (text GUI) set KickForEventProtectionTesting to true.
9. Run pac install eventprotection in the server console and restart the server.
10. Connect to the server and test the server globally to see if you have false kicks. If you do, then follow the procedure in our event protection guide to ignore the event(s).
In many cases, you will not be able to test all the server and triggers. If the customer asks you a question about a trigger, you need to assist them. It is strongly recommended that you show them how to ignore an event during installation.
It is recommended that you offer customers a 48-hour test period. This way they will have been able to find the possible triggers remaining that need to be ignored.