administrators

@kyralee Nope. Maybe a temporary issue with caching or something.

Please report if you see it again.

@kyralee Which room?

@tigga It's deployed to the official server.

@tigga Maybe one approach could be implementing two new methods Game.map.visual.export() returning a JSON strings block with currently constructed visuals and Game.map.visual.import(string). Do you think this will solve your issue?

@tigga This would be a nice addition, however it requires major refactor of how visuals data is stored on the backend, both room and map, they reuse the same storage. We recommend you to generate them only when needed and store in memory. Rendering itself (Game.map.visual methods) is not very CPU-consuming part, it simply makes a bunch of JSON.stringify.

We're excited to announce that MapVisual API is now live!

It allows you to draw simple graphics on the world map similarly to RoomVisual API. You can use it to display helpful infographics, debug info, multi-room paths visualizations, etc. It is available only in the new alpha version of the world map.

Check out the documentation for Game.map.visual.

We're excited to announce that MapVisual API is now available to test on the PTR!

It allows you to draw simple graphics on the world map similarly to RoomVisual API. You can use it to display helpful infographics, debug info, multi-room paths visualizations, etc. It is available only in the new alpha version of the world map.

Check out the documentation for Game.map.visual.

This feature will be released to production on September 6.

Should be fixed now

@zinki Thank you for the report, we'll take a look

We reworked decorations sidebar: creeps decorations moved into 'Creep' panel.