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

Setup initial 'install' button and command-to-loader sync #8

Open
10 tasks
1ForeverHD opened this issue Feb 11, 2021 · 0 comments
Open
10 tasks

Setup initial 'install' button and command-to-loader sync #8

1ForeverHD opened this issue Feb 11, 2021 · 0 comments

Comments

@1ForeverHD
Copy link
Member

Initial setup

  • Check for Nanoblox within ServerScriptService (if descendant name is Nanoblox and is a folder and find Loader then advance)
  • If not present, display 'Activate' button (similar to the CK Studio plugin)
  • Check for descendant added within serverscriptservice, if is nanoblox then advance
  • On activation click, advance
  • On advance, display Nanoblox panel and ensure commands are up to date within the loader
  • Check for descendant removed within serverscriptservice, if is nanoblox then retreat

Command sync-check

  • Determine a way to distinguish between already loaded commands (for instance if a command has been removed, renamed, etc) and completely new commands. Data stores may have to be involved, or potentially writing and reading to/from Config
  • Have a 'new commands' section where commands can be reviewed and added in or ignored. Also have the option to 'add all' and 'ignore all'
  • If new command, print "Nanoblox new commands!" in console
  • For rejected and already-loaded commands, have these under 'inactive/uninstalled commands'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant