Problem with Negative Relative Coordinates on ICs
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Reproduce the problem with the Ranged Collector (MC1214) IC in CraftBook 1.8.8 using the third-line coordinate value "1=-1:0:0" and the listed chest and item setup. Trace how the IC interprets negative relative x and z coordinates; done when those coordinates remain relative and the collector picks up the expected item.
Written by the indexing model from the issue text.
Description
CRAFTBOOK-3169 - Reported by Trainerredstone7
Whenever I try to use a negative relative coordinate on the Ranged Collector (MC1214) IC in the 1.8.8 version of Craftbook, the coordinate system switches to offset coordinates instead. The problem might apply to more than just Ranged Collector, but I've only tested it for that IC.
How to reproduce:
- Create a Ranged Collector sign facing in the positive z direction. On its third line, write "1=-1:0:0"
- Place a chest above the block the sign is attached to.
- Drop an item in the same block as the sign.
- Trigger the sign.
Expected behavior:
The sign picks up the the item, since the relative coordinates are centered on the block to which the sign is attached, and the negative x direction is in the direction of the sign (according to relative coordinates).
Actual behavior:
The sign fails to pick up the item. If you drop an item next to the global negative x side of the block to which the sign is attatched and trigger the sign, the sign will pick that item up.
This same problem applies to the x axis (and probably the y axis, but it doesn't matter there since the relative and global y directions are the same).
- Dominant language
- Java
- Stars
- 320
- Forks
- 165
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EngineHub/CraftBook
-
status:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
status:pending type:bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
status:pending type:bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
status:pending type:bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
status:accepted type:feature-request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in EngineHub/CraftBook
Similar issues
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/flink-agents#1156 ·
-
[source-shopify] FAILED bulk operation without partialDataUrl is silently treated as successful Openarea/connectors autoteam community connectors/source/shopify needs-triage team/use type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100