Kruiger Priority

Kruiger Priority is a standalone FiveM roleplay priority management system that allows authorized users to control and display the server's current priority status.

How to Use In-Game

Use:

/priority

to open the Priority Management interface.

Authorized users can change the current server Priority state.

Supported states can include:

• Priority Available
• Priority Active
• Priority On Hold
• Priority Cooldown

Changes are synchronized so players receive the updated Priority information.

Configuring Priority

Server owners can configure the Priority system through its customer-editable configuration.

This allows you to adapt the system to your server without editing protected core files.

Adding/Changing Permissions

Priority management uses FiveM ACE permissions under:

kruiger.priority.*

To authorize additional staff or groups:

1. Open your Priority permission configuration and supplied ACE examples.
2. Determine which Priority permission the user/group requires.
3. Add the appropriate ACE permission to your server.cfg.
4. Assign that permission to the desired FiveM principal/group.
5. Save your configuration.
6. Restart the resource/server.
7. Test /priority using an authorized account.

This allows you to give Priority control to groups such as:

• Owners
• Management
• Administrators
• Moderators
• LEO supervisors
• Dispatch
• Event coordinators
• Custom server groups

Regular players do not need Priority-management permission.

Discord Logging

If enabled in the supplied configuration, supported Priority activity can use your own configured Discord logging.

Any webhook used by your server should be your own.

Installation

1. Place Kruiger-Priority in your resources folder.
2. Add ensure Kruiger-Priority to server.cfg.
3. Configure Priority.
4. Configure the required ACE permissions.
5. Configure optional logging if desired.
6. Restart the resource/server.
7. Authorized users can use /priority.

Standalone

Kruiger HUD is not required.

Version

Kruiger Priority v1.0.0 — Standalone

Support

https://discord.gg/DbnPHsU9jg

Developed by Kruiger Labs LLC

Kruiger Priority

Kruiger Priority is a standalone FiveM roleplay priority management system that allows authorized users to control and display the server's current priority status.

How to Use In-Game

Use:

/priority

to open the Priority Management interface.

Authorized users can change the current server Priority state.

Supported states can include:

• Priority Available
• Priority Active
• Priority On Hold
• Priority Cooldown

Changes are synchronized so players receive the updated Priority information.

Configuring Priority

Server owners can configure the Priority system through its customer-editable configuration.

This allows you to adapt the system to your server without editing protected core files.

Adding/Changing Permissions

Priority management uses FiveM ACE permissions under:

kruiger.priority.*

To authorize additional staff or groups:

1. Open your Priority permission configuration and supplied ACE examples.
2. Determine which Priority permission the user/group requires.
3. Add the appropriate ACE permission to your server.cfg.
4. Assign that permission to the desired FiveM principal/group.
5. Save your configuration.
6. Restart the resource/server.
7. Test /priority using an authorized account.

This allows you to give Priority control to groups such as:

• Owners
• Management
• Administrators
• Moderators
• LEO supervisors
• Dispatch
• Event coordinators
• Custom server groups

Regular players do not need Priority-management permission.

Discord Logging

If enabled in the supplied configuration, supported Priority activity can use your own configured Discord logging.

Any webhook used by your server should be your own.

Installation

1. Place Kruiger-Priority in your resources folder.
2. Add ensure Kruiger-Priority to server.cfg.
3. Configure Priority.
4. Configure the required ACE permissions.
5. Configure optional logging if desired.
6. Restart the resource/server.
7. Authorized users can use /priority.

Standalone

Kruiger HUD is not required.

Version

Kruiger Priority v1.0.0 — Standalone

Support

https://discord.gg/DbnPHsU9jg

Developed by Kruiger Labs LLC

Kruiger Duty

Kruiger Duty is a standalone FiveM duty-management system designed for law enforcement, Fire/EMS, federal agencies, server staff, and custom organizations.

How to Use In-Game

Use:

/duty

to access the Duty system where permitted.

Servers can also configure physical Duty locations.

When a player approaches a configured Duty point, they can interact using:

E

to access the Duty interface.

Players can then manage their supported On Duty / Off Duty state.

Administrative Setup

Authorized administrators can use:

/dutysetup

for the supported Duty setup functionality.

Administrative functionality should only be granted to trusted server personnel.

Adding More Departments

You are not limited to the default departments.

Kruiger Duty can be configured around your server's own structure.

Examples include:

