IntellectualSites / IntellectualSites/FastAsyncWorldEdit
Can't add more vertices to convex region after creating a line of vertices.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 806
- Forks
- 394
- Avg merge
- 22h 19m
- Merged PRs (30d)
- 14
Description
Server Implementation
Paper
Server Version
1.16.5
Describe the bug
When adding vertices to a convex region, if you add them in a line no other vertices will be added.
To Reproduce
Start a convex region selection.
Add a vertex to the left.
Add a vertex to the right.
Try to add more vertices somewhere else (Part that doesn't work).
Expected behaviour
To add extra vertices.
Screenshots / Videos
Error log (if applicable)
No response
Fawe Debugpaste
https://athion.net/ISPaster/paste/view/d477662482ef4101bb7031617300be0e
Fawe Version
1.17-409;11e2591
Checklist
- I have included a Fawe debugpaste.
- I am using the newest build from https://ci.athion.net/job/FastAsyncWorldEdit-1.17/ and the issue still persists.
Anything else?
Still present using only FAWE.
https://athion.net/ISPaster/paste/view/9e4d04e142b140e28755125c10fc14d8
Using the API to make a convex region then manually adding the points makes them appear using region.getVertices(), however, when trying to actually edit the region, only the original line of vertices is changed.
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.
Research direction
Reproduce the convex region selection described in the issue, including the API case where points are added through region.getVertices(). Start by tracing the convex-region selection and editing paths. Done means vertices added after a straight line are accepted and the resulting region edit includes them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100