[BDS-18570] Wrong coordinates when running execute positioned in the console Created: 21/Jul/23  Updated: 25/Aug/23

Status: Reopened
Project: Bedrock Dedicated Server
Affects Version/s: 1.20.12 Hotfix
Fix Version/s: None

Type: Bug
Reporter: nether4526 Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Environment:

MINECRAFT DEDICATED SERVER SOFTWARE FOR WINDOWS PREVIEW


Attachments: PNG File image-2023-07-21-21-26-08-086.png     PNG File image-2023-07-25-23-37-41-108.png     PNG File image-2023-07-25-23-39-39-874.png     PNG File image-2023-07-25-23-41-35-429.png    
Confirmation Status: Confirmed
ADO: 1096014

 Description   

Steps to Reproduce:
1. Create a minecraft dedicated server software for windows preview, version 1.20.20.22.
2. Create a world with the following seed: -3292942500904204490
3. Start the server
4. Enter following command in the console: execute positioned -1797 100 105 in nether run locate structure fortress

Observed Results:
Console reports me: [2023-07-21 21:25:03:050 INFO] The nearest Nether Fortress is at block 384, (y?), -432 (754 blocks away) 
It looks like it is ignoring the passed position (that is -1797 100 105). 

Expected Results:
I'd expect to see: [2023-07-21 21:25:03:050 INFO] The nearest Nether Fortress is at block -1824, (y?), -167 (282 blocks away)

---
World seed:

Running command in-game + being in the nether (expected result when running the mentioned command):



 Comments   
Comment by nether4526 [ 25/Jul/23 ]

Hi @mapior, thanks, I updated the description of my bug. Btw, the link you provided (https://help.mojang.com/customer/portal/articles/801354-writing-helpful-bug-reports-for-minecraft) does not work for me. 

Comment by Maciej Piornik [ 25/Jul/23 ]

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Can you please provide more details how to reproduce this issue? Can you please record it and upload it here?

Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:

Steps to Reproduce:
1.
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

If your ticket does not look like the example given here, then it's likely to be closed as incomplete.

This ticket will automatically reopen when you reply.

Generated at Sat Jan 11 08:22:19 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.