Skip to content

Conversation

@SlayerOrnstein
Copy link
Member

@SlayerOrnstein SlayerOrnstein commented Nov 21, 2025

What did you fix?

Added langs for prime resurgence items, archimedea challenges, calendar challenges, deimos hub node, legacyte mission type and fixed Exilus Adapter description for its Warframe counterpart


Reproduction steps


Evidence/screenshot/link to line

Considerations

  • Does this contain a new dependency? No
  • Does this introduce opinionated data formatting or manual data entry? Yes
  • Does this pr include updated data files in a separate commit that can be reverted for a clean code-only pr? Yes
  • Have I run the linter? Yes
  • Is is a bug fix, feature request, or enhancement? Bug Fix

Summary by CodeRabbit

  • New Features
    • Added Hildryn Prime and Wisp Prime with associated cosmetics, Prime packs, and Mega Prime Vault items
    • Added Prime bobblehead statues for ship display
    • Added T1–T4 Void Fissure relics/projections for Wisp/Hildryn combinations
    • Introduced Legacyte Harvest mission type
    • Added Necralisk (Deimos) relay hub
    • Added calendar labels/entries (e.g., Force Of Attraction and related descriptors)
    • Updated Exilus Adapter display name to "Exilus Warframe Adapter"

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Nov 21, 2025

Walkthrough

Adds numerous localization entries: Hildryn Prime and Wisp Prime store items, void projection relic entries (T1–T4) for Wisp/Hildryn combos, Prime bobbleheads, Mega Prime Vault packs, several calendar/upgrade strings, renames one Exilus entry, plus a new mission type (MT_ENDLESS_CAPTURE) and a new sol node (DeimosHub).

Changes

Cohort / File(s) Summary
Language/localization (bulk)
data/languages.json
Added many public/localization entries: Prime Warframes (/Lotus/StoreItems/Powersuits/... for Hildryn Prime, Wisp Prime), Mega Prime Vault pack keys and single/dual pack names, Prime ship decos (bobbleheads), and multiple new calendar/upgrade descriptors. Also added numerous Void Projection entries (T1–T4) for Wisp/Hildryn combinations with relic descriptors.
Exilus rename
data/languages.json
Updated lotus/types/items/miscitems/utilityunlocker value from "Exilus Adapter" to "Exilus Warframe Adapter".
Mission types
data/missionTypes.json
Added MT_ENDLESS_CAPTURE with value "Legacyte Harvest".
Sol nodes
data/solNodes.json
Added DeimosHub entry: "Necralisk (Deimos)", enemy "Tenno", type "Relay".

Sequence Diagram(s)

(omitted — changes are data/localization additions and do not alter control flow)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Pay extra attention to:
    • Consistency of void projection naming patterns across T1–T4 entries.
    • Correct store item paths and Mega Prime Vault pack keys formatting in data/languages.json.
    • The single Exilus rename to ensure no divergent occurrences elsewhere.

Possibly related PRs

Suggested labels

released

Suggested reviewers

  • TobiTenno

Poem

🐰✨ I hopped through files with nimble paws,
I placed two primes inside the vaults' warm jaws,
Relics, bobbles, calendar bells chime anew,
Deimos gets a hub — a cozy view! 🥕🪄

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title accurately summarizes the main changes: additions of Prime Resurgence data, relics, and event data, which aligns with the changeset modifications to languages.json, missionTypes.json, and solNodes.json.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch langs

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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 and usage tips.

@github-actions
Copy link

github-actions bot commented Nov 21, 2025

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
npm/ansi-regex 6.2.2 🟢 4.5
Details
CheckScoreReason
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Maintained⚠️ 21 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 2
Code-Review🟢 3Found 10/30 approved changesets -- score normalized to 3
Packaging⚠️ -1packaging workflow not detected
Binary-Artifacts🟢 10no binaries found in the repo
Security-Policy🟢 10security policy file detected
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Vulnerabilities🟢 100 existing vulnerabilities detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
npm/ansi-styles 6.2.3 🟢 4.7
Details
CheckScoreReason
Code-Review🟢 4Found 12/30 approved changesets -- score normalized to 4
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Maintained🟢 32 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 3
Security-Policy🟢 10security policy file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Packaging⚠️ -1packaging workflow not detected
Binary-Artifacts🟢 10no binaries found in the repo
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Vulnerabilities🟢 100 existing vulnerabilities detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
npm/chalk 5.6.2 🟢 4.8
Details
CheckScoreReason
Maintained🟢 51 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 5
Security-Policy🟢 10security policy file detected
Packaging⚠️ -1packaging workflow not detected
Binary-Artifacts🟢 10no binaries found in the repo
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Code-Review🟢 3Found 11/30 approved changesets -- score normalized to 3
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Vulnerabilities🟢 100 existing vulnerabilities detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
npm/emoji-regex 10.6.0 🟢 4.4
Details
CheckScoreReason
Code-Review⚠️ 1Found 5/30 approved changesets -- score normalized to 1
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Maintained🟢 57 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Binary-Artifacts🟢 10no binaries found in the repo
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Security-Policy⚠️ 0security policy file not detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Packaging🟢 10packaging workflow detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
Vulnerabilities🟢 100 existing vulnerabilities detected
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
npm/strip-ansi 7.1.2 🟢 4.2
Details
CheckScoreReason
Maintained⚠️ 01 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Security-Policy🟢 10security policy file detected
Binary-Artifacts🟢 10no binaries found in the repo
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Code-Review⚠️ 2Found 6/30 approved changesets -- score normalized to 2
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing⚠️ 0project is not fuzzed
Vulnerabilities🟢 100 existing vulnerabilities detected
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
npm/wrap-ansi 9.0.2 🟢 4.4
Details
CheckScoreReason
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Maintained⚠️ 11 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 1
Packaging⚠️ -1packaging workflow not detected
Code-Review🟢 3Found 10/30 approved changesets -- score normalized to 3
Binary-Artifacts🟢 10no binaries found in the repo
Security-Policy🟢 10security policy file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Vulnerabilities🟢 100 existing vulnerabilities detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
Signed-Releases⚠️ -1no releases found
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
npm/yocto-queue 1.2.2 🟢 4.2
Details
CheckScoreReason
Packaging⚠️ -1packaging workflow not detected
Binary-Artifacts🟢 10no binaries found in the repo
Code-Review⚠️ 1Found 3/17 approved changesets -- score normalized to 1
Maintained⚠️ 12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Vulnerabilities🟢 100 existing vulnerabilities detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0

