PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Impossible Escape Jewel Allocation in Cluster Sockets

Open
#4,659 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug: behaviour
Dominant language
Lua
Stars
5.4k
Forks
2.4k
Avg merge
1d 12h
Merged PRs (30d)
26

Description

Check version
  • I'm running the latest version of Path of Building and I've verified this by checking the changelog
Check for duplicates
  • I've checked for duplicate issues by using the search function of the issue tracker
What is the expected behaviour/value?

When the Impossible Escape Jewel is located inside a Jewel socket of a Cluster Jewel, allocation must not be possible inside the radius of the specified Keystone when not connected to the tree.

What is the actual behaviour/value?

The visual represents this, by not showing the radius circle, but the allocation in the tree is still possible.

A warning should be added aswel.

How to reproduce the issue
  1. Add an Impossible Escape Jewel to the tree.
  2. Update the tree, by allocating any Node (yes, this is a bug).
  3. Allocate any Node inside the radius of the Keystone specified in the Impossible Escape Jewel.
  4. The allocation is possible without the Node being connected to the Tree
Character build code
not required
Screenshots

No response

Contributor guide

Open the contributing guide

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

Reproduce the issue by placing an Impossible Escape Jewel in a Cluster Jewel socket, updating the tree by allocating any node, and then allocating inside the specified Keystone's radius. Trace the tree-allocation behavior for this case. Done means allocation is blocked when the node is not connected, and a warning is shown.

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
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.