Page 1 of 1
[2.0.55] Medium Fulgoran ruin icon displayed wrong
Posted: Tue Jun 24, 2025 9:36 pm
by fi5hii
When adding the different Fulgoran ruins to the deconstruction planner (to not remove lightning attractors) I noticed that the icons for the lightning attractor and medium ruins are the same. The icon for the medium ruin doesn't represent any of the medium ruins that are in the game.
Would be nice to get one of the actual medium ruins as the icon, personally I would prefer the bottom row 4th one but any of them will be just fine.
The lightning attractor icon:

- Screenshot 2025-06-24 at 23.26.40.png (344.62 KiB) Viewed 348 times
The medium Fulgoran ruin icon:

- Screenshot 2025-06-24 at 23.26.27.png (272.17 KiB) Viewed 348 times
All the different medium ruin graphics:

- Screenshot 2025-06-24 at 23.27.41.png (506.58 KiB) Viewed 348 times
Re: [2.0.55] Medium Fulgoran ruin icon displayed wrong
Posted: Wed Jun 25, 2025 1:15 am
by Rseding91
Thanks for the report. It looks like the entity icon and entity graphics are simply different, but it is showing the correct icon set for the ruin entity.
Given the huge difference in ruin variations I don’t see a single one that would fit perfectly in the icon.
Re: [2.0.55] Medium Fulgoran ruin icon displayed wrong
Posted: Wed Jun 25, 2025 8:56 am
by fi5hii
Rseding91 wrote: Wed Jun 25, 2025 1:15 am
Thanks for the report. It looks like the entity icon and entity graphics are simply different, but it is showing the correct icon set for the ruin entity.
Given the huge difference in ruin variations I don’t see a single one that would fit perfectly in the icon.
I should have specified a bit more the entity set displayed is when clicking on the editor to show the collection of all medium ruins. the lightning attractor icon on the deconstruction planner looks exactly like it does in game so I was a bit confused when the ruins had the same icon and not one of the entities.
Thank you for your time

Re: [2.0.55] Medium Fulgoran ruin icon displayed wrong
Posted: Tue Jul 08, 2025 5:39 pm
by Bilka
This is fixed for the next version.