Skip to content

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

@1ForeverHD

Description

@1ForeverHD

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'

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions