NXM Aduty: ESX Dependencies and Staff Permission Checks

NXM Aduty provides a staff-duty interface for ranks, outfits and activity logs. The original release lists ESX Legacy, oxmysql, skinchanger and MariaDB/MySQL. It is an escrowed resource; the feature list is not an independent security review.

NXM Aduty original release

Prepare the database and permissions

Back up the database before first start: the creator says the resource creates its tables automatically. Follow the delivered ACE configuration and start the supplied NXM_Aduty resource. The documented /adutyui command opens rank management; /ad toggles duty and /adoff targets a player for forced duty exit. Keep those powers limited to the intended staff roles.

Test duty exit and reconnect recovery

Use separate ordinary-player, junior-staff and administrator accounts. Verify who can edit ranks, enable powers, view logs and force another player off duty. Enter and leave duty, then disconnect while on duty and check the restored job, outfit and powers. If Discord logging is enabled, keep its webhook server-side and restrict access to logs containing player identifiers.

Confirm current availability through the creator’s release links before planning deployment. No zero-performance-impact or security guarantee is inferred from its marketing. Source checked on 10 September 2026.