• LSPD
• BCSO
• SAHP
• Fire/EMS
• FIB
• DHS
• IAA
• Corrections
• Dispatch
• Server Staff
• Custom organizations

Step 1 — Open the Duty Configuration

Open the customer-editable Kruiger Duty configuration and locate the configured departments.

Step 2 — Create the Department

Use an existing department entry as the template for your new department.

Give the department a unique identifier and configure its supported information using the same structure.

Step 3 — Configure Access

Configure the appropriate permissions/access for the department.

Only players intended to use the department should receive its required access.

Step 4 — Add Duty Locations

Configure the locations where members of that department can access Duty.

You can create locations at places such as:

• Police stations
• Sheriff's offices
• Highway patrol stations
• Fire stations
• Hospitals
• Federal buildings
• Staff areas
• Organization headquarters

Step 5 — Restart

Save your changes and restart Kruiger-Duty.

The new department and its configured Duty locations can then be used in-game.

Adding Additional Duty Points

Departments are not restricted to a single Duty location.

For example, a Sheriff's Office could have Duty access at multiple stations.

To add another point:

1. Open the customer-editable Duty configuration/data.
2. Locate the existing Duty locations.
3. Use an existing point as a template.
4. Add the new location using the required structure and coordinates.
5. Associate it with the appropriate department where required.
6. Save your changes.
7. Restart Kruiger Duty.
8. Visit the new location and test the E interaction.

Headtags Integration

Kruiger Duty can optionally work alongside Kruiger Headtags.

Headtags are not required for the Standalone edition.

Installation

1. Place Kruiger-Duty in your resources folder.
2. Add ensure Kruiger-Duty to server.cfg.
3. Configure departments.
4. Configure department access.
5. Configure Duty locations.
6. Configure administrative permissions.
7. Restart the resource/server.
8. Test /duty, configured Duty points, and /dutysetup with the appropriate accounts.

Version

Kruiger Duty v1.0.0 — Standalone

Support

https://discord.gg/DbnPHsU9jg

Developed by Kruiger Labs LLC

Kruiger Duty

Kruiger Duty is a standalone FiveM duty-management system designed for law enforcement, Fire/EMS, federal agencies, server staff, and custom organizations.

How to Use In-Game

Use:

/duty

to access the Duty system where permitted.

Servers can also configure physical Duty locations.

When a player approaches a configured Duty point, they can interact using:

E

to access the Duty interface.

Players can then manage their supported On Duty / Off Duty state.

Administrative Setup

Authorized administrators can use:

/dutysetup

for the supported Duty setup functionality.

Administrative functionality should only be granted to trusted server personnel.

Adding More Departments

You are not limited to the default departments.

Kruiger Duty can be configured around your server's own structure.

Examples include:

• LSPD
• BCSO
• SAHP
• Fire/EMS
• FIB
• DHS
• IAA
• Corrections
• Dispatch
• Server Staff
• Custom organizations

Step 1 — Open the Duty Configuration

Open the customer-editable Kruiger Duty configuration and locate the configured departments.

Step 2 — Create the Department

Use an existing department entry as the template for your new department.

Give the department a unique identifier and configure its supported information using the same structure.

Step 3 — Configure Access

Configure the appropriate permissions/access for the department.

Only players intended to use the department should receive its required access.

Step 4 — Add Duty Locations

Configure the locations where members of that department can access Duty.

You can create locations at places such as:

• Police stations
• Sheriff's offices
• Highway patrol stations
• Fire stations
• Hospitals
• Federal buildings
• Staff areas
• Organization headquarters

Step 5 — Restart

Save your changes and restart Kruiger-Duty.

The new department and its configured Duty locations can then be used in-game.

Adding Additional Duty Points

Departments are not restricted to a single Duty location.

For example, a Sheriff's Office could have Duty access at multiple stations.

To add another point:

1. Open the customer-editable Duty configuration/data.
2. Locate the existing Duty locations.
3. Use an existing point as a template.
4. Add the new location using the required structure and coordinates.
5. Associate it with the appropriate department where required.
6. Save your changes.
7. Restart Kruiger Duty.
8. Visit the new location and test the E interaction.

Headtags Integration

Kruiger Duty can optionally work alongside Kruiger Headtags.

Headtags are not required for the Standalone edition.

Installation

