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
Some eventual API endpoints that could be useful for LevelLockHandler
getLockByFuzzyKey(FuzzyLockKey key) Would allow people to retrieve specific fuzzy locks without having to register them against a specific type for creation.
Modify <T> RequirementHolder getLocks(Class<? extends T> classType, T toCheck) or create a new method that supports multiple objects to check and builds up the RequirementHolder. <T> RequirementHolder getLocks(Class<? extends T> classType, T... toCheck) would probably be the declaration. Use case would be being able to pass all the materials of a tinker's tool directly to getLocks instead of having to calculate them and combine them manually.
Create and support a LockKey type for multiple levels of data. Example would be with being able to use point 2 and have the Tinker's materials also be able to register the fact they want to check a set of Locks (based on the traits that the different materials have). It probably would be best if this implementation allowed using getLocks so that it can expand to even more lock types.
The text was updated successfully, but these errors were encountered:
Some eventual API endpoints that could be useful for LevelLockHandler
getLockByFuzzyKey(FuzzyLockKey key)
Would allow people to retrieve specific fuzzy locks without having to register them against a specific type for creation.<T> RequirementHolder getLocks(Class<? extends T> classType, T toCheck)
or create a new method that supports multiple objects to check and builds up the RequirementHolder.<T> RequirementHolder getLocks(Class<? extends T> classType, T... toCheck)
would probably be the declaration. Use case would be being able to pass all the materials of a tinker's tool directly to getLocks instead of having to calculate them and combine them manually.The text was updated successfully, but these errors were encountered: