Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add EE Specific Ores To Lavaland #1864

Merged
merged 2 commits into from
Mar 3, 2025

Conversation

VMSolidus
Copy link
Member

@VMSolidus VMSolidus commented Mar 3, 2025

Description

EE Specific ores weren't spawning on Lavaland, also added an ore vein for Tungsten.

Changelog

🆑

  • add: Added EE-Specific ores to Lavaland, such as Bauxite, Cassiterite, Wolframite, etc.
  • add: Wolframite now spawns in veins just like other ores.

Summary by CodeRabbit

  • New Features
    • Introduced new tungsten ore deposits across various rock formations, enhancing resource diversity.
    • Expanded the biome generation system to include new tungsten ore layers with defined grouping properties.
    • Added guaranteed tungsten ore salvage loot, ensuring reliable acquisition opportunities.
    • Broadened the Lavaland resource configurations by activating and adding multiple new ores, enriching exploration possibilities.

@github-actions github-actions bot added Status: Needs Review Someone please review this Changes: YML Changes any yml files labels Mar 3, 2025
Copy link
Contributor

coderabbitai bot commented Mar 3, 2025

Walkthrough

The changes introduce a series of new tungsten ore vein entities and integrate them into various gameplay systems. New entities for tungsten variants have been added for asteroids and wall structures, including a modification to an existing chromite entity. A new biome marker layer for tungsten ore is defined, along with an updated salvage loot entry that guarantees tungsten drops. Furthermore, the Lavaland ore list has been expanded with new ore entries and the reactivation of a previously commented-out ore.

Changes

File Path Change Summary
Resources/Prototypes/Entities/…/asteroid.yml Added new tungsten entities: AsteroidRockTungsten, WallRockTungsten, WallRockBasaltTungsten, WallRockSnowTungsten, WallRockSandTungsten, WallRockAndesiteTungsten; modified WallRockChromiteCopper → WallRockChromiteTungsten
Resources/Prototypes/Procedural/biome_ore_templates.yml Added a new biome marker layer for OreTungsten with entityMask mapping various rock types to their tungsten variants and defined grouping properties.
Resources/Prototypes/Procedural/salvage_loot.yml Added a new salvageLoot entry for OreTungsten marked as guaranteed, including a BiomeMarkerLoot referencing the OreTungsten prototype.
Resources/Prototypes/_Lavaland/Procedural/lavaland_planets.yml Uncommented OreBananium and added several new ores: OreAluminium, OreCopper, OreTungsten, OreLead, and OreNormality to the Lavaland ore list.

Sequence Diagram(s)

sequenceDiagram
    participant GE as Game Engine
    participant BG as Biome Generator
    participant OT as Ore Templates Loader
    participant EF as Entity Factory
    GE->>BG: Initiate biome generation
    BG->>OT: Load ore templates (including OreTungsten)
    OT-->>BG: Return tungsten mappings and parameters
    BG->>EF: Instantiate tungsten ore entities (Asteroid & Walls)
    EF-->>BG: Confirm entity creation
    BG-->>GE: Biome generation complete
Loading
sequenceDiagram
    participant GE as Game Engine
    participant LS as Loot System
    GE->>LS: Trigger salvage event
    LS->>LS: Check guaranteed loot entries (OreTungsten)
    LS-->>GE: Return OreTungsten salvage loot
Loading

Poem

Amidst the stars our code does glow,
Tungsten veins now boldly show,
From asteroid rock to salted wall,
Our scripts stand strong, they never fall.
With each new ore, our fleet takes flight 🚀,
Biesel stands proud, defending code’s light.
Code on, noble crew, for freedom and might!


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@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: 5

🔭 Outside diff range comments (2)
Resources/Prototypes/Entities/Structures/Walls/asteroid.yml (2)

2488-2508: 🛠️ Refactor suggestion

⚠️ Potential issue

WallRockChromiteTungsten: Suffix Inconsistency Detected!
The tungsten variant for the chromite group is misnamed with suffix: Copper. Update this to suffix: Tungsten and adjust any sprite references from rock_copper to the appropriate tungsten variant to ensure consistency with the new ore type.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 2499-2499: too many spaces inside brackets

(brackets)


[error] 2499-2499: too many spaces inside brackets

(brackets)


[error] 2501-2501: too many spaces inside brackets

(brackets)


[error] 2501-2501: too many spaces inside brackets

