constants.json

There are several universal constant values that are just key-value mappings and have in common that they do not fit into any of the present formats.

• QUICK_BAR_COUNT and INVENTORY_SLOT_COUNT
  • these are not and should not be tracked in windows.json, as they don't fit the format
  • note that mineflayer's QUICK_BAR_START is actually INVENTORY_SLOT_COUNT
• CROUCH_HEIGHT and PLAYER_HEIGHT (called NAMED_ENTITY_HEIGHT in mineflayer)
• several other physics related constants from here and there
  • Which of these are universal enough to be in minecraft-data?
  • How would these be extracted or manually updated?
• some protocol constants which do not fit into protocol.json
• probably some others from there, for example
  • BOOK_MAXPAGES, BOOK_CHARS_PER_PAGE
  • gamemode numbers (GM_SURVIVAL etc)
  • CLIENT_TICK_RATE

Example JSON schema:

{
  "GM_SURVIVAL": 0,
  "INVENTORY_SLOT_COUNT": 27
}

Start by reviewing the existing data formats and the linked mineflayer physics.js and SpockBot constants.py references. Decide which constants are universal and how they should be maintained, then define constants.json using the proposed mapping schema; done means the selected constants are documented and consistently represented.