balance: several content entries missing combatPowerRequired field #107

Closed
opened 2026-03-23 15:41:46 -07:00 by hikari · 0 comments
Owner

Issue

Some content entries (zones, quests, or exploration areas) are missing the combatPowerRequired field entirely. This means they either have no gating (unintentionally open) or fall back to a default value of 0, which may not be the intended design.

Expected Behaviour

All content that is meant to be gated by combat power should have an explicit combatPowerRequired value set.

Steps to Reproduce

  1. Audit the data files in apps/api/src/data/
  2. Find entries where combatPowerRequired is absent or 0 unexpectedly

Suggested Fix

Add explicit combatPowerRequired values to all affected entries, set to values that fit their position in the progression curve.

Priority

🟢 Low — may allow unintended early access to content, but not game-breaking

This issue was created with help from Hikari~ 🌸

## Issue Some content entries (zones, quests, or exploration areas) are missing the `combatPowerRequired` field entirely. This means they either have no gating (unintentionally open) or fall back to a default value of `0`, which may not be the intended design. ## Expected Behaviour All content that is meant to be gated by combat power should have an explicit `combatPowerRequired` value set. ## Steps to Reproduce 1. Audit the data files in `apps/api/src/data/` 2. Find entries where `combatPowerRequired` is absent or `0` unexpectedly ## Suggested Fix Add explicit `combatPowerRequired` values to all affected entries, set to values that fit their position in the progression curve. ## Priority 🟢 Low — may allow unintended early access to content, but not game-breaking ✨ This issue was created with help from Hikari~ 🌸
naomi closed this issue 2026-03-23 17:28:30 -07:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/elysium#107