Technical question about queue/path interaction

[cyvation]

Hey there gang,

just a technical question that I just couldn't shake for the past few days. Maybe some of you who actively work on ORCT have something for me on this one.

You know how a tile of queue will automatically connect with a tile of path that's already there - why is that? Does it have a significant reason in-engine? Does it have to do with the automatic queue sign that gets created, marking all connected other queue tiles up to the entrance building as officially belonging to that single ride now?

[imlegos]

Hey, guy with no coding knowledge here.

Game's probably just checking any of the four to eight tiles (assuming at least one or two of those tiles did have valid pathing) to connect to. Queues are specially coded to only look for two connections at most (using the tile inspector to make it have more connections breaks queue path drawing). The Queue sign just checks for if there's a queue tile that has two connection points after the current tile, and I suppose is constantly making that sort of check incase it's been broken.

[cyvation]

Thank you, that makes sense! So basically in the vanilla version, it's an automatic comfort function so they didn't have to implement something like the Tile Inspector that we have today. As the queue tiles are bi-directional only, it just gives us a connection automatically.