Can't move on A2 tiles with specific tileset (set as passable)

[Parallax Panda]

So I have come across a very weird problem. On two of my maps that use the same tileset I can't move on the A2 tiles, even though they're all set to passable. See the spoiler below;

Spoiler: Tileset settings:

I know what you're thinking. Is there an event that runs an "Auto-run process" on that map?
No, there are no events placed except transfer events.

To make it even stranger, I can move if I use Yanfly's region restrictions plugin to override the impassibility(?) settings. BUT, one of the maps are looping and as I get to the map edge there's an invisible wall making it impossible to move to the next tile. Even though both tiles have the passable regions set to them?

Maybe Yanfly's region restrictions plugin isn't setup to work with looping maps. If so, that has little to do with the initial problem but it's unfortunate it couldn't be a workaround.

I'm suspecting this might be a real bug that I'll be unable to fix. But if anyone has any similar experiences, please help.

 

[Andar]

What is your version of the editor, and what is the passability on the first B tile?

In older versions of RMMV it was still possible to set the first B tile to something other than a star, and if you do that the passability on the map will be broken. Only newer versions of RMMV force the first B tile to be set to star.

Or it could be a plugin problem, in which case we'll need to see screenshots of your plugin manager.

 

[Parallax Panda]

@Andar
Some more information.

My editor is updated to the latest (1.6.2) and the passabillity of the first B-tile is a star (can't change it). I did look through my plugins and turned them all off, that didn't change anything (I don't have that many to begin with).

I did fix the problem for myself though. It worked after I made a new tileset with the exact same tile sheets and settings (tiple checked, it is exactly the same). This leads me to believe that my previous tileset settings in the database had been corrupted. And when I think about it, there's one thing that comes to mind.

This might not be super helpful in fixing this bug but I keep my laptop running for many days straight without restarting it (I do put it in sleep). RM is always open and recently have been no exception. Since I also keep GIMP and a lot of other software open, I tend to run out of memory after a while, and when things get sluggish I often reboot.

This morning was such a day. Everything was running exceptionally slow and I was in the middle of setting up my database passabillity for this tileset which later turned out to be defect. I probably should've restarted right there and then but in my mind I thought "I'll reboot after I've finished this task". But When I got to the A2 tiles it was incredibly laggy and the editor was acting weird. When I clicked on a tile it didn't register, then suddenly it registered a bunch of them at once. Some I had clicked on still didn't register properly right away so I had to re-click again and again. After a while it was so painful I just saved and restarted the computer.

I noticed the weirdness after that. Maybe the settings for that specific tileset got permanently corrupted somehow when I was running low on memory? Because afterwards I tried to change the settings several times and it showed in the database but like I said in the first post, it didn't register.

At least I found a workaround (to make a new tileset in the database).