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

Second cluster doesn't turn into pylon on fiorina #4109

Closed
3 tasks done
ihatethisengine opened this issue Aug 5, 2023 · 6 comments
Closed
3 tasks done

Second cluster doesn't turn into pylon on fiorina #4109

ihatethisengine opened this issue Aug 5, 2023 · 6 comments
Labels
Bug Admin events aren't bugs

Comments

@ihatethisengine
Copy link
Contributor

Testmerges

The following pull requests are currently test merged: #3985: 'Xeno endgame content part 1: pylons and larva' by morrowwolf at commit c3b6e3b #4063: 'Yautja Change Holder' by realforest2001 at commit e88f1b4fdc #4067: 'Research Biohazard Lockdown' by realforest2001 at commit 9020224 #4078: 'Overwatch Console TGUI Refactor' by TheGamerdk at commit 21d9187 #4081: 'Auxiliary Support Officer' by morrowwolf at commit dc00de1 #4055: 'New Healer Drone Ability: Sacrifice' by ihatethisengine at commit 95b1c53 #3942: 'Updates Yautja Plasma Rifle' by Steelpoint at commit 2b02926

Description of the bug

Queen put cluster on second tcomms tower but it didn't turn into pylon despite her even trying to rebuild it on another tile. So xenos didn't get CAS/mortar protection. First cluster turned into pylon as intended. We already had that issue few days ago and morrow had to replace cluster with pylon manually.
2023-08-05_11-05-54

What's the difference with what should have happened?

Cluster should turn into pylon.

How do we reproduce this bug?

  1. Play Fiorina
  2. Wait till 1:35
  3. Put one cluster near first tcomms.
  4. Put second cluster near second tcomms.
  5. It won't turn into pylon.

Issue Bingo

@ihatethisengine ihatethisengine added the Bug Admin events aren't bugs label Aug 5, 2023
@Huffie56
Copy link
Contributor

Huffie56 commented Aug 5, 2023

#3985 link to this PR. pretty sure morrow was there when it happen but always good to keep notes.

@morrowwolf
Copy link
Member

Something strange is happening where the signal isn't attaching to the comms relay for weed growth on init. I can't reproduce it consistently but I am aware of it.

@Drulikar
Copy link
Contributor

Drulikar commented Aug 5, 2023

Something strange is happening where the signal isn't attaching to the comms relay for weed growth on init. I can't reproduce it consistently but I am aware of it.

That signal will only occur if the weeds upgrade (because it deletes the old and places new) or grow there. If you say have a hive core w/ hive weeds, then place pylon, that won't cause the weed growth signal to occur. But could still be something else since I wasn't there for that round.

@ihatethisengine
Copy link
Contributor Author

Hivecore was in engineering. There was no other source of hive weeds. Queen even destroyed the cluster and placed it again, but it didn't help.

@morrowwolf
Copy link
Member

morrowwolf commented Aug 5, 2023

Something strange is happening where the signal isn't attaching to the comms relay for weed growth on init. I can't reproduce it consistently but I am aware of it.

That signal will only occur if the weeds upgrade (because it deletes the old and places new) or grow there. If you say have a hive core w/ hive weeds, then place pylon, that won't cause the weed growth signal to occur. But could still be something else since I wasn't there for that round.

No like the signal is literally not registering when the comms relay is initiated. It's not even setting up to look for weed growth but just sometimes.

@morrowwolf
Copy link
Member

Fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Admin events aren't bugs
Projects
None yet
Development

No branches or pull requests

4 participants