Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find possible solutions/alternatives to attribute requirement syncing #5

Open
LaughingLeader opened this issue Feb 1, 2021 · 0 comments
Labels
rework Requires a rewrite/rework of some system

Comments

@LaughingLeader
Copy link
Contributor

The Problem

  • When the Requirement property of an item stat changes, this change isn't synced with the client-side part of the game.
  • The client caches the Requirements value in a way that's different from regular stats. This isn't currently modifable with the script extender, so a save/load is required.
  • Previously, uniques whose requirements you changed were cloned (and the original deleted), which has its own set of problems:
    • Cloning generates a new UUID for the item, creating problems with scripts that used/look for the previous UUID.
    • Currently the unique weapon system (for placement, scripts, etc) looks for uniques by their UUID, since they're meant to be globally unique items.
  • In order to avoid the stats of uniques from conflicting with potential level upgrade boosts, requirement changes are stored in a local file, so the stat changes aren't saved internally by the script extender.

Possible Solutions (WIP)

  • Rework the unique system to be "agnostic" of the original item's UUID by dynamically maintaining a list of UUIDs for specific uniques. This can be added to / removed from upon characters receiving item root templates matching the original uniques.
@LaughingLeader LaughingLeader added the rework Requires a rewrite/rework of some system label Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rework Requires a rewrite/rework of some system
Projects
None yet
Development

No branches or pull requests

1 participant