Feat/map3

[oskarrough]

Playing around with a different structure so it's easier to understand. I didn't change a lot of code, but I did move it around.

• merged game/map.js into game/dungeon.js (same for testsI)
• moved the rooms out into game/dungeon-rooms.js
• drawing, but not finding, paths now happens in ui/map.js

This should make it easier to find things in the code.

Also:

• you no longer need to run generateGraph yourself when creating a dungeon. Example: dungeon = Dungeon({rows: 20})
• the option to customize which paths are created is now called customPaths

Still want to clarify the terminology. What is

• dungeon
• map
• node
• room vs encounter
• row/col vs width/height
• floor vs level vs y vs row

Closes #138

[oskarrough]

OK, updated and renamed a lot of things.

There is a dungeon. A dungeon has height floors. On each floor there are width nodes. Control how many of the nodes in each floor have an actual room with minRooms and maxRooms. The type of node is randomly selected from roomTypes.

One remaining confusing thing is that while dungeon.graph[1] is floor, dungeon.graph[1][0] is NOT a room, but a node. The room is at dungeon.graph[1][0].room. Maybe it's ok? Would be clearer if there would only be floors and rooms. Can we get rid of the filler nodes?

Recap:

• rows/columns --> height/width
• row/level --> floor
• encounters --> rooms
• A state.dungeon now has a graph and paths