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

Creating a base node for an upgraded building does not create a node for the upgrade #184

Open
Crimsonum opened this issue Jul 12, 2024 · 2 comments

Comments

@Crimsonum
Copy link
Contributor

Buildings with upgrades require two nodes on the same cell: one for the parent building, and one for the upgrade. WAE currently has the same limitation as FinalSun/Alert where creating a node from an upgraded building only places a node for the parent building, not the upgrade.

@Rampastring
Copy link
Member

It is debatable what behaviour is desirable here.

@krnyoshi
Copy link

krnyoshi commented Feb 20, 2025

Could the behavior be:

  1. Mapper places structure down with an upgrade (or two)
  2. Mapper creates a base node
  3. WAE checks if the building has an upgrade before creating a base node
  4. If the building has an upgrade (or two) it will add the base node PLUS the upgrade(s) on the same cell.
  5. When the base node is deleted, it will remove the base structure + its upgrades.
  • Example:
    GAPOWR w/ 2 GAPOWRUP upgrades placed on map and are selected to be a base node
    WAE checks if the structure has upgrades. Confirms that it has 2 upgrades.
    WAE writes:
    000=GAPOWR,123,456
    001=GAPOWRUP,123,456 (same x,y pos as the base structure)
    002=GAPOWRUP,123,456 (same x,y pos as the base structure)
    When the base node is removed, WAE checks if there's a base node in the same position of the structure. If so, removes the structure + upgrades.

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

No branches or pull requests

3 participants