SBRL-Archive/PixelHub
Archived
1
0
Fork 0
Code Issues 1 Pull requests Activity

Corrected error code categories boundaries in the PixelHub Protocol

Browse source
This commit is contained in:
Starbeamrainbowlabs 2017-03-04 13:26:21 +01:00
parent f0ead36496
commit 41f55c3ef2
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
PixelHub Protocol.md
View file

@ -205,5 +205,5 @@ Note that a status message isn't actually contained in this protocol. This is be
It's highly likely that an error will occur sooner or later. In the PixelHub protocol, all errors have their own number, where no number is ever thrown in the same place in the code base twice, allowing for errors to be reliably traced back ot their source without a usable stack trace. The following caregories of error have been assigned: It's highly likely that an error will occur sooner or later. In the PixelHub protocol, all errors have their own number, where no number is ever thrown in the same place in the code base twice, allowing for errors to be reliably traced back ot their source without a usable stack trace. The following caregories of error have been assigned:
- 0 - A general error. Please try not to use this if at all possible. - 0 - A general error. Please try not to use this if at all possible.
- 1-10,000 - Server errors. - 1-9,999 - Server errors.
- 10,001-20,000 - PixelBot errors. - 10,00-19,999 - PixelBot errors.