Start parsing equipment stat blocks

[mustyoshi]

I'd like to try doing some combat calculations, so I need the equipment stats, I'll also be doing it for the monsters.

I included moving the weight scoring to it's own function in this.

  {
    "id": 20408,
    "aliases": [],
    "name": "Dark bow",
    "examine": "A bow from a darker dimension.",
    "image": "File:Dark bow equipped.png",
    "isEquipable": true,
    "isAlchable": false,
    "isOnGrandExchange": false,
    "isTradeable": false,
    "isMembers": false,
    "isStackable": false,
    "options": [],
    "relatedItems": [],
    "value": 500,
    "weight": 1.814,
    "limit": 8,
    "equipmentStats": {
      "attackStab": 0,
      "attackSlash": 0,
      "attackCrush": 0,
      "attackMagic": 0,
      "attackRanged": 95,
      "defendStab": 0,
      "defendSlash": 0,
      "defendCrush": 0,
      "defendMagic": 0,
      "defendRanged": 0,
      "str": 0,
      "rangedStr": 0,
      "magicDamage": 0,
      "prayer": 0,
      "slot": "2h",
      "speed": 9,
      "attackRange": 10,
      "combatStyle": "Bow"
    },
    "isInMainGame": true
  }

[mustyoshi]

@AntonyGarand I think I'd like to reorganize how Monster data is captured. In addition to the schema change I already pushed, I think I'd like to capture drop tables as their own json, to let us do the monster spawn information, which references a drop table by name, Goblins for example

{{LocLine
|name = Goblin
|location = West of [[Varrock]]
|levels = 5
|members = n
|mapID = 0
|plane = 0
|x:3118,y:3432|x:3119,y:3444|x:3121,y:3422|x:3126,y:3431|x:3126,y:3450
|mtype = pin
|dropversion = Drop table 2
}}

Curious how you feel about that.

[AntonyGarand]

Sounds good to me!

[AntonyGarand]

minor: str is the only shortened word: Any downsides to use the full strength instead?

[mustyoshi]

Set the initial code for the monster spawn extractor, still need to do the typing.