Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nudj.cx/llms.txt

Use this file to discover all available pages before exploring further.

🔵 Release v2.361.4

⭐ Simple • 1 commit • 3 files
Reward Allocation Validation Fix: Resolves an issue where admins couldn’t save shared-supply rewards with individual allocations set to unlimited supply. The validation logic now correctly allows this configuration, which is valid when the total reward supply is finite.

What’s New

  • Shared-Supply Reward Configuration: Fixed validation that was incorrectly blocking valid reward configurations where individual allocations have unlimited supply but the total reward pool is finite
  • Improved Reward Flexibility: Admins can now fully leverage shared supply mode to set up rewards where per-allocation caps are managed at the reward level rather than per allocation
  • Enhanced Configuration Workflow: Eliminates validation errors when configuring advanced reward allocation strategies

Apps Updated

User App

— No changes

API

✓ Updated - 1 change

Admin

— No changes

MCP Server

— No changes

Games

— No changes

Detailed Changes

Reward Allocation Validation (apps/api/trpc/routers/admin/rewards/)
  • Fixed validation logic that was incorrectly rejecting shared-supply rewards with unlimited-supply allocations
  • When a reward uses shared supply (finite total pool), individual allocations can now safely have unlimited supply — the shared total acts as the cap
  • Added comprehensive test coverage for shared asset and entry allocations with finite totals
  • Resolves NUDJ-5731: prevents validation errors when updating unrelated reward fields on valid shared-supply configurations

Technical Details

The reward allocation validation system needed refinement for shared-supply scenarios: Before: The system rejected any allocation with unlimited (Infinity) supply if the reward’s total supply was finite, regardless of whether the supply was shared or per-allocation. After: The validation now correctly distinguishes:
  • Per-allocation supply (not shared): Rejects unlimited allocation supply with finite total ✓ (contradictory)
  • Shared supply (finite total): Allows unlimited allocation supply ✓ (finite total is the real cap)
This fix enables advanced reward configurations where the shared pool is the constraint, and individual allocations can draw from it without per-allocation limits.

Contributors

jamescockayne@jamescockayne1 commit • +73/-10 lines

Release Stats

MetricValue
Total Commits1
Lines Added+73
Lines Removed-10
Files Changed3

v2.361.4 deployed on May 29, 2026