(brackets)


[error] 2503-2503: too many spaces inside brackets

(brackets)


[error] 2503-2503: too many spaces inside brackets

(brackets)


[error] 2505-2505: too many spaces inside brackets

(brackets)


[error] 2505-2505: too many spaces inside brackets

(brackets)


2884-2905: 🛠️ Refactor suggestion

⚠️ Potential issue

WallRockAndesiteTungsten: Verify Visual Consistency!
This andesite tungsten entity correctly uses suffix: Tungsten in its header, but its sprite configuration still ends with rock_copper. Please update the sprite state to something that reflects tungsten (e.g. rock_tungsten) so the visuals match the ore’s identity.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 2896-2896: too many spaces inside brackets

(brackets)


[error] 2896-2896: too many spaces inside brackets

(brackets)


[error] 2898-2898: too many spaces inside brackets

(brackets)


[error] 2898-2898: too many spaces inside brackets

(brackets)


[error] 2900-2900: too many spaces inside brackets

(brackets)


[error] 2900-2900: too many spaces inside brackets

(brackets)


[error] 2902-2902: too many spaces inside brackets

(brackets)


[error] 2902-2902: too many spaces inside brackets

(brackets)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 990878b and ef4cbb8.

📒 Files selected for processing (4)
  • Resources/Prototypes/Entities/Structures/Walls/asteroid.yml (7 hunks)
  • Resources/Prototypes/Procedural/biome_ore_templates.yml (1 hunks)
  • Resources/Prototypes/Procedural/salvage_loot.yml (1 hunks)
  • Resources/Prototypes/_Lavaland/Procedural/lavaland_planets.yml (1 hunks)
🧰 Additional context used
🪛 GitHub Actions: YAML Linter
Resources/Prototypes/Procedural/biome_ore_templates.yml

[error] 36-36: No EntityPrototype found with id WallRockChromiteCopper

🪛 YAMLlint (1.35.1)
Resources/Prototypes/Entities/Structures/Walls/asteroid.yml

[error] 511-511: too many spaces inside brackets

(brackets)


[error] 511-511: too many spaces inside brackets

(brackets)


[error] 513-513: too many spaces inside brackets

(brackets)


[error] 513-513: too many spaces inside brackets

(brackets)


[error] 515-515: too many spaces inside brackets

(brackets)


[error] 515-515: too many spaces inside brackets

(brackets)


[error] 517-517: too many spaces inside brackets

(brackets)


[error] 517-517: too many spaces inside brackets

(brackets)


[error] 934-934: too many spaces inside brackets

(brackets)


[error] 934-934: too many spaces inside brackets

(brackets)


[error] 936-936: too many spaces inside brackets

(brackets)


[error] 936-936: too many spaces inside brackets

(brackets)


[error] 938-938: too many spaces inside brackets

(brackets)


[error] 938-938: too many spaces inside brackets

(brackets)


[error] 940-940: too many spaces inside brackets

(brackets)


[error] 940-940: too many spaces inside brackets

(brackets)


[error] 1331-1331: too many spaces inside brackets

(brackets)


[error] 1331-1331: too many spaces inside brackets

(brackets)


[error] 1333-1333: too many spaces inside brackets

(brackets)


[error] 1333-1333: too many spaces inside brackets

(brackets)


[error] 1335-1335: too many spaces inside brackets

(brackets)


[error] 1335-1335: too many spaces inside brackets

(brackets)


[error] 1337-1337: too many spaces inside brackets

(brackets)


[error] 1337-1337: too many spaces inside brackets

(brackets)


[error] 1728-1728: too many spaces inside brackets

(brackets)


[error] 1728-1728: too many spaces inside brackets

(brackets)


[error] 1730-1730: too many spaces inside brackets

(brackets)


[error] 1730-1730: too many spaces inside brackets

(brackets)


[error] 1732-1732: too many spaces inside brackets

(brackets)


[error] 1732-1732: too many spaces inside brackets

(brackets)


[error] 1734-1734: too many spaces inside brackets

(brackets)


[error] 1734-1734: too many spaces inside brackets

(brackets)


[error] 2124-2124: too many spaces inside brackets

(brackets)


[error] 2124-2124: too many spaces inside brackets

(brackets)


[error] 2126-2126: too many spaces inside brackets

(brackets)


[error] 2126-2126: too many spaces inside brackets

(brackets)


