LaserFence Issue

Bug #896353 reported by cranium
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
Triaged
Wishlist
Unassigned

Bug Description

When creating Laser Fences for multiple sides/Countries, the game will only use one LaserFence=yes structure regardless if you have a seperate LaserFence=yes section for each LaserPost. And it seems to be the first listed structure that has LaserFence=yes. For Instance, in my mod I have VFNCE, RFFNCE, and GAFNCE. All three show the correct posts but all 3 will only use the VFNCE section. It is the first listed structure with LaserFence=yes. If I comment out VFNCE, it will use the next one in list.
Is there a way to break this, so that all countries with their own laser fences will use their own fence sections?

##### STEPS TO REPRODUCE #####
give each side their own laser fences, build them and it will only use one specific LaserFence=yes section

Revision history for this message
DCoder DCoder (dcoder1337) wrote :

That's not possible without us fixing the code.

Revision history for this message
YR M0ddEr (yr-m0dder) wrote :

instead of having each side hardcoded to use one laser fence, the building with LaserFence=yes could have a tag like ConnectedTo=LASERPOST.

Supporting this.

Revision history for this message
MRMIdAS (mrmidas) wrote :

odd question, but does Owner= make any difference?

if not making the game respect Owner= on laser fences would seem like the best bet.

Revision history for this message
cranium (cranium) wrote :

Another bug with this is , Well it's not a bug, but it is cause it bugs me :) "sorry for the lame humor"

When you build 3 or more posts in the same line of cells. When the middle post is destroyed it of course blows up the fence sections as well. But I think the 2 or more remaining posts should redraw the sections if they meet the Range= requirements.

Revision history for this message
Krozalid (krozalid) wrote :

I agree with Cranium.

Changed in ares:
importance: Medium → Wishlist
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.