-
Notifications
You must be signed in to change notification settings - Fork 72
Implement a Custom Variable System #200
Copy link
Copy link
Closed
Labels
enhancementAn improvement for livesplit-core.An improvement for livesplit-core.featureA new user visible feature for livesplit-core.A new user visible feature for livesplit-core.needs further discussionIt is unclear how to progress without making further decisions.It is unclear how to progress without making further decisions.priority: highThis is a high priority issue.This is a high priority issue.
Metadata
Metadata
Assignees
Labels
enhancementAn improvement for livesplit-core.An improvement for livesplit-core.featureA new user visible feature for livesplit-core.A new user visible feature for livesplit-core.needs further discussionIt is unclear how to progress without making further decisions.It is unclear how to progress without making further decisions.priority: highThis is a high priority issue.This is a high priority issue.
We probably want to have a system that allows storing arbitrary key value pairs (probably both of type string initially). And then allow visualizing them as an info text component. The counter component can then use those to represent its inner state. The Run Editor can show them in the Metadata section. I'm guessing these variables should also have other information such as whether they are transient or are kept across attempts and whether they are read only in the Run Editor. Auto Splitters and components can provide them.