think these paths are wrong given this is one level deep

Is there any reason not to merge red with RR_GF_GROUND_BOTTOM? this would actually be a nice solution for what to name red.

RR_GF_GROUND_RED could be merged with RR_GF_GROUND_BOTTOM but RR_GF_GROUND_BOTTOM as a name doesn't really fit for both areas combined.

I'm pretty sure this is already the case, but getting caught always gives access to GROUND_BOTTOM right?

I'm not sure on how exactly getting caught is handled in every case as iirc it puts you in different places depending on if you have hookshot or not and on if ER is enabled or not

It's probably worth doing a quick testing sweep and noting them down in a comment, as coming out of GTG without gcard gets you instantly caught.

I'm not sure what I think about this kitchen layout, while it functions just fine it's not how I previously handled areas where merely existing in them requires an item.

How I handled it before was that the offending item is checked on entry, and then I mark the area as "Assuming this thing", figuring it is marginally more efficient (less looping checks for that thing) and less cluttered in the logic. That being said it would force RR_TH_KITCHEN_TOP to be split if done here and is probably worse for reading the check's logic in the check tracker so there are upsides of this approach.

Regardless of what we do here, we should probably come up with a general policy, even if that policy is doing things case by case (Goron tunic checks in fire were the main reason I had for doing it my way, as there would be a lot of them repeated in the temple otherwise.)

note a general policy with assumptions can't cross doors after #5105 (even thinking how to adjust fire timer by marking hot rooms & hot rooms would say how long it takes to get from entrance A to B, & logic would chain those times together)

That makes sense, then this kitchen layout is fine.

I did theorise a system for timer tracking between areas which would solve that fire temple problem, but it's not a small thing and was originally thought up to handle adult trade quest routes in entrance rando, so may need some adaption.

Probably out of scope, but this should really take an area instead of a region.

Can reach upper vines with long shot

So you saw the same zfg stream I did That shot was from salmon not red.

I even looked at map color, this is part of trouble with color coding. Still, applies to RR_GF_GROUND_OUTSIDE_GTG. Requires Gerudo Card

It'd be good to review hookshot access here in general. It's particularly important for Shuffle Climb

Went & checked around, from what I could see only other useful case is long shot can go from crate alcove to lower vines

I added the connections.

To prepare for equip swap, this should have IsChild as an OR to gcard

You can longshot from here to the jail windowsill, and from there jump to Yellow. It is also possible to reach Lime-Green from windowsill with a hovers backwalk into backflip but that's a trick.

The logical issue here is that it's possible to get onto the windowsill with only a hookshot, but only from jail, and there's no way to get thrown in jail if you have a g-card. The fix for this is likely some rando feature to get arrested while having the g-card, until then we cannot logically include jail + hookshot as a way to windowsill.

backflipping to red/bottom without taking damage isn't obvious, you have to go wide and aim for the rock which somehow doesn't hurt you, but you can do it without g-card if you time your backflip well. You also don't need a g-card if we say that getting caught in fortress always sends you to bottom. As getting arrested and sticking the landing have the same logical outcome.

More obvious and common is to backflip to yellow, take 1 heart of fall damage, and then walk down to Red. top ledge > yellow is definitely in logic with damage.

It's also possible with more hovers-backflip shenanigans to reach limegreen, this time going from the crate to the raised wall on the right, using the backflip to clear the rail, then carefully walking along the wall to reach the end and hover w/rolls to limegreen. This is more difficult than the windowsill movement but also skips taking damage.

You can longshot the chest from here, you can also hovers or do a kinda tight jump as adult to RR_GF_ROOFTOP_NEAR_GS, and jump down to RR_GF_ROOFTOP_BELOW_GS, which becomes relevant if the player gets here via hovers tricks from the jail area.

This should be top of lower vines.

These pots are under constant watch by a purple guard, so a way to deal with them or boomerang is required

Moving between the top ledge and the main section here needs hookshot to get over a wall. the corridor behind the blockage should be a separate region.

These pots can also be reached from top with rang, skipping the need to dodge the guards

This comes out in RR_GF_ROOFTOP_BOTTOM_OF_LOWER_VINES not RED

The dead end carpenter with 1 exit does not have any pots. Combined with the 2 pot carpenter stretching from south 1F to north 2F is why we need to rename these guys and the rooms to be less bad.

DEAD_END_CARPENTER is 1, POT_CELL_CARPENTER is another. STEEP_SLOPE_CARPENTER kinda works for the 2 pot guy, which just leaves what to name the initial carpenter.