HSC Neon Pink txAdmin Theme — Installation

This guide covers the compiled HSC Neon Pink theme supplied in monitor.zip, including the browser-based txAdmin panel and the in-game admin menu.

Read the version check before copying anything. The package contains a full txAdmin distribution as well as the customized interfaces; replacing the entire folder is not necessary for a theme installation.

1. Requirements

You need:

• A working FiveM FXServer installation running txAdmin.
• File access to the active FXServer artifact directory, including its built-in monitor system resource.
• Permission to stop and start the complete FXServer/txAdmin process.
• A ZIP extraction tool and enough space for a backup.
• A txAdmin admin account to check the panel and in-game menu.
• The HSC monitor.zip download.

If your hosting panel exposes only your server's ordinary resources folder, ask the host whether custom txAdmin interface files are supported. This theme requires access to the built-in system resource, which some providers restrict.

No build step is required

The supplied download is already compiled. Do not run npm install, npm run build, or a frontend development server inside it. Its package.json only declares CommonJS module behavior; it is not a source project with build scripts.

This theme does not need QBCore, ESX, ox_lib, SQL imports, or an additional resource entry in server.cfg.

2. Check your txAdmin version

The supplied package's monitor/fxmanifest.lua declares:

version '8.1.1'

Compare this with the version displayed by your running txAdmin and with the manifest in the active installation.

This guide targets the supplied 8.1.1 package. Compatibility with other txAdmin versions has not been established. The version in the manifest identifies the package; it is not evidence of testing against every FXServer artifact or hosting setup.

If your installed version differs, obtain a matching HSC theme release before replacing interface files. Avoid copying the package's core folder over a newer installation to force a version match.

The .v800 text in the bundled asset filenames does not override the 8.1.1 version declared in the manifest. Keep the supplied filenames unchanged.

3. Understand the download

Extract monitor.zip into a temporary folder on your computer. Open the extracted monitor folder.

The important parts are:

Package path	Purpose	Theme installation
monitor/panel/	Compiled browser panel, fonts and related assets	Copy as a complete matching folder
monitor/nui/	Compiled in-game menu, images and sounds	Copy as a complete matching folder
monitor/core/	txAdmin backend	Leave the installed copy in place
monitor/resource/	Server/client Lua scripts	Leave the installed copy in place
monitor/web/	Additional web files used by txAdmin	Leave the installed copy in place
monitor/fxmanifest.lua	Resource metadata and file declarations	Inspect the version; leave installed copy in place
monitor/entrypoint.js	Runtime entrypoint	Leave installed copy in place

Exact interface files in this release

The panel HTML references:

panel/index.html
panel/index-l89wohw6.v800.js
panel/index-iw21afnq.v800.css

The panel also includes .vite/manifest.json, fonts, favicons and images. Transfer the entire panel folder so those files stay together.

The in-game interface references:

nui/index.html
nui/index.js
nui/index.css

Transfer the entire nui folder, including images and sounds.

The in-game pink styling is present in both nui/index.js and nui/index.css. Copying only the CSS will not install every themed change.

4. Find the active monitor directory

Locate the FXServer artifact installation used by your actual startup command or hosting service. This is separate from the folder containing your gameplay resources and may be separate from txData.

Typical layouts for installations using the monitor resource are:

Windows

C:\FXServer\server\citizen\system_resources\monitor\

The beginning of the path depends on where you extracted FXServer. Look for the installation containing your active FXServer.exe, then locate citizen\system_resources\monitor within that installation.

Linux

/home/fivem/server/alpine/opt/cfx-server/citizen/system_resources/monitor/

Some hosts expose the same directory through a shortened path such as:

/cfx-server/citizen/system_resources/monitor/

These are examples, not universal paths. Follow the active launch script, container mount or hosting configuration to identify the real location.

Confirm the folder before continuing

The target should contain files and directories such as:

fxmanifest.lua
entrypoint.js
core/
resource/
panel/
nui/

If your artifact uses a different system-resource name or layout, stop and request compatibility guidance. Do not create a second monitor resource to imitate this layout.

These are incorrect destinations

• Your ordinary gameplay resources directory.
• A newly created resources/[standalone]/monitor directory.
• txData or an individual txAdmin profile folder.
• The docs website's static directory.
• An inactive copy of FXServer that your service does not launch.

Do not add ensure monitor to server.cfg to install the theme. txAdmin is already integrated with FXServer.

5. Back up the installation

Before the maintenance window:

1. Record your installed txAdmin version and artifact build.
2. Record the complete path to the active monitor folder.
3. Copy the original panel and nui folders to a separate backup location outside the live system resource.
4. Preferably keep a backup of the complete original monitor folder as well.
5. Keep an independent backup of txData and your normal server configuration.
6. Label the backup with its version and date so it can be matched to this installation later.

