From b855d86841b05aeeee4846a4bd314ff88121cd05 Mon Sep 17 00:00:00 2001 From: ruckus7382sfgsgdf <355121112+ruckus7382sfgsgdf@users.noreply.github.com> Date: Tue, 10 Nov 2026 22:32:16 -0600 Subject: [PATCH] CONTRIBUTING: Triforce's own page (links, file names, logs) Co-Authored-By: Claude Opus 5.5 --- CONTRIBUTING.md | 321 ++++++++++++++---------------------------------- 1 file changed, 92 insertions(+), 229 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 34e60ae..c86cefd 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,12 +1,13 @@ -# Contributing to Hookshot +# Contributing to Triforce -Hookshot is a static recompilation of the Switch 2 *The Legend of Zelda: Ocarina of Time* remake: the game's AArch64 -code is lifted to C, the Horizon OS and NVN2 are implemented natively, and the GPU work is replayed on Vulkan. No -emulator is involved, and the game is built on your PC from your own copy. +Triforce is a native PC port of the Switch 2 *The Legend of Zelda: Ocarina of Time* remake. The game's code is +translated to C and built on your own PC from your own copy of the game; the system and the graphics are rebuilt +natively, with the graphics replayed on Vulkan. No emulator is involved. Triforce builds on the open-source Hookshot +project (GPL-3.0), and its code keeps that license. This page covers what to send, how to build and test it, and the rules that keep the project out of trouble. The [development guide](docs/development.md) has the full pipeline and its commands; the [design notes](docs/design.md) -have the architecture and the lessons the code follows. +have the architecture. ## The rule with no exceptions @@ -14,273 +15,135 @@ have the architecture and the lessons the code follows. never will. That includes: - the `.nup`, `romfs`, `exefs`, `.nso`, `.nca`, `.nsp`, `.xci` or `.nsz`/`.xcz` files, and any title keys; -- `work/` and everything in it: the extracted dump, `image.bin`, the lifted C, test builds, runs and screenshots; -- `hookshot.exe`, `hookshot_vk.dll`, `hookshot_programs.bin` (and its `hookshot_programs.idx`), `hookshot_pipelines.bin`, - `mkw_vk_pipelines.bin` and other build output; -- saves (`user/`), `hookshot_options.ini`, `hookshot_env.txt` and `language.txt`. +- `work/` and everything in it: the extracted dump, `image.bin`, the translated C, test builds, runs and screenshots; +- `Triforce.exe`, `triforce_vk.dll`, `triforce_shaders.bin`, `triforce_programs.bin` (and `.idx`), + `triforce_pipelines.bin`, `mkw_vk_pipelines.bin` and every other file a build or a run makes; +- saves (`user/`), `triforce_options.ini`, `triforce_env.txt` and `language.txt`. -Do not open an issue or a PR asking where to get the game, how to decrypt it, or for someone else's files. A -screenshot, a video and `hookshot_log.txt` are fine and often necessary; the log holds no game data. +Do not open an issue or a pull request asking where to get the game, how to decrypt it, or for someone else's files. +A screenshot, a video and `triforce_log.txt` are fine and often necessary; the log holds no game data. `.gitignore` covers most of this, but check `git status` before you commit. If you are not sure whether a file is game data, leave it out. -## Ways to help +## Reporting a problem -What to work on first, and the steps from claiming a problem to its release, are in the [workflow](docs/workflow.md): -priorities by severity and by how many players run the affected hardware, and the hardware tiers a change must not -break. Claim in Discord #dev-work before you start. +Open an [issue](https://github.com/ruckus7382sfgsgdf/CBeta0.2/issues) and include: + +- the Triforce version (the release name, or the first line of `triforce_log.txt`); +- your graphics card, its driver version, and your Windows version; +- where you were in the game and what you did; +- the logs: + - **a game problem:** `triforce_log.txt` from your game folder (the folder with `Triforce.exe`). If you started the + game again after the problem, send `triforce_log.1.txt` too: each start keeps the four runs before it as + `triforce_log.1.txt` (the last) to `triforce_log.4.txt`. + - **a Setup or build problem:** `setup.log` from `%LOCALAPPDATA%\Programs\Triforce`, and for a failed build the text + from **Show details** on the build page. + +Before you report: + +- Try the [newest release](https://github.com/ruckus7382sfgsgdf/CBeta0.2/releases) first. +- Search the open issues; if yours is there, add your details to it. +- For graphics or performance problems, test without ReShade, overlays, shader-cache tools and frame-generation + injectors: they change what Triforce does. +- If graphics look wrong after an update, clearing the shader caches often helps: close the game and delete + `triforce_programs.bin`, `triforce_programs.idx`, `triforce_pipelines.bin`, `triforce_pipeline_states.bin`, + `triforce_computes.bin`, `mkw_vk_pipelines.bin` and `triforce_prepared.bin` from the game folder (never + `triforce_shaders.bin`). The next start prepares them again. + +One topic per issue or pull request, in English, please. + +## Ways to help | | What | |---|---| -| **Test on other hardware** | NVIDIA cards are the most tested; the README's [status table](readme.md#project-status) says what works where, and [tested configurations](docs/tested-configurations.md) lists the runs behind it (build, hardware, driver, where, fps). Reports from AMD and Intel cards, other NVIDIA drivers, other distributions and SteamOS are useful even when everything works: add a row there. | -| **Play further** | The tested area is the start of the game. Reaching new areas, cutscenes, menus and items finds problems the developer has not seen. | -| **Report what is broken** | Use the [issue forms](https://github.com/NotRexed/Hookshot/issues/new/choose): game problem, build problem or idea. Include the version, your hardware, where you were and `hookshot_log.txt`. | -| **Send a fix** | Fork, fix, test, open a pull request. Small, focused changes are easiest to review and merge. | -| **Improve the docs** | The README, the development guide and the design notes are part of the project. Corrections and clearer steps are welcome. | - -## Before you open an issue or a PR - -- Try the [newest release](https://github.com/NotRexed/Hookshot/releases/latest) first. It includes every fix before it. -- Search the open issues. If yours is already there, add your details instead of opening another. -- English, please. -- One topic per issue or pull request. Do not mix a fix with a refactor or a batch of unrelated changes. -- Report the version you actually ran: the release name, or the first line of `hookshot_log.txt`. -- Test without ReShade, shader-cache tools, overlays and frame-generation injectors when you report a graphics or - performance problem. They change what Hookshot does. +| **Test on other hardware** | NVIDIA cards are the most tested. Reports from AMD and Intel cards and other drivers are useful even when everything works. | +| **Play further** | Reaching new areas, cutscenes, menus and items finds problems nobody has seen yet. | +| **Report what is broken** | As above, with the version, your hardware, where you were and the log. | +| **Send a fix** | Fork, fix, test, open a pull request. Small, focused changes are easiest to review. | +| **Improve the docs** | Corrections and clearer steps are welcome. | ## Development setup -You need your own supported dump: program `0400486024DEC000`, update v131072, build `e0f3ccfa`. Other versions do -not work, and the build reads the dump where it lies without changing it. Builds need about 60 GB free and a run uses -about 10 GB of RAM. Build on an SSD if you can: a hard drive works, but takes much longer, and the builder warns you -before it starts. +You need your own supported copy of the game: program `0400486024DEC000`, update v131072, build `e0f3ccfa`. Other +versions do not work, and the build reads your files where they are without changing them. A build needs about 60 GB +free and takes around 40 minutes; a run uses about 10 GB of RAM. Build on an SSD if you can. -### Windows, from the command line +The easy way to get every tool a build needs is **Triforce Setup** from the +[releases](https://github.com/ruckus7382sfgsgdf/CBeta0.2/releases): it installs the tools (Python with its packages, +llvm-mingw, the Vulkan headers, FFmpeg, SDL2) into `%LOCALAPPDATA%\Programs\Triforce\tools`. -1. Install Python 3 from [python.org](https://www.python.org/downloads/) (not the Microsoft Store build: `python -I` - does not see packages installed there) and the pipeline's packages: - - ```powershell - python -m pip install -r requirements.txt - ``` - - (the second line: the button prompts' packages. Without them the game shows the Switch's icons) +To build from a clone instead: +1. Install Python 3 from [python.org](https://www.python.org/downloads/) (not the Microsoft Store build) and the + pipeline's packages: `python -m pip install -r requirements.txt`. 2. Get [llvm-mingw](https://github.com/mstorsjo/llvm-mingw) (the `ucrt-x86_64` build) and set `HOOKSHOT_MINGW` to its - folder. Without it the build falls back to emsdk's clang at `C:\emsdk` with Visual Studio's C++ tools and the - Windows SDK (`HOOKSHOT_MSVC=1` forces that route). - -3. Copy the pieces a clone does not carry from the `tools` folder Hookshot Builder installs. Run `HookshotBuilder.exe` - from the latest release once (releases no longer carry a `HookshotBuilder.zip`): the folder is - `%LOCALAPPDATA%\HookshotBuilder\versions\\HookshotBuilder\tools`. - - | From `tools` | To | Variable | - |---|---|---| - | `tools\cpm` | anywhere | `RX_CPM` points at it (Vulkan headers and FFmpeg; without it, system headers or `HOOKSHOT_*_HEADERS`, the standalone build stops) | - | `tools\wgpu-native` | anywhere | `WGPU_NATIVE` points at it (the WebGPU fallback renderer; without it the game is built without one) | - | `tools\third_party` | `third_party\` | (its `.dll`, `.exe`, `.lib` and `.sha1` files, to the same places: `a64emit`, `lld-link`, `zbic` and SDL2) | - | `tools\work` | `work\` | (hot-function list, link order, profile and icon; without it the game builds but runs slower) | - + folder. +3. From the installed tools folder, point `RX_CPM` at `tools\cpm` and `WGPU_NATIVE` at `tools\wgpu-native`, and copy + `tools\third_party` into `third_party\` and `tools\work` into `work\`. 4. Run everything with `python -I` from the repository root. -### Linux +(Some environment variables still carry the older `HOOKSHOT_` name; they work as documented.) -Either use the `Hookshot--x86_64.AppImage` from the Releases page, or build the environment and the AppImage -yourself: +### Triforce Setup -```sh -scripts/linux/deps.sh # LLVM, Python packages, FFmpeg with dav1d, SDL2, Vulkan headers -scripts/linux/appimage.sh # the AppImage, in build-linux/ -``` - -The AppImage needs glibc 2.35 or newer and a Vulkan 1.3 driver with mesh shaders. `HOOKSHOT_JOBS` sets how many files -compile at once. The README's [Linux section](readme.md#on-linux) has the details and the runtime paths. - -### NVIDIA DLSS (optional) - -DLSS (`gpu/vk/vk_dlss.cpp`) is built in only with NVIDIA's DLSS SDK, which is NVIDIA's, under NVIDIA's own license, and -is never committed, bundled or uploaded: not in a PR, not in a release, not in a CI artifact. Fetch it for your own -builds with `scripts/ngx_sdk.py` (it prints NVIDIA's license notice and needs `--accept-nvidia-license` or a typed yes), -then build with `HOOKSHOT_NGX_SDK=`: - -```powershell -python -I scripts/ngx_sdk.py --platform windows C:\path\ngx-sdk # headers, nvsdk_ngx_s.lib, nvngx_dlss.dll -$env:HOOKSHOT_NGX_SDK = "C:\path\ngx-sdk" -python -I nx2/make_game.py --nup "C:\path\your-game.nup" --out "C:\Games\Hookshot-dlss" -``` - -On Windows the llvm-mingw build links NVIDIA's static `nvsdk_ngx_s.lib` (built for Microsoft's static runtime) into -`hookshot_vk.dll`, with `gpu/vk/vk_ngx_msvc_rt.cpp` and `host/mingw_msvc_shims.c` for what it needs of that runtime. -`make_game.py` copies `nvngx_dlss.dll` into the game folder's `ngx` folder; never put NGX's core, `_nvngx.dll`, beside -the game (it is the driver's). On Linux it is `--platform linux` (or `scripts/linux/ngx-sdk.sh`), with `libnvsdk_ngx.a` -and `libnvidia-ngx-dlss.so`. A Windows game with DLSS can be built on Linux too, with `RX_TARGET=windows` as below. -CI's `vulkan-dlss` workflow (`.github/workflows/vulkan-dlss.yml`) checks only that `hookshot_vk.dll` still links with the -SDK. It runs by hand, and on a push or pull request only when a file DLSS's build depends on changes; it accepts NVIDIA's -license for that run alone and uploads nothing. - -Never share a game folder built with the SDK. A change to the pinned release updates the file table and SHA-256s in -`scripts/ngx_sdk.py` (and `tests/test_ngx_sdk.py`), and the release named in the builder's license text -(`builder/HookshotBuilder/MainWindow.xaml.cs`). - -### Hookshot Builder - -The builder is a .NET 8 WPF app. Open `builder/HookshotBuilder.sln` in Visual Studio 2022 with the .NET desktop -workload, or build it from a developer prompt: - -```powershell -dotnet build builder/HookshotBuilder.sln -``` - -You only need Visual Studio for the builder itself. The game build uses llvm-mingw. - -The Windows app's **Build workers** choice applies to builds started from that window. **Automatic** keeps the existing -`HOOKSHOT_JOBS` override, or the build tools' free-memory policy when no override is set. A number overrides it for that -build's child process only; more workers need more memory and are not always faster. This choice is not saved: a new -window, including one started to update a game, uses Automatic again. +The launcher lives in `setup/`: a .NET Framework 4.8 WPF app, built with `powershell -File setup\build.ps1` (needs the +C# compiler from Visual Studio Build Tools). `setup\pack_tools.ps1` packs the tools zip a release carries. Never run a +development build's install, update or uninstall without `TRIFORCE_TEST_ROOT` set to a scratch folder: it would act +on your real install. ## Building | Command | What it does | |---|---| -| `python -I nx2/make_game.py --nup "C:\path\your-game.nup" --out "C:\Games\Hookshot" --language en-US` | Build a complete game folder from a `.nup`. A build takes about 40 minutes. | -| `python -I nx2/make_game.py --romfs "C:\path\romfs" --exefs "C:\path\exefs" --out "C:\Games\Hookshot"` | The same, from extracted folders. | +| `python -I nx2/make_game.py --nup "C:\path\your-game.nup" --out "C:\Games\Triforce" --language en-US` | Build a complete game folder from a `.nup`. | +| `python -I nx2/make_game.py --romfs "C:\path\romfs" --exefs "C:\path\exefs" --out "C:\Games\Triforce"` | The same, from extracted folders. | | `python -I nx2/make_game.py --check --nup "C:\path\your-game.nup"` | Check the game and its version without building. | -| `python -I nx2/dump.py --dump --set` | Record the dump in `work/dump.txt`. | -| `python -I nx2/lift.py --standalone --write` | Lift the game to C in `work/sa/gen`. | -| `python -I nx2/build.py --standalone --jobs 4` | Compile `work/sa/build/hookshot.exe` and `hookshot_vk.dll`. | -| `powershell -File scripts/run-vk.ps1 -Window -Seconds 120` | Run the standalone build with the Vulkan back end and take screenshots in `work/runs//shots`. | -| `python -I scripts/prof.py ` | Read a profile sampled with `HOS_PROFILE`, `HOS_SAMPLE` and `HOS_SAMPLE_FILE`. | -Use a separate `--work` folder or `OOT_WORK` if you keep more than one dump around. The lifted C and every build are -local artifacts; they are never committed. +The translated C and every build are local files; they are never committed. ## Testing -### Game-free checks - -These need no dump and are what CI runs, on every pull request and every push to `main`. One command runs them all: +The game-free checks need no game files: ```powershell python -I -B tests/run_all.py ``` -It runs every `tests/test_*.py` and `nx2/test_*.py` in its own process, the C++ unit tests under `gpu/vk/tests` and a -byte-compile of every tracked Python file, goes on after a failure, and ends with a table (slowest first) and every -failure's output. Name a check to run only the ones whose path contains it (`python -I -B tests/run_all.py ub_`). A new -`test_*.py` file is picked up by itself: no workflow to edit. +It runs every `tests/test_*.py` and `nx2/test_*.py`, the C++ unit tests under `gpu/vk/tests`, and a byte-compile of +every Python file, and ends with a table of results. Name a check to run only the ones whose path contains it. A new +`test_*.py` file is picked up by itself. -Some checks compile a small C or C++ fixture and need a compiler (`g++`, `gcc` or `clang++` on PATH), the SPIR-V -validator (`spirv-val`), the SPIR-V or Vulkan headers (`HOOKSHOT_SPIRV_HEADERS` / `HOOKSHOT_VULKAN_HEADERS`, or the CPM -cache in `RX_CPM` or `build-linux/deps/cpm`), or the `zstandard` package. A check whose tool is missing is skipped and -says so; CI passes `--strict`, which fails it instead. A check that cannot run in CI (a GPU, the game, a Visual Studio -prompt), or runs on one OS only, says so in its own file with `RUN_ALL_SKIP`; `--no-skip` runs it anyway. +When you add a fix, add a game-free test where the behavior can be tested without the game. For a renderer or runtime +fix, say what you saw before and after, on which GPU and driver, and where in the game. -### Checks that need your dump or a run +## Code conventions -These are slow and local, and they need `work/dump.txt` from `nx2/dump.py --set`: +- Match the file you are editing: its indentation, comment style and naming. Do not reformat unrelated code. +- Do not modify `third_party/`. Its parts are unmodified upstream copies, each with its notice in its own + `PROVENANCE.md`. +- New switches use the `RX_` prefix in the renderer and `HOS_` in the runtime, are off unless asked for, and cost + nothing while off. +- Rendering fixes must reproduce what the game itself does, not tuned factors that only look right on one screen. +- Python runs with `-I`; tests stay on the standard library. Keep line endings LF. -| Command | What it checks | -|---|---| -| `python -I nx2/test_insn.py` | Every instruction form the game uses, Unicorn against the lifted C. | -| `python -I nx2/test_leaf.py --calls` | Whole functions and call trees on the relocated image, native against Unicorn. | -| `python -I nx2/census.py --nx2` | The instruction census per module. | -| `python -I nx2/lower_test.py work/lowfail` | Shader programs that failed to lower. | -| `powershell -File scripts/run-vk.ps1 -Window` | An in-game run: screenshots, the flash detector, frame dumps and the profiler. | +## Pull requests -For a graphics fix, look at the screenshots in `work/runs//shots` and delete them afterwards; they reach -gigabytes and are derived from the game. The switches for scripted input, screenshots, frame dumps and profiles are in -the development guide's [reference](docs/development.md#switches-for-testing-and-debugging). - -### When you add a fix or a check - -- Add a game-free test where the behavior can be tested without the dump. The existing tests are small Python files - under `tests/` or `nx2/` that read source files and run them, or compile a tiny C++ fixture. -- Name it `tests/test_*.py` or `nx2/test_*.py`: `tests/run_all.py` picks it up by itself and CI runs it on every pull - request, so there is no workflow to edit. What it needs from the runner it declares in its own file, after its - docstring and imports, as plain literals `tests/run_all.py` reads without importing the test (its docstring has - the details); there is no central list to add a line to: - - ```python - RUN_ALL_ARGS = ["--cxx", "{cxx}", "--headers", "{vulkan_headers}"] # a compiler, headers, spirv-val ... - RUN_ALL_MODULES = ["zstandard"] # packages it imports - RUN_ALL_SKIP = {"windows": "POSIX signals: the Linux guard"} # cannot run in CI there (a GPU, the game, - # one OS only), and why - ``` - - `{name}` is a tool the runner finds (`cxx`, `vulkan_headers`, `spirv_headers`, `spirv_val`, `glslang`, `dotnet`); - a check whose tool is missing is skipped, or fails with `--strict`. A test that needs none of this declares nothing. -- Keep the test fast: every check shares one CI job with a 20-minute limit. Make it pass on both Ubuntu and Windows - where it can. -- If the fix is in the renderer or the runtime, say what you saw before and after, on which GPU and driver, and in - which part of the game. - -## Code and data conventions - -- Match the file you are editing: there is no formatter configuration, so use the indentation, comment style and - naming around you. Do not reformat unrelated code in the same change. -- Keep OoT-specific code in new files where possible. `nx2/`, `host/` and `gpu/` are kept close to mkw-recomp so - upstream fixes can be applied as a patch; keeping the paths and the shared files recognizable is what makes that - work. Each sync names its new mkw-recomp base commit in the commit message. -- Do not modify `third_party/`. Its parts are unmodified upstream copies with their notices in `PROVENANCE.md`; add a - new folder and a provenance note rather than editing one. -- Treat the local mkw-recomp and Eglantine checkouts as read-only references: read from them, run them, never edit - them. -- New switches use the `RX_` prefix in the renderer and `HOS_` in the runtime. They are off, or neutral, unless - asked for, and they do not cost anything while off. Document them where the surrounding switches are documented. -- The GPU replay rules in [design notes, section 4](docs/design.md#4-the-lessons-from-mkw-as-rules-here) are not - suggestions: nothing the replay reads may come from live guest memory, waits are honoured per queue, and texture - and sampler registrations stay in submission order. A change that reads guest memory at replay time is a - regression, even if it looks right on one frame. -- Python runs with `-I`. Tests stay on the standard library so CI needs no install step; the pipeline's existing - dependencies (lz4, numpy, capstone, unicorn, zstandard) are the exception, not a reason to add more. So are the - button prompts' (fontTools, Pillow, astc-encoder-py, texture2ddecoder: `nx2/prompt_requirements.txt`), accepted for - `nx2/prompt_assets.py` and `nx2/prompt_draw.py` alone, at build time. Maintainers' agents reviewing a change: check - that these four are still used only there, and flag any other use. Keep line endings LF (`.gitattributes`). -- New code has to be GPL-compatible. See below. - -## Commits and pull requests - -1. Fork the repository and branch from `main`. Name the branch for the change: `fix/...`, `linux/...`, `builder/...`, - `docs/...`. -2. Keep the pull request to one topic. Bug fixes do not carry refactors, and two unrelated fixes are two PRs. -3. Write the title as a short imperative sentence, as the history does: "Stop scanning storage-buffer tables after - one pass", "Linux: a crash report gives the whole host stack". Start the body with why the PR is needed, in one or - two plain sentences a player could follow: the bug, the missing feature or the cost it removes ("The menu's text - is cut off at 4K", "First starts spend 20 s waiting on a few shaders"). Then say what changed, how it was tested - (GPU, driver, game area, fps before and after), and link the issue it fixes. -4. Include screenshots when the change shows on screen: graphics, the menu, the start-up screen, an overlay, a - message. Before and after for a fix, the new screen for a feature, and the sizes or settings it was checked at. A - screenshot of the game is fine; the rule above is about game files, not pictures of the game. -5. Run the relevant checks. CI must pass; a change that only works on your machine is not ready. -6. Rebase or merge `main` when it has moved, and resolve conflicts in your branch rather than in the review. -7. Do not include build output, dumps, generated files or a `.gitignore` bypass. Check `git status`. - -Commit subjects decide the next release: write them as Conventional Commits (`feat:`, `fix:`, and `!` or -`BREAKING CHANGE:` for a break). The version rules, branches and changelog format are in -[docs/versioning.md](docs/versioning.md). - -Maintainer commits record AI assistance with `Assisted-by:` and `Co-Authored-By:` trailers. If you used a tool, add -the trailers that describe it; if you wrote the change yourself, there is nothing to add. +1. Fork the repository and branch from `main`. +2. One topic per pull request: a fix does not carry a refactor. +3. Title: a short imperative sentence. Body: why it is needed, what changed, how it was tested (GPU, driver, game + area, fps before and after), and the issue it fixes. +4. Screenshots for anything that shows on screen, before and after. +5. No build output, dumps or generated files. Check `git status`. ## Licensing -Hookshot is free software under the [GNU General Public License, version 3 or later](LICENSE). By submitting a change -you agree to license it under those terms. Only send code you can license that way. Do not paste code from a project -with an incompatible license, and do not paste decompiled game code or anything generated from the dump into a PR. +Triforce is free software under the [GNU General Public License, version 3 or later](LICENSE), like the Hookshot code +it builds on. By submitting a change you agree to license it under those terms. Do not paste code from a project with +an incompatible license, and never paste decompiled game code or anything generated from the game files. The third-party parts (Eden, suyu, Sirit, the Vulkan Memory Allocator, SDL, Opus, Dear ImGui, zstd, the Libertinus -fonts, zbic and the a64-kit tools) keep their own notices. Preserve them, and do not relicense their code. +fonts, zbic and the a64-kit tools) keep their own notices. Preserve them. -NVIDIA's DLSS SDK is not one of them: it is never in the repository, and nothing of it may be added (see -[NVIDIA DLSS](#nvidia-dlss-optional)). - -## Where to talk - -- **Issues:** [use the forms](https://github.com/NotRexed/Hookshot/issues/new/choose). -- **Discord:** https://discord.gg/EajnD2AJD9. Use the `hookshot-discussion` channel; the server is mainly for - web ports, and that channel is where Hookshot talk belongs. -- **Newest release:** https://github.com/NotRexed/Hookshot/releases/latest. - -Thanks for testing, reporting and sending fixes. Every report from a different GPU and every area played further than -before moves the port forward. +Thanks for testing, reporting and sending fixes. Every report from a different GPU and every area played further +moves the port forward.