Jump to content

[From YotC event] Fence Gates Are Bugged When Placed Next to Walls in the NW & SE Orientation


lakhnish
  • Fixed

This bug was introduced during the Year of the Carrot.

Place down two walls with a two space gap in the NW & SE orientation (hold a compass and let the red arrow point in the mentioned cardinal directions).

^ Make four sets of these (lets call them sets A through D).

For set A, place the fence gates in between the walls while facing the NW orientation at the front line of the stone walls. Its works fine, like here.

Spoiler

20200322173441_1.thumb.jpg.47d7cebf16d904266a8786046e5f7400.jpg

 

For set B, face the NW orientation, but place the fence gates in the back line of the stone walls. It's placed super weird and has a big gap to it between the walls.

Spoiler

20200322173451_1.thumb.jpg.cd3c7e68fce6f147d203616c90447e16.jpg20200322173458_1.thumb.jpg.3474101ce1ebb4a636be5fc0164eda10.jpg

 

For set C, place the fence gates in between the walls while facing the SE orientation at the front line of the stone walls. It's placed super weird and has a big gap to it between the walls.

Spoiler

20200322173535_1.thumb.jpg.7f31606f5417f19b97a446658457b585.jpg20200322173536_1.thumb.jpg.8b94ccc4b23ba1022471adfbd1b8da27.jpg

 

For set D, face the SE orientation, but place the fence gates in the back line of the stone walls. The fence gates face the NW orientation instead.

Spoiler

20200322173544_1.thumb.jpg.3b2a4dd2192986e12bde64179601968f.jpg

 

This only occurs if the walls are placed before the fence gates, which was not the case before the Year of the Carrot update. The fence gates also do not face this issue in other other cardinal directions. 
I can produce a clip of this behavior if requested.


Steps to Reproduce
Try facing fence gates in the NW/SE orientation, so that fence gate is placed in the "front line" or "back line" in between the walls. Notice the bugged orientation.
  • Like 3



User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.

Changed Status to Fixed

Thanks for the patience and effort documenting the bugs on this one. It ended up being 3 different issues all conflated on each other, so it took some time to track down. I think I've got it fixed up now, but after the next update if you see anything weird still, please let me know.

  • Thanks 2

Share this comment


Link to comment
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...