World Map/Sign Bug

[NineteenGiraffes]

Sign placed back before BB logs in 1.3, saw a typo on world map the next day and fixed sign:

The fixed sign is in the same location as the one with the typo.
The first sign said had SW not NE.

Sign as seen today on the world map:

As you can see it is still showing the typo form when I first placed the sign in 1.3.

And yes I cleared my cache and used a different browser, it is not on my end.

Long story short, if you replace a sign in the same location, world map will not update it, EVER.

 

[Cpt.Carnage]

Hmm, Try this Nineteen. Smash the sign, see if it is removed from the map the next day. Then replace it.

I think that may force the sign to update.

 

[Yennage]

Hmm I believe I know the cause for this and a quick fix. Long story short, the world map plugin will go through the map files checking for updates against its cache files. This is done on a per-chunk basis (I believe) so if a block in a chunk has been edited, it will be re-rendered and therefore update the map. HOWEVER, in this case when checking your chunk it would have come up with no updates as there was a sign in that position before, and a sign there after you changed to text (when looking for chunk updates the text of the sign isn't read as I believe it would take too long) so it would have assumed everything in that chunk was the same and not done the updates (and therefore not read the updated text from the sign).

Now here's what I believe should be a simple fix. Head to that area where the non-updated sign is and mine/place a few blocks (basically so the chunk doesn't match the cache when the map next updates). That way when the plugin next runs it should register that changes have been made and therefore update the text of the sign.

Hope this helps and lemme know if this doesn't sort it!

 

[NineteenGiraffes]

I have 3 signs with this problem, one I moved down one block, and the other two I dug up some dirt right next to them, we shall see if it works. Sorry Cpt.Carnage I am going to try the "done in one day" method first.

 

[CommanderFluffy]

heres the problem... it all comes down to one simple fact.

you need to update a bunch of blocks in taht region for the map to recognize a change when re rendering for a forced update.

about 10 blocks placed around their should do.