1. Place Kruiger-Duty in your resources folder.
2. Add ensure Kruiger-Duty to server.cfg.
3. Configure departments.
4. Configure department access.
5. Configure Duty locations.
6. Configure administrative permissions.
7. Restart the resource/server.
8. Test /duty, configured Duty points, and /dutysetup with the appropriate accounts.

Version

Kruiger Duty v1.0.0 — Standalone

Support

https://discord.gg/DbnPHsU9jg

Developed by Kruiger Labs LLC

Kruiger Chat

Kruiger Chat is a standalone FiveM chat replacement featuring roleplay messaging, social communication, advertisements, Chat Tags, player settings, staff functionality, chat management, and optional Discord logging.

How to Use In-Game

Use your normal FiveM chat control to open Chat.

Roleplay Commands

/me [message]

Describe an action performed by your character.

Example:

/me reaches into their pocket and removes their ID.

/gme [message]

Use the supported global ME-style functionality.

/do [message]

Describe a scene, condition, or roleplay detail.

Example:

/do The vehicle's front windshield would be shattered.

Communication

/social

Access supported social functionality.

/sms

Access supported SMS functionality.

/ad

Use the configured advertisement functionality.

Player Settings

/chatsettings

Open supported player Chat settings.

Chat Tags

/chattag

Access the Chat Tag system.

Chat Visibility

L

Controls the supported Chat visibility/display functionality.

Chat History

F1

Access supported Chat-history scrolling functionality.

Adding Chat Tags

Server owners can customize supported Chat Tags rather than being restricted to the included options.

Chat Tags can represent:

• Owner
• Management
• Administrator
• Moderator
• Developer
• Police
• Fire/EMS
• VIP
• Supporter
• Custom community roles

To add a supported custom Chat Tag:

1. Open the customer-editable Kruiger Chat configuration.
2. Locate the existing Chat Tag configuration.
3. Use an existing entry as your template.
4. Create a unique entry for the new tag.
5. Configure its supported display information.
6. Configure any required access/permission according to the supplied configuration.
7. Save your changes.
8. Restart Kruiger-Chat.
9. Test the new tag using /chattag with an authorized player.

Configuring Chat Features

Server owners can customize supported Chat behavior through the included configuration.

This includes configurable functionality for the systems exposed by the resource, including supported commands, Chat Tags, logging, and other customer-facing options.

Use the existing configuration values and included examples as the expected structure when adding or changing entries.

Staff Functionality

Kruiger Chat includes permission-controlled functionality for authorized staff, including supported:

• Staff messaging
• Chat management
• Chat locking
• Staff-only functionality

Only trusted groups should receive administrative Chat permissions.

Discord Logging

Discord webhook logging is optional.

To configure it:

1. Create your own Discord webhook in the channel where you want supported logs delivered.
2. Open Kruiger Chat's customer-editable configuration.
3. Enable the supported logging option.
4. Enter your own webhook where instructed.
5. Save the configuration.
6. Restart Kruiger Chat.
7. Test the relevant functionality and confirm logs reach your channel.

Kruiger Labs does not require your Chat logs to be sent to a Kruiger Labs webhook.

Never publicly share your Discord webhook URL.

Installation

1. Place Kruiger-Chat inside your resources folder.
2. Disable any conflicting Chat replacement.
3. Add ensure Kruiger-Chat to server.cfg.
4. Configure Chat settings.
5. Configure Chat Tags and permissions.
6. Configure optional Discord logging.
7. Restart the resource/server.
8. Test normal Chat, roleplay commands, Chat Tags, and staff functionality.

Standalone

Does not require HUD, Priority, Headtags, Duty, ESX, QBCore, or Qbox.

No external database is required for normal operation.

Version

Kruiger Chat v1.0.0 — Standalone

Support

https://discord.gg/DbnPHsU9jg

Developed by Kruiger Labs LLC

Kruiger Chat

Kruiger Chat is a standalone FiveM chat replacement featuring roleplay messaging, social communication, advertisements, Chat Tags, player settings, staff functionality, chat management, and optional Discord logging.

How to Use In-Game

Use your normal FiveM chat control to open Chat.

Roleplay Commands

/me [message]

Describe an action performed by your character.

Example:

/me reaches into their pocket and removes their ID.

/gme [message]

Use the supported global ME-style functionality.

/do [message]

Describe a scene, condition, or roleplay detail.

Example:

/do The vehicle's front windshield would be shattered.

Communication

/social

Access supported social functionality.

/sms

Access supported SMS functionality.

/ad

