Skip to content

fix: correct the family experience table and extend it to level 30 - #130

Merged
erwan-joly merged 1 commit into
masterfrom
fix/family-experience-table
Aug 23, 2026
Merged

fix: correct the family experience table and extend it to level 30#130
erwan-joly merged 1 commit into
masterfrom
fix/family-experience-table

Conversation

@erwan-joly

Copy link
Copy Markdown
Contributor

The table merged in #129 was wrong in every row, and short.

Level was is
1 100 000 80 000
7 1 900 000 512 000
15 7 000 000 5 000 000
19 17 000 000 20 000 000
20–30 missing 22 000 000 → 57 062 334

Two separate faults: the numbers, and the ceiling. A family reaching 19 on the old table would have hit uint.MaxValue and been unable to level at all, because the game goes to 30.

The <remarks> in #129 already flagged the level 7 row as suspect off a single ginfo observation. It was right to doubt it — the whole curve was off.

From level 20 the requirement is the previous one plus a tenth, compounded on the unrounded value and floored — 20 000 000 × 1.1ⁿ reproduces rows 20–30 exactly, including the non-round tail (47 158 953, 51 874 849). That the derived formula lands on every published row is decent evidence the numbers are self-consistent rather than transcribed noise.

Also adds Constants.MaxFamilyLevel = 30 alongside the other level ceilings, and extends the approval table to cover the full range.

Version bumped to 2.1.0. 22/22 tests pass.

🤖 Generated with Claude Code

Every row was wrong. Level 1 asked 100 000 against 80 000, level 7 asked
1 900 000 against 512 000, and the curve stopped at 19 where the game goes to
30. A family would have needed roughly triple the experience it should at the
top of the old table and then been unable to level at all.

From level 20 the requirement is the previous one plus a tenth, compounded
unrounded and floored, which is why those rows are not round.

Version bumped to 2.1.0.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@erwan-joly, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 25 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: f44aaa50-fb07-44e8-80e0-c20128d63ee6

📥 Commits

Reviewing files that changed from the base of the PR and between 1cce607 and 9d9a677.

📒 Files selected for processing (5)
  • documentation/DocumentationTest.FamilyExperienceDocumentation.approved.md
  • src/NosCore.Algorithm/Constants.cs
  • src/NosCore.Algorithm/FamilyExperienceService/FamilyExperienceService.cs
  • src/NosCore.Algorithm/NosCore.Algorithm.csproj
  • test/NosCore.Algorithm.Tests/DocumentationTest.cs

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@erwan-joly
erwan-joly merged commit a7439cd into master Aug 23, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant