-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing connections #24
Comments
Quick notes on potentially incomplete anchors after a glance over the visualizer:
WestHollow.FarLeftRoom is actually correct, no way out through the pressure plate door |
These anchors do need more connections in kii or bellow:
These anchors will need more connections in difficulties above kii:
At least in kii, those anchor don't have any missing connections:
|
Just adding a note since it doesn't seem to be present here yet: A path to the ShriekTP would also be relevant in unsafe because it could give the NonGladesTeleporter state |
The Shriek TP path is a pretty massive one to pathfind for because you need to destroy all willow's hearts and these have been disreguarded since gorlek's pathfinding |
It can also be noted that if you can get logical access to all willow's hearts, you can also access WillowsEnd.InnerTP, which would be a less restrictive way to get the NonGladesTeleporter state. So this will only be useful when using headers which can grant the Shriek teleporter pickup or when playing with No willows Hearts. |
Yeah No Willow Hearts + Spawn in front of the Shriek door + Spawn with Glades TP would be a simple example |
Doesn't fully random spawn solves the issue? You'll get a point on your map on which you tp to, so you don't need the teleporter in order to get the pickup. |
That's an interesting implication. We'd need a way to communicate this to logic, then it should indeed render a connection towards ShriekTP redundant. |
logic could probably just set that state to true if you spawn somewhere else than at glades TP |
Closing the issue since all the pathfinding has been done. All the paths validation can get done during the kii validation process, except for MidnightBurrows for which the issue #107 got created. |
Some anchors assume the player comes from a certain direction, and omit "backwards" paths in that direction.
Since those anchors can be spawned on, this is a faulty assumption, and the connections will be logical gaps if the player spawns there.
The kii branch parser can detect anchors with no outgoing anchor connections. (This is only a subset of the problematic anchors).
Currently these are:
Scanning the logic visualizer would probably yield further missing connections.
For all of these either the missing connections should be implemented, or the anchor should be marked as nospawn.
The text was updated successfully, but these errors were encountered: