daid / daid/EmptyEpsilon

[Bug] Zone entities are all located at 0,0 and unexpectedly selectable on the GM screen

Open
#2,874 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
869
Forks
222
Avg merge
18h 33m
Merged PRs (30d)
1

Description

All Zone entities are located at coordinates 0,0 regardless of where their points are located or rendered. The GM screen can unexpectedly select the entity location at 0,0 and move it, which moves the offset zone points.

Via @aBlueShadow on Discord

there seems to be at least some buggy/unintentional behavior. Here I am just doing a small rectangular selection (as I often do for single objects, as it is more reliable than clicking), but somehow selecting a whole array of zones

Image

@GinjaNinja32:

zones don't get their transform.position set to COM like they did on legacy, so they're all at the origin with a really big offset in their polygon points

@daid:

Dont think there was a technical reason beyond "this was easier"

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how Zone entities set transform.position and store their polygon points, then inspect how the GM screen uses entity locations for selection and movement. Verify the fix by confirming zones are positioned at their center of mass rather than 0,0 and that selecting or moving them no longer applies an unintended offset to their points.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.