Do not place backup folders inside the live monitor/panel or monitor/nui directories.

The theme installation does not require editing or replacing txData. That directory holds persistent txAdmin data and must remain in place.

6. Stop the complete process

Schedule a maintenance window and notify connected players before stopping the server.

1. Stop the managed game server gracefully.
2. Stop the parent FXServer process that runs txAdmin through your terminal, Windows service, Linux service, container manager or hosting panel.
3. Verify that the process stays stopped and is not automatically relaunched by a service manager.
4. Confirm that the txAdmin web panel is no longer being served by that process.

A game-server restart from within txAdmin can leave the parent txAdmin process running. The installation needs a full process stop/start so the panel is loaded again as well.

Keep access to your host panel, service manager or terminal available. You will need it to start txAdmin again after the web panel is offline.

Do not use restart monitor as an installation shortcut. The bundled upstream development documentation notes that restarting this resource can trigger crash handling and a server restart.

7. Install on Windows

With the complete process stopped:

1. Open the extracted download's monitor directory in File Explorer.
2. Open your active installed monitor directory in a second window.
3. Confirm both versions match the compatibility check above.
4. Move the installed panel and nui folders to your separate backup location if you have not already done so.
5. Copy the download's complete panel folder into the installed monitor directory.
6. Copy the download's complete nui folder into the same installed monitor directory.
7. Wait for both transfers to finish.
8. Confirm the account running FXServer can read the copied folders and files.

The resulting paths must include:

...\citizen\system_resources\monitor\panel\index.html
...\citizen\system_resources\monitor\panel\index-l89wohw6.v800.js
...\citizen\system_resources\monitor\panel\index-iw21afnq.v800.css
...\citizen\system_resources\monitor\nui\index.html
...\citizen\system_resources\monitor\nui\index.js
...\citizen\system_resources\monitor\nui\index.css

An accidental extra monitor directory is incorrect:

...\system_resources\monitor\monitor\panel\index.html

Leave the existing backend, Lua resource scripts, manifest and entrypoint unchanged.

8. Install on Linux or through SFTP

With the complete process stopped:

1. Connect using your host's supported file manager or SFTP client.
2. Navigate to the confirmed active monitor directory.
3. Download or move the original panel and nui folders into your backup location outside the live directory.
4. Upload the extracted download's entire panel folder.
5. Upload the extracted download's entire nui folder.
6. Include hidden content such as panel/.vite/manifest.json.
7. Check the transfer queue for failed or skipped files.
8. Verify ownership and read access for the account running FXServer.

Keep the original folder names and filename capitalization. Linux paths are case-sensitive.

Do not apply chmod 777 to fix a transfer problem. Use the same ownership and access pattern as the working original installation, or ask your host to correct permissions.

Containers and managed hosts

Install into the persistent location actually used by the running container or service. Changes made only to an ephemeral container filesystem may disappear when the container is recreated.

If your provider replaces system resources on startup, ask how to persist custom interface files. Repeatedly uploading into an automatically regenerated directory will not resolve that behavior.

9. Start txAdmin again

1. Start the parent FXServer/txAdmin process using your existing launch method.
2. Watch startup output for missing files, permission errors or txAdmin startup failures.
3. Open your normal txAdmin URL and sign in.
4. Start the managed game server if it has not started automatically.
5. Wait for the server to finish loading before joining.

Keep your original startup arguments, port, profile and server configuration. The theme does not require a different launch command.

Do not open panel/index.html directly from your computer. It expects runtime values supplied by txAdmin and includes an error for a missing window.txConsts value when opened outside txAdmin.

10. Verify the browser panel

1. Open the panel through your normal txAdmin address.
2. Hard-refresh the page with Ctrl + F5 or Ctrl + Shift + R.
3. If the old appearance remains, test in a private browser window.
4. Select dark mode if available when checking the intended neon appearance.
5. Check navigation, buttons, forms and dialogs for pink accents.
6. Open the dashboard, player list, live console and settings.
7. Confirm that text remains readable and controls respond normally.

If necessary, open browser developer tools and check the Network tab for failed CSS, JavaScript or font requests. A successful upload should serve the exact JS and CSS filenames referenced by the installed panel/index.html.

Avoid changing operational settings solely to test the colors.

11. Verify the in-game menu

Reconnect to the server after the complete restart, then:

1. Sign in with an account registered in txAdmin's Admin Manager.
2. Ensure the account has its appropriate Cfx.re or Discord identifier linked.
3. Confirm the menu is enabled in txAdmin settings.
4. Open chat and enter /tx or /txadmin.
5. Inspect the menu background, tab selection, icons and hover styling.
6. Open the player list and a player details dialog to check readability.
7. Open any embedded panel view available to your account and check that it loads.

