This guide will help you configure the Atlas Admin system after installation. Follow these steps to ensure your setup is correct and that the system functions as expected.

---

1. Placement

   • Place the Atlas_Loader into the Workspace.

2. Additional Tasks

• Read the README script, as well as customizing settings under Atlas_Loader.

3. Notes
   • Do Not Edit Atlas_Loader => Loader_f => loader!!

---

Here's a quick explanation of the key settings you can configure:

• prefix: Sets the command prefix. Default is ":".
• datastore: Set this to a random string for system logging, bans, etc.
• Server_Message_Header: Change this to customize the server message header.
• debug: Keep this false to prevent bypassing admin/override verification checks.
• fun_commands: Enable fun commands like :sit, :jump, etc.
• plugins_enabled: Set to true to enable custom plugins (see Plugins section).
• developer_metrics: Sends us, the developers, metrics regarding the system and helps us track unique games the system's used in.

• component_verification: Helps delete broken components and source the correct ones.
• banned_users: Hard-banned users cannot be unbanned unless removed from this script.
• whitelist: When enabled, players in this list are allowed access.
• Override: Users in this section can run special commands and are immune to certain restrictions.
• Admins: Hard-coded admins. Any other user (added with :admin user) is a temporary admin.

---

To add your own plugins, refer to the example_plugin ModuleScript file for setup instructions.

• Requirements
  • Plugins must have a maximum of two arguments. They can have a minimum of zero arguments.

---

If you encounter any issues during configuration or need assistance, please join our support server on Discord. You can also report issues or suggest new features on our GitHub repository.

• Discord Support Server: Join here.
• GitHub Repository: Visit here.

---

This configuration guide should help you set up Atlas Admin and understand key settings. If you have further questions or require additional support, don't hesitate to reach out to us through Discord or GitHub.