Support optional markers/maps

[mathiasbynens]

As @leekuntibia said:

I'm having a hard time dealing with the Ank desert digging spots... There are so many markers that I can't click anywhere else around a tomb and it's really annoying, but I can see their usefulness of course. In similar fashion, there are also several markers around Thais of Pinatas which some players might be interested, but others certainly aren't.

We could add support for optional markers. These markers would live in a separate subdirectory (perhaps extra-markers?) and consist of a single JSON file per set of markers. Some example sets/categories:

• achievements: contains highly-specific achievement-related markers, that are unlikely to be used generally (e.g. Ank desert digging spots)
• events (or spawns?): e.g. pinata spawn points in Thais
  • not sure if we want to name this spawns, since there are spawns like undead cavebear and midnight panther that we do want to include in the standard markers
• blocklist: contains known "bad" markers that we explicitly do not want to include when importing markers from *.bin files. These include markers like "Commander Stone" which the client auto-inserts -- we don't want those, because we already have our own marker for that. This is kind of a separate feature but it could be based on the same implementation.
• ... more ideas?

[mathiasbynens]

In the tibia-map-data build script, we could then create ZIPs for all combinations of the standard markers + optional markers, and update our /downloads page + .exe to let advanced users toggle the optional sets of markers.

[mathiasbynens]

Note: this does not have to be limited to markers, but could even include map files, to account for Orcsoberfest/Percht Island for example.

[mathiasbynens]

https://github.com/tibiamaps/tibia-map-data/commit/de8740555dae61945cf9c4579d3ee401e58bd41f moves the Gold Digger achievement markers to a separate folder. We can use this to test our implementation.