Use the configured advertisement functionality.

Player Settings

/chatsettings

Open supported player Chat settings.

Chat Tags

/chattag

Access the Chat Tag system.

Chat Visibility

L

Controls the supported Chat visibility/display functionality.

Chat History

F1

Access supported Chat-history scrolling functionality.

Adding Chat Tags

Server owners can customize supported Chat Tags rather than being restricted to the included options.

Chat Tags can represent:

• Owner
• Management
• Administrator
• Moderator
• Developer
• Police
• Fire/EMS
• VIP
• Supporter
• Custom community roles

To add a supported custom Chat Tag:

1. Open the customer-editable Kruiger Chat configuration.
2. Locate the existing Chat Tag configuration.
3. Use an existing entry as your template.
4. Create a unique entry for the new tag.
5. Configure its supported display information.
6. Configure any required access/permission according to the supplied configuration.
7. Save your changes.
8. Restart Kruiger-Chat.
9. Test the new tag using /chattag with an authorized player.

Configuring Chat Features

Server owners can customize supported Chat behavior through the included configuration.

This includes configurable functionality for the systems exposed by the resource, including supported commands, Chat Tags, logging, and other customer-facing options.

Use the existing configuration values and included examples as the expected structure when adding or changing entries.

Staff Functionality

Kruiger Chat includes permission-controlled functionality for authorized staff, including supported:

• Staff messaging
• Chat management
• Chat locking
• Staff-only functionality

Only trusted groups should receive administrative Chat permissions.

Discord Logging

Discord webhook logging is optional.

To configure it:

1. Create your own Discord webhook in the channel where you want supported logs delivered.
2. Open Kruiger Chat's customer-editable configuration.
3. Enable the supported logging option.
4. Enter your own webhook where instructed.
5. Save the configuration.
6. Restart Kruiger Chat.
7. Test the relevant functionality and confirm logs reach your channel.

Kruiger Labs does not require your Chat logs to be sent to a Kruiger Labs webhook.

Never publicly share your Discord webhook URL.

Installation

1. Place Kruiger-Chat inside your resources folder.
2. Disable any conflicting Chat replacement.
3. Add ensure Kruiger-Chat to server.cfg.
4. Configure Chat settings.
5. Configure Chat Tags and permissions.
6. Configure optional Discord logging.
7. Restart the resource/server.
8. Test normal Chat, roleplay commands, Chat Tags, and staff functionality.

Standalone

Does not require HUD, Priority, Headtags, Duty, ESX, QBCore, or Qbox.

No external database is required for normal operation.

Version

Kruiger Chat v1.0.0 — Standalone

Support

https://discord.gg/DbnPHsU9jg

Developed by Kruiger Labs LLC

Kruiger HUD

Kruiger HUD is a modern standalone FiveM heads-up display featuring player information, vehicle data, navigation tools, speed limits, seatbelt functionality, postal navigation, and customizable HUD settings.

This edition is completely standalone and does not require any other Kruiger resource.

How to Use In-Game

The HUD automatically loads when a player joins the server.

HUD Settings

Use:

/hud

to open the HUD settings interface.

Players can customize supported HUD display preferences directly in-game.

Postal Navigation

Use:

/postal [postal code]

Example:

/postal 301

The system locates the configured postal and provides navigation toward that location.

Recommended Postal Map

For visible map postals that align with Kruiger HUD's postal system, use the Big Daddy Scripts Postal Map:

https://bigdaddyscripts.com/Products/View/2963/Postal-Map

Using a different postal map or postal dataset may cause the numbers displayed on the map to differ from the locations used by /postal.

The Postal Map is a third-party resource and is not developed, owned, or distributed by Kruiger Labs LLC.

Speed Limit

Use:

/togglespeed

to toggle the supported speed-limit display.

Vehicle HUD

The vehicle HUD activates automatically when entering a supported vehicle.

Supported information includes vehicle speed, speed-limit information, navigation information, vehicle indicators, and seatbelt status.

Leaving the vehicle automatically returns the HUD to its normal state.

Configuring the HUD

Server owners can customize supported HUD functionality through the customer-editable configuration supplied with the resource.

To change a setting:

1. Open the Kruiger HUD configuration.
2. Locate the setting you want to change.
3. Follow the structure and comments supplied with the configuration.
4. Save the file.
5. Restart Kruiger-Hud.

The protected core does not need to be modified for normal configuration.

Installation

