Skip to content

Update description of canTrickyGMode #2220

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.

Sign up for GitHub

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

Merged
osse101 merged 1 commit into from
Aug 14, 2025
Merged

Update description of canTrickyGMode #2220

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions tech.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2540,11 +2540,14 @@
"id": 200,
"name": "canTrickyGMode",
"techRequires": [
"canComplexGMode"
"canComplexGMode",
"canInsaneJump"
Copy link
Copy Markdown
Contributor Author

@kjbranch kjbranch Aug 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know we don't usually like to have these types of requirements, but I think of this as an extension of canInsaneJump and don't typically include both on a given strat.

],
"otherRequires": [],
"note": [
"Doing something particularly precise, risky, or unintuitive while in G-mode or while setting up G-mode."
"Doing something particularly precise, risky, or unintuitive while in G-mode or while setting up G-mode.",
"This includes very precise movement, enemy manipulation, and timings, where a failure may result in soft-lock or death.",
"This also includes complex dodging of invisible projectiles or camera scroll blocks, and it can be paired with complex off-screen movement."
]
}
]
Expand Down