PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Passives altered by Timeless Jewels remain when switching classes

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

Nobody has claimed this yet.

bug
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?

Pathing to a timeless jewel changes all of the nodes around it accordingly. Switching to a different class (breaking the tree) should reset the nodes

What is the actual behaviour/value?

The nodes remain until you path around again

How to reproduce the issue

No response

Character build code
eNqtWttz2jgXfy5_hYen75tJwDcMZGB3ciEJO5BSIGm7Lx1hH0Bb2aK2nITd2f99j2xzaRqCrDYPxMi_c9G5S0nn9-eQGY8QJ5RH3apVM6sGRD4PaLToVu-n16et6u-_VTojIpbv5xcpZfLNb5V3nezZYPAIDOmqhiDxAsTDhpPzBTmtSCSWwKMh-YvHNzzoVu94BFVjRqKAis03n5EkuSMhdKtDEpM0gLhqkMSHKLjcvcqxIaHRhPtfQdzEPF1lkh8pPA15gJj-cPR-PN2TS6N9uaj2u86IkTXEE0GEkeBHt3qOuycLuCIhfiI3wlJk5dbsdst2G57lmk7DqtZfJ56sAIItkVWzDwFHMfTmc_AFfYTLmIrLJYn8nTjzEF1Z7DBlgq4YlTbcatU4RHH7A3PLPMh-ygVhV6PJFtuoWY1mq-02Ha_l2tbbdFwc38BHKpYXDC2qIUXS9hcRFaBJPOI04dFP7G-f9LCPUsYwg9SwPJzRSMsaQxKRS54o2HxA56CG7E3UcGPMIzWk1HIEMWa6UFe2FEEhYQI-x2pSRkYZkr196AnToOxNdAg0BE3ErpS0Dta3K3jeomz3EKofCQXUFTxygV3kuG5Z6vVuR7vyZdk1u-m2226rYVrewWq8XCfUJ2xInmmYhlgGp-QrRHtVsHnYY4uliDCFD9F6Xq3VPFhxr2kMepSXnAWalEvCEz1SGZ8qVsE-6J9JcD_y1aL-Poohgfhxv32-ZfU5jDFoZa-eMVAl2QkpYl-lz-WyFhCpbWQA4C9vcC4ZEwFqtWJXze03DSqxSgaVwFcMepj99wQljCMJXxin1n4LXNI8H0kcKNSyCOLFerKkwEqiiyBaX5KVQumTTtinVnLG9-KU4mifpKTBeo8k2a-Vh4tevpscrhZVgLMYEgSgOoGOYv6XnHFZObLzOORprOiPHKy0gU2Zz2f7MQSpr9ZXtqP6EIMlxNTI5nw8ZOzMfIj0guHxRHXjyJaxUhTnQhD_6xUPFlBKSHmKSbpaYYGQ0aJKJ5vbGBK6N1acegro95iRSgkpe6C6gB1aWcC2u6tLeUGivhfZlUtsZgdXFnGNhw2lk8aIPyHLpTzCJ-XQOFZsCZyDesQQ_b1W5v8dXElALwrSWMaosoyXFD-K6dSzKw751A9XPBbZ4iVhfpKx7EerVBhRdjkR0sT_Mkvnc3kPUUURcXZ_0ru-7l1O-w-9Qot9kuQrZexLlIYzeVTPf-_KygSySmX4nDGySiDoViPKqgbFh4mknGBt9oUCGge-4mrjOBabrx9TNN9xqDzPK6iaXY8cx8mbCwUY-oEwUDXRdL0C6fFEzUpFkTuOzW4oFHD5hYLKtrJrCxWjg0_WCrjtCKGA7TE4p0z2OBU7DTHQ8-aogsZmFdNZKpQiKjtqKGgg52eFbe1PiEqRrwIrBhUF8cVUdhxZdACVsMMxQdFFVzAHDGalRM6KQ34mzMvepsR1sixKjARr3w2EycUae8m1NOiLq6mQCAw3CAfyMnjKZUUlvoB4kF8OzwlLZFHcZ9OtijjFxQDmJGVy_UNKGBVrWbL3VgsWmbbJkj_JoSTnI7M7QY8MBvmbcyYKFlLIRmq2o2kMYJBsnpMTpKyyuVnwy_5Fcz_IpIckQeXXRZh3q1idsarjg-01bOfEbVrNxknDbHn2iet6pnfiWJ7dOrE9q-2d2G3LObEapufiy7aJy06rZSGk7eBns91un7QbliVx7XbVEKja3p251Squw6UquZbvOr0Aq0NwJ3Wo5yv340H28G4pxCo5q9efnp5qKyKWfA7POHzXfB7WV8gGd3yaNZpTKah-jj8Xi9751UeYPX_z0lGUDv9kHwafp_Hn2H4OJp_WTXbTYn84_RFCu5mw-kZaJ794T3LRxbfMNlLbbPsYUgLCXPlC1_oeFX5Bk2dBJn0iH-44Vgf5Ti5uvmQee6DwZCSALWk5EbF0w9-ch5-7VbfdqjU8x3Rzx98CEUOyKoJEYoqgaRUhgy3giqIz4ywlNpEngZ_khVGzXWubXnEb1emj_kkRLPJ5AiL7I0OaQH5p9hHIikfZshSY93UE4vAQUxLhspsnVuG-MS6L9Zlxf9f_cN-r3DAeU54mxgPBor-uTGmInTxJjD_gCVhlAGSRwpkxgAWGROUh53lmXPF4jQS7hU90Rr6lZLfwJ8Sr5R7gfJlipazkcwIExvaF-6NMNNcYvp0ZtlkZk4CmCSogp6LKgIYy9gzBzwyrgu2XUZ8KfG1W_in2e2b9-w8OUgs4M2uNfy8wCBFPIwN_GzPGeWDwufE_yzRPW6Zp_t9ICI4Yc-rvUHIekqDNHrec7V_FeWOsLWfnV3EurL5l7P4qxoX7RnkSJ_J1nLnGIDEYlzz6lmJAB8ZsnZE9EMIqt9hIMLr8LO9wEh1LTYxMH3lN09jEZZGZBxH2UYRzFLG53K3L3NgmCabNwUzaT5rOhPHNoJzDDGvyRFbG-WydJIQZRfFp7AqOuVHpFdKXZLYa2duoC85FoqnQa3s5otQFMFGS5Bo7yVfDUVLJfk0lR8-8akawfxGZq6ekpyfN07emTjwd8cAt4OQuygp6JZI8HTlHwg9b3aM8ipdn7OhnkaUjz9WLBUsv8tzj7lExbFm2r4WX5saV6k5DQx-NGugcExOsjfzYVtJ9r1tZK74aOkRKKaniCK19NrTNamv43dPLJEcvfJ3yUebql32NmLa0je-oBISrAtJQ-yeGH0VP6nvB04hKfTf8RLiolmRJq5g16lANy41ptFCbBEoXioPm1SwX6v7U2Y6jYCdL3w2utrUaOrtRyRf9ID-i0nmYsld6W36YxANjdoOU3dRkf5Lh0ZwuENGpv_w31f8A8p1eaA==
Screenshots

image

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

Start in the passive-tree and class-switching flow, then reproduce the issue by applying a Timeless Jewel passive transformation and switching classes. Check how the transformed nodes are recalculated after the class change. Done means the altered passives reset immediately when switching to a class that breaks the tree.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
desktop-dev, game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.