Skip to content

Examples and troubleshooting

Change only the options you need. Everything else keeps its default.

Short rounds and a generous wait for an opponent.

Config.Debug = false
Config.FightSettings = {
MaxOponentSearchTime = 30,
Player1StartingLocation = vector4(-1242.5548, -1594.8619, 4.3083, 169.3889),
Player2StartingLocation = vector4(-1243.3414, -1599.8231, 4.3083, 349.2167),
TotalRounds = 1,
ProlongationRounds = 2,
RoundDuration = 1,
OutSideZoneTimer = 10,
}

One knockout wins the match. If the timer runs out with no knockout, nobody scores the round, so the extra rounds act as the tiebreaker.

Best of three with a draw breaker.

Config.FightSettings = {
MaxOponentSearchTime = 20,
Player1StartingLocation = vector4(-1242.5548, -1594.8619, 4.3083, 169.3889),
Player2StartingLocation = vector4(-1243.3414, -1599.8231, 4.3083, 349.2167),
TotalRounds = 3,
ProlongationRounds = 2,
RoundDuration = 3,
OutSideZoneTimer = 8,
}

A fighter needs at least 2 round wins and more wins than the opponent after round 3. Otherwise up to 2 extra rounds are played.

Use debug mode to check the ring, the corners and the scoreboard with one player.

Config.Debug = true

Sign up at the bouncer. A match against an AI boxer starts at once. Do not leave debug mode on for players.

Config.Settings = {
NpcModel = `s_m_m_bouncer_01`,
NpcCoords = vector4(100.0, 200.0, 30.0, 90.0),
BoxingArenaCoords = {
vector2(110.0, 210.0),
vector2(116.0, 210.0),
vector2(116.0, 216.0),
vector2(110.0, 216.0),
},
ArenaMinZ = 28.0,
ArenaMaxZ = 36.0,
BoxingSpectate = {
vector2(104.0, 204.0),
vector2(122.0, 204.0),
vector2(122.0, 222.0),
vector2(104.0, 222.0),
},
SpectateMinZ = 28.0,
SpectateMaxZ = 38.0,
}

These numbers are made up to show the shape. Use your own. The fighter corners in Config.FightSettings must also be inside the new ring. See Ring and zone setup.

Situation Result Fix
None of es_extended, qb-core, qbx_core is running Bouncer appears, no interaction option. Zones load. Start your framework before kivo-boxing.
Framework resource is renamed Not detected, same as above. The script only looks for the standard resource names listed above.
Framework starts after kivo-boxing Not detected, same as above. Fix the order in server.cfg, or restart kivo-boxing after the framework.
Framework is restarted while the server runs The framework is only checked when kivo-boxing starts. Restart kivo-boxing as well.
Missing Result Fix
PolyZone kivo-boxing does not start, the console reports a dependency problem. Install PolyZone and name its folder PolyZone.
ox_target and qb-target Bouncer appears but cannot be used. A red message is printed in the F8 console. Install and start one of them before kivo-boxing.
ox_lib Nothing breaks. Notifications appear as chat messages. Optional. Start ox_lib for notification popups.
  • A ring area that does not cover the fighter corners: the forfeit countdown may not work as expected. Put both corners inside the polygon.
  • Wrong Z range: the zone never triggers. Make sure the floor height fits between the Min and Max values.
  • Points in the wrong order: the polygon folds over itself and parts of the ring count as outside. List points around the edge.
  • Spectator area too small: players near the ring do not see the scoreboard. Enlarge it.
  • Check the F8 console for errors from kivo-boxing.
  • Check that NpcModel is a valid ped model. A wrong name stops the client setup, so the bouncer and the zones both fail to load.
  • Check the coordinates. Fly to NpcCoords and look around.

The bouncer appears but there is no sign-up option

Section titled “The bouncer appears but there is no sign-up option”
  • Run ensure for your framework and target resource, then restart kivo-boxing.
  • Check that you run ox_target or qb-target. Turn Config.Debug on and read the F8 lines that start with [kivo-boxing]. They say which framework was detected and whether a target was found.

The script places him 1.0 unit below the Z you set. Copy the coordinates while you stand on the ground where he should be.

Config.Debug is true. Set it to false and restart the script.

  • Both players must sign up within MaxOponentSearchTime seconds of each other. Raise the value.
  • If a match is running, new sign-ups get an “Arena Busy” message.
  • With Config.Debug = false, a single player waits and is cancelled when the time runs out. That is expected.

Check Player1StartingLocation and Player2StartingLocation. They must be inside your ring.

Fighters can leave the ring and nothing happens

Section titled “Fighters can leave the ring and nothing happens”

Their starting corner is outside the ring polygon, or the Z range is wrong. See Ring and zone setup.

The scoreboard does not show for spectators

Section titled “The scoreboard does not show for spectators”
  • The spectator must stand inside BoxingSpectate and between SpectateMinZ and SpectateMaxZ.
  • The scoreboard shows only while a match is running.
  • Turn on Config.Debug to see the zone outlines.

No round bell or knockout sound at a moved ring

Section titled “No round bell or knockout sound at a moved ring”

These two sounds only play close to the default ring location. See Sounds.

Notifications appear in chat instead of popups

Section titled “Notifications appear in chat instead of popups”

ox_lib is not running. Start it to use ox_lib notifications.

Restart the script with restart kivo-boxing. The config is read when the script starts.

  • Config.Debug = false
  • PolyZone, framework and target resource start before kivo-boxing
  • Tested with two players: sign-up, 2 rounds, win and loss
  • Tested a forfeit by walking out of the ring
  • Spectator area shows the scoreboard
  • Bouncer stands on the ground and faces the right way