You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow for the user to select a different logic set or supply their own logic files. The files in question would be the item_locations.txt and macros.txt. If the user supplies their own logic file, the responsibility would be on them to ensure that it is a valid file. There are two main use cases for this change.
The first use case is that it would allow the user to use the tracker for a previous version of the randomizer. During an event such as a tournament or a showcase, the version of the seed being played may not be the same as the one for the current version of the tracker.
The second use case would be for builds of the randomizer that use custom logic sets. A good example would be DualVission’s fork of the randomizer which has glitched logic sets and allows for custom, user-specified logic sets.
The text was updated successfully, but these errors were encountered:
The updated tracker will automatically pull the logic based on the version in the permalink, even pulling the specific commit if you're running from source. However, this currently only works for commits and tags in LagoLunatic/wwrando, so I'll keep this issue open for being able to load logic files stored in other places.
It makes sense for the tracker to be able to support loading alternate item_locations.txt and macros.txt files. However, DualVission's fork uses an XML format for alternate logic sets for some reason, and it isn't reasonable for the tracker to support that format.
Allow for the user to select a different logic set or supply their own logic files. The files in question would be the item_locations.txt and macros.txt. If the user supplies their own logic file, the responsibility would be on them to ensure that it is a valid file. There are two main use cases for this change.
The first use case is that it would allow the user to use the tracker for a previous version of the randomizer. During an event such as a tournament or a showcase, the version of the seed being played may not be the same as the one for the current version of the tracker.
The second use case would be for builds of the randomizer that use custom logic sets. A good example would be DualVission’s fork of the randomizer which has glitched logic sets and allows for custom, user-specified logic sets.
The text was updated successfully, but these errors were encountered: