Main uses of canComplexCarryFlashSuit#2259
Conversation
| {"noFlashSuit": {}}, | ||
| {"and": [ | ||
| "HiJump", | ||
| "canPreciseGrappleJump", |
There was a problem hiding this comment.
What does it mean to be self-dependant?
There was a problem hiding this comment.
Good catch, yeah I think that would be a problem. We could avoid the circular dependency by using {"tech": "canPreciseGrappleJump"}, but I think it may be better to switch to using helpers instead of trying to cram all this into the tech otherRequires. Using helpers should allow cutting down on the amount of redundant requirements too
There was a problem hiding this comment.
I guess a simpler solution is to just drop the canPreciseGrappleJump and canTrickyGrappleJump requirements here. In terms of difficulty placement it's already covered by the canComplexCarryFlashSuit and canTrickyCarryFlashSuit.
0cdb2db to
82da07a
Compare
kjbranch
left a comment
There was a problem hiding this comment.
Looks good.
I think it would be good if we had another helper, like h_ComplexCarryFlashSuit, defined as canComplexCarryFlashSuit or noFlashSuit. And then we could prevent canComplexCarryFlashSuit from being used in strats (similar to how we don't use SpringBall and instead use h_useSpringBall.)
Co-authored-by: kjbranch <61815121+kjbranch@users.noreply.github.com>
This builds on PR #2258 , which should be merged first.