You can also configure the menu key under Settings → Key Bindings → FiveM → (txAdmin) Menu: Open Main Page.

The theme does not grant admin permissions. If authentication needs to be retried, the bundled documentation provides /txAdmin-reauth.

If only the in-game interface looks unchanged, confirm that both nui/index.js and nui/index.css were transferred, then fully reconnect before considering further cache troubleshooting.

12. Troubleshooting

Symptom	Check and next action
Everything still looks stock	Confirm you edited the active artifact directory, completed both folder transfers and restarted the parent process.
Browser panel changed, menu did not	Check nui/, including its JS and CSS; reconnect; confirm you opened the actual txAdmin menu.
Menu changed, browser panel did not	Check panel/, hard-refresh and confirm the browser URL belongs to the installation you edited.
Panel is blank	Check failed JS/CSS requests and browser console errors; confirm HTML and assets came from the same package. Restore the original UI if needed.
CSS or JS returns 404	Check folder nesting, exact filenames, capitalization, file permissions and incomplete uploads.
Fonts or images are missing	Transfer the complete folders, including font files, image subfolders and hidden content.
window.txConsts is undefined	Open the panel through the running txAdmin service rather than opening its HTML file directly.
/tx does nothing or access is denied	Check the menu setting, admin registration and linked identifiers. Retry authentication with /txAdmin-reauth where appropriate.
Theme disappears after an artifact update	The update may have replaced system resources. Check the new txAdmin version before installing a matching theme again.
Theme disappears after every startup	Check host automation, container persistence and whether another artifact directory is being launched.
FXServer or txAdmin fails to start	Review startup logs. If files outside panel/nui were replaced, restore the matching original installation and retry with only the UI folders.

When a hard refresh is not enough

Test a private window first. If it works there, clear cached site data for your txAdmin origin and sign in again. Clearing site data can remove your current login session.

For the in-game menu, reconnect first. Do not delete your server's txData, player database or gameplay resources as a theme-cache fix.

Mismatched versions

A frontend from one txAdmin release can expect data or behavior that another backend does not provide. Restoring a working same-version UI is the correct first step when errors begin immediately after installation.

Do not rename the compiled assets to imitate another release, change the manifest version to claim compatibility, or replace the backend simply to suppress a mismatch.

13. Updates and maintenance

Before updating FXServer artifacts or txAdmin:

1. Back up the current installation and record its versions.
2. Expect that artifact replacement may overwrite customized system-resource files.
3. Check the txAdmin version included in the update.
4. Obtain a theme release intended for that version.
5. Test on a non-production installation before applying it to your live server.
6. Repeat the browser and in-game verification checks.

Keep security and stability updates current. Do not stay on an old backend solely to retain a visual theme; use the stock interface until a compatible theme is available.

14. Remove the theme or roll back

To restore the original appearance:

1. Stop the managed server and the complete parent FXServer/txAdmin process.
2. Move the themed panel and nui folders out of the live directory.
3. Restore the original panel and nui folders backed up from that same txAdmin version.
4. If other txAdmin files were replaced, restore the matching complete original monitor installation instead.
5. Leave txData and gameplay configuration in place.
6. Start the parent process normally.
7. Hard-refresh the browser and reconnect in-game.
8. Confirm both interfaces and normal administration work again.

If you no longer have a backup, obtain clean official files matching the installed version rather than mixing files from unrelated releases.

15. Request support

Join the Hotspot Creations Discord and include:

• Theme package/release name.
• Installed txAdmin version and FXServer artifact build.
• Windows, Linux, container or managed-host details.
• Whether the problem affects the browser panel, in-game menu or both.
• The target directory used, with private account information removed.
• Relevant startup errors, browser console errors or failed asset requests.
• Screenshots and the steps needed to reproduce the issue.
• Whether restoring the original UI resolves it.

Remove passwords, tokens, license keys and private player information from anything you share.

Installation checklist

• Existing txAdmin version matches the theme package.
• Active system-resource path confirmed.
• Original UI and persistent data backed up.
• Complete parent FXServer/txAdmin process stopped.
• Complete panel and nui folders installed without extra nesting.
• Backend and persistent profile data preserved.
• Parent process restarted successfully.
• Browser panel verified after a hard refresh.
• In-game menu verified after reconnecting.
• Matching rollback backup retained.

Reference material

This guide was prepared from the supplied monitor.zip: its manifest, HTML asset references, compiled UI styling and bundled menu documentation. File structure and version details apply to that package. Live installation and gameplay testing were not performed while preparing this guide.

For upstream behavior, see the official txAdmin project and development documentation. Custom HSC styling is maintained separately from upstream txAdmin.