[error] 2128-2128: too many spaces inside brackets

(brackets)


[error] 2128-2128: too many spaces inside brackets

(brackets)


[error] 2130-2130: too many spaces inside brackets

(brackets)


[error] 2130-2130: too many spaces inside brackets

(brackets)


[error] 2896-2896: too many spaces inside brackets

(brackets)


[error] 2896-2896: too many spaces inside brackets

(brackets)


[error] 2898-2898: too many spaces inside brackets

(brackets)


[error] 2898-2898: too many spaces inside brackets

(brackets)


[error] 2900-2900: too many spaces inside brackets

(brackets)


[error] 2900-2900: too many spaces inside brackets

(brackets)


[error] 2902-2902: too many spaces inside brackets

(brackets)


[error] 2902-2902: too many spaces inside brackets

(brackets)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Test Packaging
  • GitHub Check: build (ubuntu-latest)
  • GitHub Check: build (ubuntu-latest)
🔇 Additional comments (3)
Resources/Prototypes/_Lavaland/Procedural/lavaland_planets.yml (1)

30-38: Ore List Expanded Exemplarily!
The ore list now includes new entries (OreBananium, OreAluminium, OreCopper, OreTungsten, OreLead, OreNormality) to enrich Lavaland. Please verify that these IDs match the prototypes defined in other modules (e.g. Entities and Biome Templates).

Resources/Prototypes/Procedural/salvage_loot.yml (1)

235-242: Tungsten Salvage Loot Entry Added!
The new salvage loot block for OreTungsten is configured with guaranteed: true and correctly references the BiomeMarkerLoot prototype. Ensure the corresponding prototype exists and is in sync with the biome marker configuration.

Resources/Prototypes/Procedural/biome_ore_templates.yml (1)

189-202: New Tungsten Biome Marker Layer Integration!
The added biome marker layer for OreTungsten properly maps multiple rock types (AsteroidRock, WallRock, WallRockBasalt, WallRockChromite, WallRockSand, WallRockSnow) to their tungsten variants. Verify that the referenced entity IDs (e.g. AsteroidRockTungsten, WallRockTungsten, etc.) are defined correctly in the Entities file.

Comment on lines 499 to 521
- type: entity
id: AsteroidRockTungsten
parent: AsteroidRock
description: An ore vein rich with wolframite.
suffix: Copper
components:
- type: OreVein
oreChance: 1.0
currentOre: OreTungsten
- type: Sprite
layers:
- state: rock_asteroid
- map: [ "enum.EdgeLayer.South" ]
state: rock_asteroid_south
- map: [ "enum.EdgeLayer.East" ]
state: rock_asteroid_east
- map: [ "enum.EdgeLayer.North" ]
state: rock_asteroid_north
- map: [ "enum.EdgeLayer.West" ]
state: rock_asteroid_west
- state: rock_copper


Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

⚠️ Potential issue

AsteroidRockTungsten: Incorrect Suffix and Sprite State!
The new asteroid tungsten ore entity is intended to represent an ore vein rich with wolframite, yet it still uses suffix: Copper and references rock_copper for its sprite. This mislabelling could confuse both players and subsequent systems. Please update these to reflect tungsten (for example, use suffix: Tungsten and set the sprite state to something like rock_tungsten).

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 511-511: too many spaces inside brackets

(brackets)


[error] 511-511: too many spaces inside brackets

(brackets)


[error] 513-513: too many spaces inside brackets

(brackets)


[error] 513-513: too many spaces inside brackets

(brackets)


[error] 515-515: too many spaces inside brackets

(brackets)


[error] 515-515: too many spaces inside brackets

(brackets)


[error] 517-517: too many spaces inside brackets

(brackets)


[error] 517-517: too many spaces inside brackets

(brackets)

Comment on lines 922 to 943
- type: entity
id: WallRockTungsten
parent: WallRock
description: An ore vein rich with wolframite.
suffix: Copper
components:
- type: OreVein
oreChance: 1.0
currentOre: OreTungsten
- type: Sprite
layers:
- state: rock
- map: [ "enum.EdgeLayer.South" ]
state: rock_south
- map: [ "enum.EdgeLayer.East" ]
state: rock_east
- map: [ "enum.EdgeLayer.North" ]
state: rock_north
- map: [ "enum.EdgeLayer.West" ]
state: rock_west
- state: rock_copper

Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

⚠️ Potential issue