Scanned Files

  • package-lock.json

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2f404cb and 16ed5f0.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (3)
  • data/languages.json (26 hunks)
  • data/missionTypes.json (1 hunks)
  • data/solNodes.json (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: SlayerOrnstein
Repo: WFCD/warframe-worldstate-data PR: 588
File: data/languages.json:18862-18865
Timestamp: 2024-12-17T20:05:33.832Z
Learning: In `data/languages.json`, upgrade descriptions should remain as provided by Digital Extremes (DE) without modifying formatting inconsistencies.
📚 Learning: 2024-12-17T20:05:33.832Z
Learnt from: SlayerOrnstein
Repo: WFCD/warframe-worldstate-data PR: 588
File: data/languages.json:18862-18865
Timestamp: 2024-12-17T20:05:33.832Z
Learning: In `data/languages.json`, upgrade descriptions should remain as provided by Digital Extremes (DE) without modifying formatting inconsistencies.

Applied to files:

  • data/languages.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Summary
🔇 Additional comments (12)
data/missionTypes.json (1)

76-79: Well-formatted addition that follows existing conventions.

The new MT_ENDLESS_CAPTURE entry for "Legacyte Harvest" is correctly added with proper JSON syntax, consistent naming convention (MT_* prefix), and proper placement in the file structure.

data/solNodes.json (1)

1267-1271: Correctly structured relay hub entry following established patterns.

The new DeimosHub entry for "Necralisk (Deimos)" is properly formatted with consistent naming (*Hub pattern matching ZarimanHub), appropriate metadata ("Tenno" enemy and "Relay" type matching other hubs), and logical placement within the Deimos node cluster. JSON syntax is valid.

data/languages.json (10)

32-43: Prime warframe and void projection entries look good.

The new Hildryn Prime and Wisp Prime warframe entries, along with their associated void projection relic entries (hunks 2-4), follow the established naming and formatting conventions used in the file for other Prime warframes.


161-232: Noggle statue entries are correctly formatted.

The new bobblehead/Noggle statue entries for Hildryn Prime and Wisp Prime follow the same naming pattern and formatting as existing collectible entries.


248-250: Shade Prime Sentinel entry is consistent.

The new Shade Prime Sentinel entry follows the established pattern for sentinel entries in the file.


419-427: Prime Syandana and weapon entries are well-formatted.

The new Prime syandana and weapon entries (Fulmin Prime, Gunsen Prime, Surator Prime Syandana, Entheor Prime Syandana) maintain consistency with existing entries.


501-528: Calendar challenge entries follow expected format.

The new calendar challenge entries ("Starve the beast", "By The Blade") follow the pattern used in existing challenge definitions with consistent value/desc structure.


15436-15437: Exilus Adapter terminology update is sensible.

Updating /lotus/types/items/miscitems/utilityunlocker from "Exilus Adapter" to "Exilus Warframe Adapter" correctly distinguishes this from the new WeaponUtilityUnlocker entry (hunk 12), which is labeled "Exilus Weapon Adapter". This clarification aligns with the PR objective to fix adapter descriptions for their respective counterparts.


617-619: WeaponUtilityUnlocker entry is correctly added.

The new entry for WeaponUtilityUnlocker with value "Exilus Weapon Adapter" correctly distinguishes weapon adapters from warframe adapters, providing appropriate terminology clarity.


647-697: Mega Prime Vault package entries are properly formatted.

The new entries for MPVClearvoyPrimeSuit, MPVHeimtPrimeSentAccessories, MPVHildrynPrimeSinglePack, MPVLarkspurGravimag, MPVWispHildrynPrimeDualPack, and MPVWispPrimeSinglePack all follow the established naming and formatting patterns for Mega Prime Vault packages.


790-793: Calendar upgrade entry is consistently formatted.

The new MagnetStatusPull entry ("Force Of Attraction") follows the established pattern for calendar upgrade definitions with both value and desc fields.


19302-19427: Archimedea challenge modifiers are generally well-structured.

The bulk of new Archimedea challenge modifier entries follow the expected pattern with descriptive names and gameplay mechanics. The formatting and structure are consistent with existing challenge entries, though note the spelling issues flagged separately (throughtout, extra space).

Based on learnings: Per your previous feedback, descriptions should remain as provided by Digital Extremes. All descriptions here appear to be game-authored content and are correctly preserved.

ADHD brain fo brrrr
@SlayerOrnstein SlayerOrnstein enabled auto-merge (squash) November 21, 2025 02:08
@TobiTenno TobiTenno changed the title fix: adds new Warframe Prime Resurgance, relics, and event data fix: new resurgence, relics, and event data Nov 21, 2025
@SlayerOrnstein SlayerOrnstein merged commit a5a5c2b into master Nov 21, 2025
11 checks passed
@SlayerOrnstein SlayerOrnstein deleted the langs branch November 21, 2025 02:57
@wfcd-bot-boi
Copy link
Contributor

🎉 This PR is included in version 3.1.9 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants