Free tools Windows power users keep installed
One-click scans. No signup required.
RocketMod permissions are configured in the Rocket installation used by your specific Unturned server. In the legacy RocketMod layout, start the server once to generate Servers/<server-name>/Rocket/Permissions.config.xml, stop it, then define a default group, add SteamID64 members, and place each command’s exact registered permission node in that group’s <Permissions> section. Rocket groups do not replace Unturned’s vanilla administration file, so configure both systems when a command requires both.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Unturned servers with free DDoS protection and up to three free backups a day.
Confirm which RocketMod implementation you are running
Before editing anything, identify the Rocket module, Unturned version, and server distribution that are actually installed. The original RocketMod/Rocket.Unturned repository is archived; its README says that Sven Mawby (fr34kyn01535) and Enes Sadık Özbek (Trojaner) stopped maintaining RocketMod. That makes the original implementation legacy software rather than a guarantee of compatibility with every current Unturned build.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
Many communities use a maintained fork or a host-provided Rocket-compatible module. Those versions can generate different file names and XML schemas. The legacy workflow uses Permissions.config.xml, while a newer third-party reference uses separate permissions.xml and groups.xml files with elements such as <Parent>, wildcards, and negation. They are not interchangeable. Use the template created by the build installed on your server instead of copying a schema from another version.
- Record the Unturned server version and the Rocket module or fork version.
- Check the module’s installation instructions for your operating system and server provider.
- Do not overwrite a generated configuration file with an example from a different implementation.
- Make a backup of the entire server instance before changing permissions.
Install or enable RocketMod and generate its files
Rocket cannot authorize commands until it is loaded by the particular Unturned server instance. Installing it on one instance does not automatically configure another instance on the same machine.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Self-hosted server
- Install the Rocket module in the module location supported by your Unturned server distribution.
- Start the server and wait for a completed boot. Rocket should load before you expect plugin commands to work.
- Stop the server cleanly. The first boot creates the Rocket directory and its configuration files, commonly including
Rocket.config.xmlandPermissions.config.xml.
Managed server
- Open the host’s module or server-software selector and enable RocketMod if the host offers it.
- Start the instance once, then stop it after the console shows that the module has loaded and generated its files.
- Use the host’s file manager, SFTP, or control-panel console to open the instance-specific Rocket directory.
If no Rocket directory appears, do not create a blank permissions file by hand. First confirm that the module is enabled for this instance, that the server completed a boot, and that the account running the server can write to its data directory.
Find the permissions file and preserve its schema
In the legacy layout, the file is commonly located at:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsServers/<server-name>/Rocket/Permissions.config.xmlThe exact root path can differ when a host renames the server instance or stores multiple instances separately. Search from the instance’s own Servers directory, not from an unrelated global Rocket folder.
Open the generated file while the server is stopped. Keep the original as a backup, and make one logical change at a time. XML is unforgiving: an omitted closing tag, altered namespace, duplicate group identifier, or unsupported attribute can prevent the provider from loading.
Do not replace a generated root element, namespace, or element name merely because an online guide shows a cleaner example. A legacy file may use <RocketPermissions> and a single permissions document, while another fork may split groups and permissions into different files. The generated template is authoritative for your build.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Understand the legacy permissions structure
A representative legacy document has a default group and a collection of groups. Each group has an identifier, a display name, members, and permission entries:
<RocketPermissions>
<DefaultGroup>default</DefaultGroup>
<Groups>
<Group>
<Id>default</Id>
<DisplayName>Default</DisplayName>
<Members />
<Permissions>
<Permission Cooldown="0">home</Permission>
<Permission Cooldown="0">tpa</Permission>
</Permissions>
</Group>
</Groups>
</RocketPermissions>This is a model of the legacy arrangement, not a universal replacement file. Keep every required namespace and attribute already present in your generated document. The command entries shown are examples; only add commands supplied by Rocket or by plugins that are installed and loaded on your server.
| Element | Purpose | What to verify |
|---|---|---|
DefaultGroup |
Selects the group applied to a player who has no other assignment. | Its value exactly matches one existing group Id. |
Group/Id |
Internal identifier used when assigning members and selecting the default. | Every ID is unique and uses the spelling expected by the installed build. |
DisplayName |
Human-readable group label. | Changing it does not change the ID referenced elsewhere. |
Members |
Contains the SteamID64 values assigned to that group. | Use the generated member element format; do not guess a different nesting style. |
Permissions |
Contains the command or plugin nodes granted to the group. | Use the exact registered node and preserve attributes such as cooldown settings. |
Create groups and assign SteamID64 members
Start with the least privilege a player needs. Leave ordinary players in a default group containing only normal gameplay or utility commands. Create a separate moderator group for moderation tools and a tightly restricted administrator group for high-impact operations such as banning, server control, item spawning, or teleportation.
Set the default group
Choose the group that should apply to every player without an explicit assignment and set DefaultGroup to that group’s exact ID. If the ID is misspelled or the group is absent, players may receive no expected permissions or the file may fail validation, depending on the implementation.
Add a group
Duplicate the group shape already in the generated file, then give the new group a unique ID and display name. Keep the permissions list empty until you have confirmed the nodes you intend to grant. A group ID is a configuration key, not a chat name; changing it requires updating the default-group value and any member assignments that reference it.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Add a player
Place the player’s SteamID64 in the members element required by your generated schema. Steam names are not reliable identifiers: they can change, contain unusual characters, or be shared by multiple accounts. Verify every digit before saving. Hosting documentation describes Rocket permissions as a mapping from Steam IDs to groups; a player with no explicit group receives the default group’s permissions.
When a player should move from one tier to another, remove the old assignment according to the file’s schema rather than leaving contradictory entries in multiple groups. If your fork supports multiple group memberships, check its precedence rules before relying on inheritance or deny behavior.
Add the exact permission node for each command
Rocket checks the command registered by Rocket or by a plugin. The name a player sees in chat is not necessarily the permission string. A plugin can register a namespaced node, and the node may be case-sensitive in the installed implementation.
Find the registered node
- Read the plugin’s documentation for its permission section.
- Inspect the command source or metadata when documentation is incomplete.
- Use the node declared by the installed build, including its namespace and capitalization.
For example, the archived CommandTphere implementation declares Rocket.Unturned.Tphere as its permission. Granting only tphere or a display label would not be equivalent. Community examples also show nodes such as home, tpa, tpa.accept, tpa.deny, and plugin-specific kit permissions, but those examples do not mean every server has those commands installed.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Enter the node
Add one permission element in the group’s existing Permissions section, preserving the generated attribute format. A legacy entry may look like this:
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
<Permission Cooldown="0">Rocket.Unturned.Tphere</Permission>Do not assume that a wildcard grants every plugin command, or that a node from a newer fork’s documentation works in the archived implementation. If a plugin documents a node such as myplugin.use, enter the complete string rather than shortening it to use.
Save, restart, and apply changes safely
- Stop the server before making broad XML edits.
- Save a dated backup of the working permissions file.
- Preserve the file’s encoding, root element, namespaces, and required attributes.
- Start the server and watch the console for XML parsing, module-loading, and plugin errors.
- Join with a test account in each group and execute one permitted and one unpermitted command.
Some community instructions recommend /rocket reload for minor changes after startup. Reload behavior varies by RocketMod build and plugin. In one archived implementation, the general reload-all operation was disabled while individual plugin reload operations remained available. Treat a reload command as implementation-specific: use the command documented for your distribution, and restart the server when the result is unclear or the permission provider itself changed.
Keep Rocket permissions separate from vanilla Unturned administration
Unturned’s vanilla administration is configured through Adminlist.dat or the equivalent owner and admin settings. Rocket’s groups are a separate authorization layer. A player can be a vanilla administrator and still receive “permission denied” for a Rocket plugin command because the plugin node is missing. Conversely, a player can belong to a Rocket group without having the vanilla privilege required by a game command.
When a workflow crosses both layers, configure both: grant the appropriate vanilla role in Adminlist.dat, then grant the Rocket or plugin node in the relevant Rocket group. Test the complete command path rather than assuming one administrator setting supersedes the other.
Troubleshoot the common failure modes
The Rocket folder or permissions file does not exist
- Confirm Rocket is enabled for this exact server instance.
- Start the server once and wait for a complete boot; files are normally generated during startup.
- Check the console for a module-load failure or a write-permission error.
- On a managed host, verify that you are browsing the instance’s own
Servers/<server-name>/Rocketdirectory.
The server rejects the XML
- Restore the last generated or known-good backup.
- Compare the root element, namespaces, and nesting with the template created by your build.
- Check every opening and closing tag, quotation mark, and duplicate group ID.
- Reapply one change at a time, restarting after each change so the failing edit is identifiable.
A player receives permission denied
- Confirm the player’s SteamID64, digit by digit.
- Confirm the member is in the intended group and is not still assigned to a different tier.
- Confirm
DefaultGrouppoints to a real group when the player has no explicit assignment. - Copy the node from the command or plugin documentation exactly, including namespace and capitalization.
- Restart if your build does not reliably reload permission changes.
The command is unknown
An unknown command is normally a loading or registration problem, not a permissions problem. Confirm that the plugin DLL is present, that the plugin loaded without errors, and that the command belongs to the installed Rocket build or plugin. Adding a guessed permission node cannot make an unloaded command exist.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
It works on Windows but not on Linux
Linux paths are case-sensitive. A mismatched plugin directory or DLL name can prevent the plugin from loading even when the XML permission entry is correct. Compare the directory and file names character for character with the names expected by the host and plugin, then inspect the startup log for a load error.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteReload appears to do nothing
Reload support differs between RocketMod builds and individual plugins. Check the console for a reload result, verify that the plugin remains loaded, and perform a full restart when the provider or XML file changed. Do not repeatedly edit a running file while trying to determine which version the server has read.
Two guides show different file names
That usually indicates different implementations. The archived legacy layout and newer third-party references use materially different schemas. Prefer the files generated by your installed build; migrate only after reading that build’s migration instructions and preserving a rollback copy.
Design a permission model that is easy to audit
- Keep the default group small and suitable for an untrusted player.
- Separate moderation from administration so a moderator cannot automatically run server-control or item-spawn commands.
- Grant a complete namespaced node only when you understand what the plugin command does.
- Review every plugin’s permission documentation rather than relying on a universal “safe” list; the available commands and risks vary by plugin.
- Record why each high-impact node was granted and to which SteamID64 values.
- Back up the generated file before every structural edit so a failed change can be reversed immediately.
Test with accounts representing each tier. A successful test should demonstrate both sides of the boundary: a command that the account should run and a high-impact command that it should not run. Also test after a server restart, because a temporary in-memory permission state is not proof that the XML is valid.
Choose a deployment approach and plan migration
| Option | Compatibility check | Operational concerns | Migration risk |
|---|---|---|---|
| Self-hosted legacy RocketMod | Match the archived module to the Unturned build you actually run. | You manage module installation, backups, XML validation, logs, and Linux file-case issues. | High if a future Unturned update or plugin expects a newer fork. |
| Managed hosting with Rocket support | Ask which Rocket implementation and permissions schema the panel installs. | Confirm file access, backup and rollback controls, plugin reload behavior, and instance-specific paths. | Depends on whether the host preserves your existing group and node format. |
| Maintained RocketMod fork | Verify current Unturned compatibility and read the fork’s generated template. | Expect possible changes to file names, inheritance, wildcards, negation, and reload commands. | Plan a documented conversion from legacy Permissions.config.xml; do not merge files by intuition. |
Before migrating, export a list of groups, SteamID64 members, and every permission node currently in use. Install the target implementation on a test instance, let it generate its own files, then recreate the groups using the target schema. Validate each node against the target plugin documentation, test with representative accounts, and keep the old instance backup until the new server has survived a restart and a permissions audit.
Final verification checklist
- Rocket is installed or enabled for the correct Unturned server instance.
- The server has booted once and generated its own Rocket files.
- The server was stopped before the XML was edited.
- The file path, root element, namespaces, and element names match the installed build.
DefaultGroupnames an existing group.- Each SteamID64 is in the intended group and is spelled correctly.
- Every permission entry is the exact node registered by Rocket or the plugin.
- Vanilla roles in
Adminlist.datare configured separately when required. - The console is free of XML, module, and plugin-loading errors after restart.
- Each group has been tested with both an allowed and a denied command.
The Bottom Line
Use the permissions file generated by your installed RocketMod implementation, assign SteamID64 members to narrowly scoped groups, and grant only the exact nodes registered by the commands or plugins. Keep Rocket groups and vanilla Unturned administration configured separately, and restart and test after every structural change.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
