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
WIth the C# library, users are able to create their own custom specialists. In order to do this, users need an interface to customize their specialists. The website should provide this interface.
However, in order to get domain lists, the backend is going to have to heavily utilize the CLI tool to be able to return a list of all of the specialists types, events, actions, scaling, etc. To ensure that users are configuring their specialists correctly.
None of the above details have been done yet.
TODO:
Make the CLI tool return the appropriate domain lists
Backend to provide an endpoint to return the C# domain lists
Frontend to provide the interface for creating specialists
Backend to create database table to store the specialist configurations as well as a shortcode for the config like "4FJ3LA"
App to allow importing specialist "packages" by inputting the shortcode.
C# to import custom specialist configurations (In progress)
Long Term:
Allow players to 'bundle' multiple custom specialists into a package and import codes will import all of the specialists in the bundle.
Allow publically and privately sharing specialist configurations
Allow voting and comments on user-designed specialists?
The text was updated successfully, but these errors were encountered:
WIth the C# library, users are able to create their own custom specialists. In order to do this, users need an interface to customize their specialists. The website should provide this interface.
However, in order to get domain lists, the backend is going to have to heavily utilize the CLI tool to be able to return a list of all of the specialists types, events, actions, scaling, etc. To ensure that users are configuring their specialists correctly.
None of the above details have been done yet.
TODO:
Long Term:
The text was updated successfully, but these errors were encountered: