Add new translations for block entity culling

[Texaliuz]

No description provided.

[coderabbitai]

Walkthrough

Adds three Spanish (Argentina) localization entries for EntityCulling: a category title key and block-entity frustum culling label plus tooltip, appended to es_ar.json without changing other translations.

Changes

Cohort / File(s)	Summary
Spanish (Argentina) Localization src/main/resources/assets/entityculling/lang/es_ar.json	Adds three translation keys: key.category.minecraft.text.entityculling.title, text.entityculling.blockEntityFrustumCulling, and text.entityculling.blockEntityFrustumCulling.tooltip; minor trailing-comma formatting adjusted

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single JSON file change; purely additive key/value entries with consistent structure.

Possibly related PRs

• Update pt_br.json #245 — Adds identical localization keys to another locale file for the same EntityCulling UI strings.
• Update uk_ua.json #254 — Introduces the same translation keys across additional language files.
• Add Traditional Chinese translation #244 — Parallel localization update adding the same keys (category and block-entity frustum culling strings) to other locales.

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided by the author, making it impossible to assess relevance to the changeset.	Add a description explaining the purpose of the translation additions and any context about the block entity culling feature.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding new Spanish-Argentine translations for block entity frustum culling functionality.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between aa164e9 and e38663e.

📒 Files selected for processing (1)

• src/main/resources/assets/entityculling/lang/es_ar.json (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/main/resources/assets/entityculling/lang/es_ar.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: build

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 39edc37 and aa164e9.

📒 Files selected for processing (1)

• src/main/resources/assets/entityculling/lang/es_ar.json (2 hunks)

🧰 Additional context used

🪛 Biome (2.1.2)

src/main/resources/assets/entityculling/lang/es_ar.json

[error] 23-23: expected , but instead found "text.entityculling.blockEntityFrustumCulling"

Remove "text.entityculling.blockEntityFrustumCulling"

(parse)

⏰ 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: build

🔇 Additional comments (1)

src/main/resources/assets/entityculling/lang/es_ar.json (1)

1-25: Verify translation consistency and completeness.

While the new translations appear well-formed Spanish (Argentina) localization, please verify:

1. That the key names match their counterparts in other language files (e.g., en_us.json)
2. That the new keys (blockEntityFrustumCulling and related category title) are actually used elsewhere in the codebase

Run the following script to verify that the new translation keys are referenced in the codebase:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Texaliuz]

Sorry, I was missing one comma.