Interactive maps

Updated 2026-08-13

A game wiki without a map is usually a wiki with forty screenshots of a map. The Maps extension gives you the real thing: an image you can pan and zoom, with markers readers can filter, linking to your pages.

It is an extension, so first check it is switched on for your wiki.

Make a map

Each marker carries a name, a category readers can filter by, and a link. Placed by hand for a dozen landmarks, read from a table for anything that also has pages.

Upload the map image. A large one is fine, it is served in tiles.
Add a map block to a page and open its editor from Properties.
Place markers, and give each a name, a category and a link.

The marker editor is a full screen rather than a panel, because placing markers is a job you do at map size. Everything it writes is ordinary block settings underneath.

The three blocks

Map embedThe one you want most of the time: a map on a page, with the category filter.

Current page mapThe same map, zoomed to this entry’s marker. Put it on a shared layout and every entry gets one.

Maps gridLists your maps, for a wiki with several regions.

Markers from a table

Placed by handFine for a dozen landmarks.When nothing else references them.

Read from a tableEvery chest, boss and resource node lives in a table with its coordinates.For anything that also has pages.

Then the map draws itself. Adding a row adds a marker, correcting a coordinate corrects the map, and nobody has to remember to update it, which is the failure mode of every hand-placed one.

It also means the map and the entry’s page cannot disagree, because they are reading the same row.

Categories readers can filter

Give each marker a category and readers get a filter. A map showing chests, bosses, merchants and fast-travel points at once is unreadable; the same map with four switchable layers is the feature people actually use.

Keep the list short and name categories the way a player would: what they are looking for, not what your data calls it.