1. Place Kruiger-Hud inside your FiveM resources folder.
2. Add ensure Kruiger-Hud to server.cfg.
3. Configure the customer-editable settings.
4. Install the recommended postal map if matching visible postals are desired.
5. Restart the resource/server.
6. Join the server. The HUD loads automatically.

Standalone

Does not require Kruiger Priority, Headtags, Duty, Chat, ESX, QBCore, or Qbox.

Version

Kruiger HUD v1.0.0 — Standalone

Support

https://discord.gg/DbnPHsU9jg

Developed by Kruiger Labs LLC

Kruiger HUD

Kruiger HUD is a modern standalone FiveM heads-up display featuring player information, vehicle data, navigation tools, speed limits, seatbelt functionality, postal navigation, and customizable HUD settings.

This edition is completely standalone and does not require any other Kruiger resource.

How to Use In-Game

The HUD automatically loads when a player joins the server.

HUD Settings

Use:

/hud

to open the HUD settings interface.

Players can customize supported HUD display preferences directly in-game.

Postal Navigation

Use:

/postal [postal code]

Example:

/postal 301

The system locates the configured postal and provides navigation toward that location.

Recommended Postal Map

For visible map postals that align with Kruiger HUD's postal system, use the Big Daddy Scripts Postal Map:

https://bigdaddyscripts.com/Products/View/2963/Postal-Map

Using a different postal map or postal dataset may cause the numbers displayed on the map to differ from the locations used by /postal.

The Postal Map is a third-party resource and is not developed, owned, or distributed by Kruiger Labs LLC.

Speed Limit

Use:

/togglespeed

to toggle the supported speed-limit display.

Vehicle HUD

The vehicle HUD activates automatically when entering a supported vehicle.

Supported information includes vehicle speed, speed-limit information, navigation information, vehicle indicators, and seatbelt status.

Leaving the vehicle automatically returns the HUD to its normal state.

Configuring the HUD

Server owners can customize supported HUD functionality through the customer-editable configuration supplied with the resource.

To change a setting:

1. Open the Kruiger HUD configuration.
2. Locate the setting you want to change.
3. Follow the structure and comments supplied with the configuration.
4. Save the file.
5. Restart Kruiger-Hud.

The protected core does not need to be modified for normal configuration.

Installation

1. Place Kruiger-Hud inside your FiveM resources folder.
2. Add ensure Kruiger-Hud to server.cfg.
3. Configure the customer-editable settings.
4. Install the recommended postal map if matching visible postals are desired.
5. Restart the resource/server.
6. Join the server. The HUD loads automatically.

Standalone

Does not require Kruiger Priority, Headtags, Duty, Chat, ESX, QBCore, or Qbox.

Version

Kruiger HUD v1.0.0 — Standalone

Support

https://discord.gg/DbnPHsU9jg

Developed by Kruiger Labs LLC

Kruiger Headtags

Kruiger Headtags is a standalone FiveM player-identification system featuring configurable overhead Headtags, Gang/Department tags, ACE permissions, and player-controlled display settings.

How to Use In-Game

Use:

/headtag

or:

/headtags

to access the Headtag system.

Use:

/gangtag

to access Gang/Department tags.

/gantag

is also supported as an alternate command.

Use:

/headtagsettings

to open the standalone Headtag settings interface.

Use:

/showheadtagself

for supported self-Headtag display functionality.

Adding New Headtags

You are not limited to the included Headtags.

Server owners can create additional tags through the customer-editable Headtags configuration.

Step 1 — Open the Configuration

Open the supplied Kruiger Headtags configuration.

Locate the existing Headtag definitions.

Step 2 — Use an Existing Tag as a Template

Copy the structure of an existing tag and create a new entry.

You can create tags for:

• Owner
• Management
• Developer
• Administrator
• Moderator
• Police
• Sheriff
• State Police
• Fire/EMS
• Federal agencies
• Dispatch
• VIP groups
• Custom server roles

Give each configured tag a unique identifier.

Step 3 — Configure Permissions

Headtag permissions use:

headtag.kruiger.*

Create/grant the appropriate ACE permission for the tag according to the included configuration and ACE examples.

Step 4 — Grant Access

Assign the corresponding ACE permission to the FiveM principal/group that should receive the tag.

Players without the required permission cannot use restricted tags.

Step 5 — Restart

Save your changes and restart Kruiger-Headtags.

