Kruiger Ultimate Suite
Kruiger Ultimate Suite combines:
- KruigerHUD
- KruigerHeadtags
- KruigerPriority
- KruigerDuty
- KruigerChat
The suite is most reliable when you configure the shared concepts once and use the same identifiers everywhere.
Established command set
HUD
/hud
/postal [code]
/togglespeed
Headtags / Gangtags
/headtag
/headtags
/gangtag
/gantag
/headtagsettings
/showheadtagself
Duty
/duty
/dutysetup
Priority
/priority
Chat
/me
/gme
/do
/social
/sms
/ad
/chatsettings
/chattag
Established controls include E, L, and F1, depending on the component/configuration.
Permission namespaces
The package work established these namespaces:
headtag.kruiger.*
gangtag.kruiger.*
kruiger.priority.*
Use the exact granular ACEs shipped with your release.
Recommended installation order
- Back up the server.
- Install the required postal map/dependencies.
- Upload all suite components.
- Decide your internal department identifiers.
- Configure those departments consistently across components.
- Configure Headtags/Gangtags.
- Configure duty locations.
- Configure priority statuses/cooldown.
- Configure Chat Tags and chat behavior.
- Configure ACE permissions.
- Configure optional Discord logging.
- Disable conflicting HUD/chat/priority/headtag resources only when ready.
- Start dependencies before suite resources.
- Cold boot.
- Test each component separately.
- Test cross-component behavior.
Department planning worksheet
Before editing configs, make a small table:
| Internal ID | Display name | Duty access | Headtag | Chat tag |
|---|---|---|---|---|
sahp |
San Andreas Highway Patrol | configured group | configured tag | configured tag |
Use your own identifiers. The important part is consistency.
Priority statuses
The established states are Available, Active, On Hold, and Cooldown.
Postal
The HUD package was designed around the recommended Big Daddy Scripts Postal Map. Validate the map before troubleshooting postal alignment.
Logging
Optional Discord logging is part of the suite configuration work. Keep webhooks private and use separate logging destinations when that helps operations.
Full acceptance test
Do not call the suite finished because it starts. Test:
- HUD on foot.
- HUD in multiple vehicles.
- Postal command.
- Headtag authorized/unauthorized.
- Gangtag authorized/unauthorized.
- Duty in/out.
- Duty setup permission.
- Every priority state.
- Cooldown.
- Every enabled chat command.
- Chat tag.
- User settings.
- Reconnect synchronization.
- Full cold boot.
- Multi-player visibility.
- Console/client errors.
Troubleshooting the suite
When several features fail, disable the assumption that “the suite is one problem.” Verify each component individually, then shared identifiers, permissions, start order, and conflicts.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.