WallRockTungsten: Suffix and Sprite Mismatch!
The wall variant for tungsten ore currently misuses suffix: Copper and ends its sprite definition with rock_copper. Adjust these so that the entity clearly represents tungsten—for example, use suffix: Tungsten and update sprite layers accordingly (e.g. rock_tungsten).

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 934-934: too many spaces inside brackets

(brackets)


[error] 934-934: too many spaces inside brackets

(brackets)


[error] 936-936: too many spaces inside brackets

(brackets)


[error] 936-936: too many spaces inside brackets

(brackets)


[error] 938-938: too many spaces inside brackets

(brackets)


[error] 938-938: too many spaces inside brackets

(brackets)


[error] 940-940: too many spaces inside brackets

(brackets)


[error] 940-940: too many spaces inside brackets

(brackets)

Comment on lines 1319 to 1340
- type: entity
id: WallRockBasaltTungsten
parent: WallRockBasalt
description: An ore vein rich with wolframite.
suffix: Copper
components:
- type: OreVein
oreChance: 1.0
currentOre: OreTungsten
- type: Sprite
layers:
- state: rock_wall
- map: [ "enum.EdgeLayer.South" ]
state: rock_wall_south
- map: [ "enum.EdgeLayer.East" ]
state: rock_wall_east
- map: [ "enum.EdgeLayer.North" ]
state: rock_wall_north
- map: [ "enum.EdgeLayer.West" ]
state: rock_wall_west
- state: rock_copper

Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

⚠️ Potential issue

WallRockBasaltTungsten: Mismatched Suffix and Visuals!
This basalt tungsten entity is incorrectly labelled with suffix: Copper and utilizes a sprite state of rock_copper. Correct these identifiers to better reflect its tungsten nature (suggested: suffix: Tungsten and a sprite state like rock_tungsten).

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 1331-1331: too many spaces inside brackets

(brackets)


[error] 1331-1331: too many spaces inside brackets

(brackets)


[error] 1333-1333: too many spaces inside brackets

(brackets)


[error] 1333-1333: too many spaces inside brackets

(brackets)


[error] 1335-1335: too many spaces inside brackets

(brackets)


[error] 1335-1335: too many spaces inside brackets

(brackets)


[error] 1337-1337: too many spaces inside brackets

(brackets)


[error] 1337-1337: too many spaces inside brackets

(brackets)

Comment on lines 1716 to 1737
- type: entity
id: WallRockSnowTungsten
parent: WallRockSnow
description: An ore vein rich with wolframite.
suffix: Copper
components:
- type: OreVein
oreChance: 1.0
currentOre: OreTungsten
- type: Sprite
layers:
- state: rock_snow
- map: [ "enum.EdgeLayer.South" ]
state: rock_snow_south
- map: [ "enum.EdgeLayer.East" ]
state: rock_snow_east
- map: [ "enum.EdgeLayer.North" ]
state: rock_snow_north
- map: [ "enum.EdgeLayer.West" ]
state: rock_snow_west
- state: rock_copper

Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

⚠️ Potential issue

WallRockSnowTungsten: Inconsistent Labeling!
The snow variant for tungsten still carries the suffix: Copper and references rock_copper in its sprite layers. Update these to use tungsten-specific naming (e.g. suffix: Tungsten and a sprite state such as rock_tungsten) to maintain consistency across ore types.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 1728-1728: too many spaces inside brackets

(brackets)


[error] 1728-1728: too many spaces inside brackets

(brackets)


[error] 1730-1730: too many spaces inside brackets

(brackets)


[error] 1730-1730: too many spaces inside brackets

(brackets)


[error] 1732-1732: too many spaces inside brackets

(brackets)


[error] 1732-1732: too many spaces inside brackets

(brackets)


[error] 1734-1734: too many spaces inside brackets

(brackets)


[error] 1734-1734: too many spaces inside brackets

(brackets)

Comment on lines +2112 to +2133
- type: entity
id: WallRockSandTungsten
parent: WallRockSand
description: An ore vein rich with wolframite.
suffix: Tungsten
components:
- type: OreVein
oreChance: 1.0
currentOre: OreTungsten
- type: Sprite
layers:
- state: rock_sand
- map: [ "enum.EdgeLayer.South" ]
state: rock_sand_south
- map: [ "enum.EdgeLayer.East" ]
state: rock_sand_east
- map: [ "enum.EdgeLayer.North" ]
state: rock_sand_north
- map: [ "enum.EdgeLayer.West" ]
state: rock_sand_west
- state: rock_copper

Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