Authorized players can then access the newly configured tag through /headtag or /headtags.

Adding Gang / Department Tags

Gangtags are also customizable.

These do not have to represent literal gangs. They can be used for departments, subdivisions, organizations, teams, agencies, or other groups.

To add one:

1. Open the Gang/Department tag section of the configuration.
2. Copy an existing entry as your template.
3. Give the new entry a unique identifier.
4. Configure its supported display information.
5. Configure its permission.
6. Grant the permission to the appropriate group.
7. Save the configuration.
8. Restart the resource.
9. Authorized players can access it through /gangtag.

Gang/Department permissions use:

gangtag.kruiger.*

Example Uses

A law-enforcement server could configure Department tags for:

• LSPD
• BCSO
• SAHP
• FIB
• DHS
• Dispatch

while keeping staff Headtags completely separate.

Optional Duty Integration

Kruiger Headtags can optionally work alongside Kruiger Duty.

Kruiger Duty is not required for the Standalone edition.

Installation

1. Place Kruiger-Headtags in your resources folder.
2. Add ensure Kruiger-Headtags to server.cfg.
3. Configure your Headtags.
4. Configure Gang/Department tags.
5. Configure ACE permissions.
6. Restart the resource/server.
7. Use /headtagsettings to configure player display preferences.

Version

Kruiger Headtags v1.0.0 — Standalone

Support

https://discord.gg/DbnPHsU9jg

Developed by Kruiger Labs LLC

Kruiger Headtags

Kruiger Headtags is a standalone FiveM player-identification system featuring configurable overhead Headtags, Gang/Department tags, ACE permissions, and player-controlled display settings.

How to Use In-Game

Use:

/headtag

or:

/headtags

to access the Headtag system.

Use:

/gangtag

to access Gang/Department tags.

/gantag

is also supported as an alternate command.

Use:

/headtagsettings

to open the standalone Headtag settings interface.

Use:

/showheadtagself

for supported self-Headtag display functionality.

Adding New Headtags

You are not limited to the included Headtags.

Server owners can create additional tags through the customer-editable Headtags configuration.

Step 1 — Open the Configuration

Open the supplied Kruiger Headtags configuration.

Locate the existing Headtag definitions.

Step 2 — Use an Existing Tag as a Template

Copy the structure of an existing tag and create a new entry.

You can create tags for:

• Owner
• Management
• Developer
• Administrator
• Moderator
• Police
• Sheriff
• State Police
• Fire/EMS
• Federal agencies
• Dispatch
• VIP groups
• Custom server roles

Give each configured tag a unique identifier.

Step 3 — Configure Permissions

Headtag permissions use:

headtag.kruiger.*

Create/grant the appropriate ACE permission for the tag according to the included configuration and ACE examples.

Step 4 — Grant Access

Assign the corresponding ACE permission to the FiveM principal/group that should receive the tag.

Players without the required permission cannot use restricted tags.

Step 5 — Restart

Save your changes and restart Kruiger-Headtags.

Authorized players can then access the newly configured tag through /headtag or /headtags.

Adding Gang / Department Tags

Gangtags are also customizable.

These do not have to represent literal gangs. They can be used for departments, subdivisions, organizations, teams, agencies, or other groups.

To add one:

1. Open the Gang/Department tag section of the configuration.
2. Copy an existing entry as your template.
3. Give the new entry a unique identifier.
4. Configure its supported display information.
5. Configure its permission.
6. Grant the permission to the appropriate group.
7. Save the configuration.
8. Restart the resource.
9. Authorized players can access it through /gangtag.

Gang/Department permissions use:

gangtag.kruiger.*

Example Uses

A law-enforcement server could configure Department tags for:

• LSPD
• BCSO
• SAHP
• FIB
• DHS
• Dispatch

while keeping staff Headtags completely separate.

Optional Duty Integration

Kruiger Headtags can optionally work alongside Kruiger Duty.

Kruiger Duty is not required for the Standalone edition.

Installation

1. Place Kruiger-Headtags in your resources folder.
2. Add ensure Kruiger-Headtags to server.cfg.
3. Configure your Headtags.
4. Configure Gang/Department tags.
5. Configure ACE permissions.
6. Restart the resource/server.
7. Use /headtagsettings to configure player display preferences.

Version

Kruiger Headtags v1.0.0 — Standalone

Support

https://discord.gg/DbnPHsU9jg

Developed by Kruiger Labs LLC