Extending No Signposts line

[AmethystRain]

Firstly, forgive me if this has been discussed or notated somewhere else, or... if I'm just being a derp, which I suspect, given my track record lately.

Anyway, I'm having some difficulty getting the NOSIGNPOSTS line in Settings to work right, past a certain point. I've gotten to where I have so many maps that require signposts to be annulled from one direction or another that this line surpasses the width of the script page.

Like so:

And I'm an RGSS noob, so I don't know if that actually makes a difference, but the no-signpost pairs that do pass that edge, well, aren't working (whereas the others are). I also tried putting the spill-over on a new line, and that didn't work either.

How should this be handled?

Full code for reference:

#===============================================================================
NOSIGNPOSTS = [81,36,37,57,57,66,119,125,119,124,124,120,120,121,85,87,94,95,130,57,131,57]

#===============================================================================

 

[Maruno]

I don't know why the last pair wouldn't be working. I've just checked the scripts again, and they would be counted. Are you sure you're going between maps 131 and 57?

You can insert line breaks and spaces in the middle of arrays without any problems, like so:

NOSIGNPOSTS = [81,36,   37,57,   57,66, 119,125, 119,124,
               124,120, 120,121, 85,87, 94,95,   130,57,
               131,57]

All it does is make it a bit easier to read, and doesn't affect how it actually works.

 

[AmethystRain]

Oh, well, that's a relief about the line break thing.

But, it's both of the last two pairs that aren't working...
I'm positive I'm on the right maps. As you can see, 57 is connected to a number of things, and it works just fine annulling the signposts with the other maps. 130 and 131 are the maps I just created, and I figured, "hey, let's test the sign post thing to make sure it works over the edge the page" and sure enough it didn't.

I'm trying to think of any other peculiarity with those maps from the others. Other than the fact that I've only designed the basic layout (so no events yet), 130 and 131 share the same name so that they don't show signposts moving to/from each other. I don't suppose that could confuse the signpost overrule with Map 57 some how, though?
Edit: A quick test of that makes no difference. So... I don't at all know what it could be.
Edit 2: I also tried removing one of the non-functional pairs just in case they were some how conflicting with each other. No change.

 

[Maruno]

The code that checks through NOSIGNPOSTS is fine. It doesn't interfere with the "don't show if same name" thing.

The only thing I can think of is that your new maps 130 and 131 don't have the "MapPosition" metadata set. The history of which maps you've been on (which is used as part of the NOSIGNPOSTS check) is erased whenever you enter a different (or no) region, which would mean there's no "previous" map to check and the NOSIGNPOSTS bit is never done in the first place.

 

[AmethystRain]

Well, and that's exactly what it was. I didn't realise the MapPosition thing was pre-requisite for NoSignposts, and I've always set ShowArea and MapPosition at the same time before, later, rather than just to test. Stupid question, solved. :D

Well, I learned two things, then. Not a total waste. Thank you.

 

[Maruno]

Metadata is important, clearly. :)

Thinking about it, there's no need to erase the map trail when moving to a new region. I've stopped it doing so in the next release. The region map trail is still erased, though, because it is intended to be used to show the player's progress on the Town Map (it's not currently used, though).