Common Issues & Fixes

Common Issues & Fixes

Common Advanced AOP setup issues usually come from PolyZone ensure order, missing html files, ACE permission setup, staff bypass testing, or boundary configuration.

AOP Commands Do Not Work

• Confirm Advanced AOP is started.
• Confirm PolyZone started before Advanced AOP.
• Check the configured ACE permission, usually teedle.aop.
• Verify DiscordAcePerms or your ACE bridge is mapping Discord staff roles to the correct ACE group.
• Add an ACE line such as add_ace group.admin teedle.aop allow, then restart the resource.

Warning UI Does Not Show

• Confirm the html folder was uploaded with index.html, style.css, and app.js.
• Confirm Config.WarningScreen.enabled is true or that your current config uses Config.ScreenType correctly.
• Confirm the player is actually outside the configured AOP area.
• Check F8 and server console for NUI or config errors.

Staff Testing Ignores Enforcement

• If you are owner/admin and AOP enforcement appears to ignore you, staff bypass may be working as configured.
• For testing, set Config.Debug.forceEnforcementForStaff = true if that option exists in your current config.
• Restart Advanced AOP after changing the config.

Boundary Feels Wrong

• Confirm the correct AOP is active.
• Check that the configured coordinates match the intended area.
• Config.Enforcement.hardBorder = true blocks players from crossing from the valid AOP side into the banned/out-of-AOP side.
• If a player spawns already outside AOP and no safe coordinate is known yet, the warning and timer behavior should handle them.
• Test boundaries in-game from multiple roads and entry points.

Map Markers Or Old Blips Look Wrong

• Fully reconnect once if old map blips remain after testing older builds.
• Set Config.MapBlips.enabled = false to hide map markers completely.
• Use Config.MapBlips.showBoundaryDots and Config.MapBlips.showBoundaryMarkers to swap between old red dot/circle style and cleaner boundary marker style.