TinkerStorm/hack-n-slash

Command Structure

Closed this issue · 1 comments

Each command requires...

  • a type being chat; user or message respectively
  • a name that matches the given requirements of it's context up to 32 characters
  • a description up to 100 characters

Another theory that may help resolve the blocking issue may be that a property not included before was holding up the process, although I have yet to test the service methods.

The database itself using pouchdb is makeshift at best, which may be why it's not handled correctly (if the db returns a 404, the error is uncaught and likely held in the process indefinitely).

// pouchdb 404 sample response
const response = {
  status: 404,
  error: true,
  reason: 'missing',
  docId: '1'
}

Fixed in 83566ee, but still happens in certain contexts. This will remain open to monitor accordingly.