Prism: Difference between revisions

From ETM
Jump to navigation Jump to search
No edit summary
 
Line 4: Line 4:
* There could still be items with repairlevel that would not be indexed correctly in the itemlib. Prism would need to store libid, amount, repairlevel...more? (books, filled shulker boxes)
* There could still be items with repairlevel that would not be indexed correctly in the itemlib. Prism would need to store libid, amount, repairlevel...more? (books, filled shulker boxes)
* Changing all code to support LibIds will force rewriting nearly every part of the plugin -> ditch mysql for postres or couchbase if possible
* Changing all code to support LibIds will force rewriting nearly every part of the plugin -> ditch mysql for postres or couchbase if possible
* Change prism logging to player UUIDs, LibIds. Add static world-event IDs; dont store in DB

Latest revision as of 01:06, 14 March 2020

Prism todos

  • We now use a item library that allows unique key based references
  • There could still be items with repairlevel that would not be indexed correctly in the itemlib. Prism would need to store libid, amount, repairlevel...more? (books, filled shulker boxes)
  • Changing all code to support LibIds will force rewriting nearly every part of the plugin -> ditch mysql for postres or couchbase if possible
  • Change prism logging to player UUIDs, LibIds. Add static world-event IDs; dont store in DB