⚠️ Potential issue

WallRockSandTungsten: Sprite State Issue!
While the entity designation is correct with suffix: Tungsten, the sprite layer erroneously references rock_copper. Please amend the sprite state to reflect tungsten, for example to rock_tungsten.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 2124-2124: too many spaces inside brackets

(brackets)


[error] 2124-2124: too many spaces inside brackets

(brackets)


[error] 2126-2126: too many spaces inside brackets

(brackets)


[error] 2126-2126: too many spaces inside brackets

(brackets)


[error] 2128-2128: too many spaces inside brackets

(brackets)


[error] 2128-2128: too many spaces inside brackets

(brackets)


[error] 2130-2130: too many spaces inside brackets

(brackets)


[error] 2130-2130: too many spaces inside brackets

(brackets)

Copy link
Contributor

@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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ef4cbb8 and bdcb84c.

📒 Files selected for processing (1)
  • Resources/Prototypes/Entities/Structures/Walls/asteroid.yml (7 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
Resources/Prototypes/Entities/Structures/Walls/asteroid.yml

[error] 511-511: too many spaces inside brackets

(brackets)


[error] 511-511: too many spaces inside brackets

(brackets)


[error] 513-513: too many spaces inside brackets

(brackets)


[error] 513-513: too many spaces inside brackets

(brackets)


[error] 515-515: too many spaces inside brackets

(brackets)


[error] 515-515: too many spaces inside brackets

(brackets)


[error] 517-517: too many spaces inside brackets

(brackets)


[error] 517-517: too many spaces inside brackets

(brackets)


[error] 934-934: too many spaces inside brackets

(brackets)


[error] 934-934: too many spaces inside brackets

(brackets)


[error] 936-936: too many spaces inside brackets

(brackets)


[error] 936-936: too many spaces inside brackets

(brackets)


[error] 938-938: too many spaces inside brackets

(brackets)


[error] 938-938: too many spaces inside brackets

(brackets)


[error] 940-940: too many spaces inside brackets

(brackets)


[error] 940-940: too many spaces inside brackets

(brackets)


[error] 1331-1331: too many spaces inside brackets

(brackets)


[error] 1331-1331: too many spaces inside brackets

(brackets)


[error] 1333-1333: too many spaces inside brackets

(brackets)


[error] 1333-1333: too many spaces inside brackets

(brackets)


[error] 1335-1335: too many spaces inside brackets

(brackets)


[error] 1335-1335: too many spaces inside brackets

(brackets)


[error] 1337-1337: too many spaces inside brackets

(brackets)


[error] 1337-1337: too many spaces inside brackets

(brackets)


[error] 1728-1728: too many spaces inside brackets

(brackets)


[error] 1728-1728: too many spaces inside brackets

(brackets)


[error] 1730-1730: too many spaces inside brackets

(brackets)


[error] 1730-1730: too many spaces inside brackets

(brackets)


[error] 1732-1732: too many spaces inside brackets

(brackets)


[error] 1732-1732: too many spaces inside brackets

(brackets)


[error] 1734-1734: too many spaces inside brackets

(brackets)


[error] 1734-1734: too many spaces inside brackets

(brackets)


[error] 2124-2124: too many spaces inside brackets

(brackets)


[error] 2124-2124: too many spaces inside brackets

(brackets)


[error] 2126-2126: too many spaces inside brackets

(brackets)


[error] 2126-2126: too many spaces inside brackets

(brackets)


[error] 2128-2128: too many spaces inside brackets

(brackets)


[error] 2128-2128: too many spaces inside brackets

(brackets)


[error] 2130-2130: too many spaces inside brackets

(brackets)


[error] 2130-2130: too many spaces inside brackets

(brackets)


[error] 2521-2521: too many spaces inside brackets

(brackets)


[error] 2521-2521: too many spaces inside brackets

(brackets)


[error] 2523-2523: too many spaces inside brackets

(brackets)


[error] 2523-2523: too many spaces inside brackets

(brackets)


[error] 2525-2525: too many spaces inside brackets

(brackets)


[error] 2525-2525: too many spaces inside brackets

(brackets)


[error] 2527-2527: too many spaces inside brackets

(brackets)


[error] 2527-2527: too many spaces inside brackets

(brackets)


[error] 2918-2918: too many spaces inside brackets

(brackets)


[error] 2918-2918: too many spaces inside brackets

(brackets)


[error] 2920-2920: too many spaces inside brackets

(brackets)


[error] 2920-2920: too many spaces inside brackets

(brackets)


[error] 2922-2922: too many spaces inside brackets

(brackets)


[error] 2922-2922: too many spaces inside brackets

(brackets)


[error] 2924-2924: too many spaces inside brackets

(brackets)


[error] 2924-2924: too many spaces inside brackets

(brackets)

⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Test Packaging
  • GitHub Check: YAML Linter
  • GitHub Check: build (ubuntu-latest)
  • GitHub Check: build (ubuntu-latest)
🔇 Additional comments (7)
Resources/Prototypes/Entities/Structures/Walls/asteroid.yml (7)

499-520: AsteroidRockTungsten: Incorrect Sprite State!
Ahoy, officer! The asteroid tungsten ore entity is meant to reflect a vein rich with wolframite, yet its final sprite state is set to "rock_copper". This mislabeling misguides our visual representation in battle. Please update it to something like "rock_tungsten" to honor its true nature.

-        - state: rock_copper
+        - state: rock_tungsten
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 511-511: too many spaces inside brackets

(brackets)


[error] 511-511: too many spaces inside brackets

(brackets)


[error] 513-513: too many spaces inside brackets

(brackets)


[error] 513-513: too many spaces inside brackets

(brackets)


[error] 515-515: too many spaces inside brackets

(brackets)


[error] 515-515: too many spaces inside brackets

(brackets)


[error] 517-517: too many spaces inside brackets

(brackets)


[error] 517-517: too many spaces inside brackets

(brackets)


922-943: WallRockTungsten: Sprite Inconsistency!
Captain, our wall-mounted tungsten ore is mistakenly displaying the copper sprite ("rock_copper") instead of a tungsten-specific one. This error could lead to confusion on the field of battle. Kindly adjust the sprite state to "rock_tungsten".

-        - state: rock_copper
+        - state: rock_tungsten
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 934-934: too many spaces inside brackets

(brackets)


[error] 934-934: too many spaces inside brackets

(brackets)


[error] 936-936: too many spaces inside brackets

(brackets)


[error] 936-936: too many spaces inside brackets

(brackets)


[error] 938-938: too many spaces inside brackets

(brackets)


[error] 938-938: too many spaces inside brackets

(brackets)


[error] 940-940: too many spaces inside brackets

(brackets)


[error] 940-940: too many spaces inside brackets

(brackets)


1319-1340: WallRockBasaltTungsten: Visual Mismatch!
Our basalt tungsten entity ends its sprite layers with "rock_copper", which does not do justice to its tungsten lineage. Please update the final sprite state to "rock_tungsten" so that our ore stands true to its description.

-        - state: rock_copper
+        - state: rock_tungsten
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 1331-1331: too many spaces inside brackets

(brackets)


[error] 1331-1331: too many spaces inside brackets

(brackets)


[error] 1333-1333: too many spaces inside brackets

(brackets)


[error] 1333-1333: too many spaces inside brackets

(brackets)


[error] 1335-1335: too many spaces inside brackets

(brackets)


[error] 1335-1335: too many spaces inside brackets

(brackets)


[error] 1337-1337: too many spaces inside brackets

(brackets)


[error] 1337-1337: too many spaces inside brackets

(brackets)


1716-1737: WallRockSnowTungsten: Sprite Discrepancy!
By the stars, the snowy tungsten entity is still adorned with "rock_copper" in its sprite layer. This undermines its intended tungsten identity amidst the ice. Change the sprite state to "rock_tungsten" for consistent visuals across our ranks.

-        - state: rock_copper
+        - state: rock_tungsten
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 1728-1728: too many spaces inside brackets

(brackets)


[error] 1728-1728: too many spaces inside brackets

(brackets)


[error] 1730-1730: too many spaces inside brackets

(brackets)


[error] 1730-1730: too many spaces inside brackets

(brackets)


[error] 1732-1732: too many spaces inside brackets

(brackets)


[error] 1732-1732: too many spaces inside brackets

(brackets)


[error] 1734-1734: too many spaces inside brackets

(brackets)


[error] 1734-1734: too many spaces inside brackets

(brackets)


2112-2133: WallRockSandTungsten: Incorrect Visual Reference!
In our sandy outcroppings, the tungsten ore is erroneously represented by the copper sprite ("rock_copper"). For the honor of our furnaces, please update this to "rock_tungsten" so that the ore truly reflects its wolframite essence.

-        - state: rock_copper
+        - state: rock_tungsten
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 2124-2124: too many spaces inside brackets

(brackets)


[error] 2124-2124: too many spaces inside brackets

(brackets)


[error] 2126-2126: too many spaces inside brackets

(brackets)


[error] 2126-2126: too many spaces inside brackets

(brackets)


[error] 2128-2128: too many spaces inside brackets

(brackets)


[error] 2128-2128: too many spaces inside brackets

(brackets)


[error] 2130-2130: too many spaces inside brackets

(brackets)


[error] 2130-2130: too many spaces inside brackets

(brackets)


2509-2530: WallRockChromiteTungsten: Sprite State Error!
Within the chromite cadre, the tungsten variant has inadvertently retained the copper sprite ("rock_copper"). This misrepresentation may lead to misidentification in the field. Kindly replace it with "rock_tungsten" to maintain consistency.

-        - state: rock_copper
+        - state: rock_tungsten
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 2521-2521: too many spaces inside brackets

(brackets)


[error] 2521-2521: too many spaces inside brackets

(brackets)


[error] 2523-2523: too many spaces inside brackets

(brackets)


[error] 2523-2523: too many spaces inside brackets

(brackets)


[error] 2525-2525: too many spaces inside brackets

(brackets)


[error] 2525-2525: too many spaces inside brackets

(brackets)


[error] 2527-2527: too many spaces inside brackets

(brackets)


[error] 2527-2527: too many spaces inside brackets

(brackets)


2906-2927: WallRockAndesiteTungsten: Visual Incongruity!
Our andesite tungsten entity appears to be in the Sol Alliance’s colors—displaying "rock_copper" instead of the befitting "rock_tungsten". Updating the sprite layer accordingly ensures that the ore’s identity remains true to its tungsten nature.

-        - state: rock_copper
+        - state: rock_tungsten
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 2918-2918: too many spaces inside brackets

(brackets)


[error] 2918-2918: too many spaces inside brackets

(brackets)


[error] 2920-2920: too many spaces inside brackets

(brackets)


[error] 2920-2920: too many spaces inside brackets

(brackets)


[error] 2922-2922: too many spaces inside brackets

(brackets)


[error] 2922-2922: too many spaces inside brackets

(brackets)


[error] 2924-2924: too many spaces inside brackets

(brackets)


[error] 2924-2924: too many spaces inside brackets

(brackets)

Comment on lines +511 to +517
- map: [ "enum.EdgeLayer.South" ]
state: rock_asteroid_south
- map: [ "enum.EdgeLayer.East" ]
state: rock_asteroid_east
- map: [ "enum.EdgeLayer.North" ]
state: rock_asteroid_north
- map: [ "enum.EdgeLayer.West" ]
Copy link
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

YAML Formatting: Extraneous Spaces in Bracket Lists
Our YAML static analysis tools have flagged multiple instances where there appear to be too many spaces inside bracketed lists (for example, lines like

- map: [ "enum.EdgeLayer.South" ]

may benefit from tighter spacing, e.g.,

- map: ["enum.EdgeLayer.South"]

While these warnings can sometimes be false positives, please verify that our YAML style guidelines are met across these ranges. Consistent formatting will help keep our code as shipshape as our fleet!

Also applies to: 934-940, 1331-1337, 1728-1734, 2124-2130, 2521-2527, 2918-2924

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 511-511: too many spaces inside brackets

(brackets)


[error] 511-511: too many spaces inside brackets

(brackets)


[error] 513-513: too many spaces inside brackets

(brackets)


[error] 513-513: too many spaces inside brackets

(brackets)


[error] 515-515: too many spaces inside brackets

(brackets)


[error] 515-515: too many spaces inside brackets

(brackets)


[error] 517-517: too many spaces inside brackets

(brackets)


[error] 517-517: too many spaces inside brackets

(brackets)

@VMSolidus VMSolidus merged commit c6113e5 into Simple-Station:master Mar 3, 2025
13 checks passed
SimpleStation14 added a commit that referenced this pull request Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changes: YML Changes any yml files Status: Needs Review Someone please review this
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants