Contribute

You're helping me port New Blitz 2027 to <DEVICE> (<CPU, OS and version, GPU>).

New Blitz 2027 is a native recompilation of NFL Blitz 2000 for the N64: N64Recomp turns the game's code into C at build time, from the player's own ROM, and a host app (SDL2, the RT64 renderer and N64ModernRuntime) runs it. The source is at https://github.com/blitzrecomp/newblitz. Nothing from the game is in the repository, and nothing may be added.

Read these first, in order:
1. README.md and CONTRIBUTING.md.
2. docs/PLATFORMS.md, especially "Adding a platform".
3. include/blitz_platform.h and include/blitz_host.h.
4. The closest existing port: its src/main/platform_<os> file, platform/<os>/, its Makefile targets (<os>-modern) and its guide in docs/.

Rules:
- Never add a ROM, anything extracted from one, or any team or league content.
- Don't change src/game for the port. A platform is a column in blitz_platform.h, one host-services file, packaging in platform/<os>/, and small library patches made with tools/new_patch.sh (NNNN-<os>.patch, one per library).
- Builds run on a Mac today and cross-compile. If <DEVICE> needs another build host, say so and propose the smallest change.
- RT64 needs Vulkan, Metal or Direct3D 12. Before writing any code, find out which of these <DEVICE> has, which version and which driver, and tell me. If it has none, stop: write down what a separate renderer would take, and don't start one without asking me.

Plan first: the steps, the files you'll add or change, the libraries that need patches, and what can't be checked without the device. Then work in small steps that each build: it compiles, it links, it boots to the title screen, then input, sound, saves, and speed. After each step, give me the exact commands to run on the device and what I should see, and ask me for the zip from Settings → General → Save Logs.

At the end, write docs/<DEVICE>.md: how to build and install it, what works, what doesn't, and what was tested on real hardware.

Help me add an aarch64 Linux build of New Blitz 2027 for <DEVICE, e.g. a Retroid/Anbernic handheld on ROCKNIX, Knulli or muOS, or a Raspberry Pi 5>. The source is at https://github.com/blitzrecomp/newblitz.

There's already a Linux x86_64 build, cross-compiled on a Mac: read platform/linux/toolchain-x86_64.cmake, tools/linux/make_sysroot.sh, src/main/platform_linux.cpp and the linux-modern target in the Makefile, then docs/PLATFORMS.md. Follow the same pattern for aarch64: a toolchain file, a sysroot for <DISTRO> with SDL2, FreeType and Vulkan headers and libraries, and a linux-arm64-modern target.

Things to check before building:
- The device's Vulkan driver (Mesa Panfrost/PanVK, Turnip, or v3dv on the Pi) and its version; RT64 needs Vulkan.
- How much RAM it has. Android's Potato Mode (search the source for potato) shows how the game is slimmed down for weak devices: lower resolution, no antialiasing, no Redo Play.
- How players install games on it. PortMaster is the usual way on these handhelds: propose a port folder (launcher script, controls, the ROM in a rom/ folder beside the app).

Never add a ROM or anything from the game. Don't change src/game. Give me the commands to run on the device after each step, and ask for the Save Logs zip (Settings → General). Finish with docs/LINUX_ARM.md.

I'm running New Blitz 2027 on <DEVICE> and I want it smooth: <WHAT I SEE: stutter, slow menus, heat, a crash…>. The source is at https://github.com/blitzrecomp/newblitz. I've attached the zip from Settings → General → Save Logs.

How to read it:
- blitz.log gets an [fps] line every 5 seconds of play: frames per second, the worst gap between frames, and "VIs per frame 1/2/3/4+". The game runs at 30 fps, each frame shown for 2 VIs (60 Hz refreshes); a frame held 4 or more is a hitch. tools/stutter_report.py sums a log up. src/main/fps_counter.cpp writes these lines.
- The game itself stops drawing for about 65 ms at the top of every play, as play select comes up. That one is the 1999 game's own: ignore it.
- With the environment variable BLITZ_WAITS=1 the log also says where the renderer waited (texture uploads, shader compiles, a full queue, presenting).

Tell me what the numbers show, and where the time goes: the game, the renderer, or the device (heat, memory, the display's refresh). Suggest one change at a time, in Settings first (Graphics: resolution, antialiasing, framerate) and in code only if Settings can't do it. For each, say what to measure before and after. Never add anything from the game to a patch.

Help me make a roster pack for New Blitz 2027: <WHAT: e.g. "every team as of the 1999 season", "my friends' fantasy league", "my state's high school champions">.

Read packs/README.md and tools/pack.py in https://github.com/blitzrecomp/newblitz (the format is "blitz-pack/2", and the validator's rules are the game's). My starting point is a copy of the 2026 Season's pack: <PATH TO MY COPY>/pack.json. Don't edit the original in the app folder.

Rules:
- A new "id" (letters, digits, - or _) and "title". Keep "format" and "requires_rom" as they are.
- 16 slots a team, with fixed roles: 0-2 OL, 3 QB, 4 RB, 5-6 WR/TE, 7-9 DL, 10-13 LB/DB, 14 K, 15 unused.
- Last names of up to 12 characters (letters, space, . ' -); numbers 0-99; skin 0-5 (light to dark: 5, 1, 2, 3, 4, 0); heavy 1 for the bigger build; ratings 0-5.
- Use only data I give you or that you can point me to. Don't invent details about real people; ask me instead.

Go team by team. After each one, run python3 tools/pack.py validate <folder> and fix what it reports. When it passes, tell me how to zip the folder, so I can install it with Settings → Add-Ons → Add… and pick it in Settings → Teams → Rosters.

Help me make an alternate uniform for <TEAM ID, e.g. DEN> in New Blitz 2027: <DESCRIBE IT: colours, helmet, stripes, numbers>.

I have the source (https://github.com/blitzrecomp/newblitz) built on my Mac with my own ROM imported. Read the top of tools/uniform_handoff.py and tools/import_uniform_sets.py first.

1. Run .venv/bin/python tools/uniform_handoff.py --teams <TEAM>. It writes the team's current parts as PNG templates at the exact game sizes (build/nfl_uniforms/<TEAM>/templates), from my ROM. Use them for size and layout only: they stay on my machine and none of their pixels go into the new set.
2. Draw new versions of the ten parts (helmet_side, helmet_stripe_front, helmet_stripe_back, facemask, shoulder, jersey, pant_stripe, pants, socks, numbers) at the same sizes, as new art, with a script I can rerun. The helmet side is drawn as it looks on the helmet. A part we leave out keeps the team's away one.
3. Save them as build/nfl_uniforms_out/<TEAM>/<NN_set_name>/<part>.png with a set.json: {"name": "<shown name>", "dark": <true for a dark jersey>, "kind": "alternate"}.
4. Run .venv/bin/python tools/import_uniform_sets.py --teams <TEAM> --app-folder "<my app folder>", then tell me how to check it: Settings → Rules → Uniform Picker on, then △ at team select.
5. Show me a contact sheet of the parts at 4x before we call it done, and how to zip <TEAM>/<NN_set_name>/ to share.

New Blitz 2027 goes wrong on my <DEVICE>: <WHAT HAPPENS, WHEN, AND WHAT I EXPECTED>. I've attached the zip from Settings → General → Save Logs (the log, any crash reports, device details and my settings).

The source is at https://github.com/blitzrecomp/newblitz. Read CONTRIBUTING.md, then the log. Log lines start with a tag ([crash], [savestate], [fps], [pak]…): search the source for a tag to find the code that wrote it.

Tell me what the log shows, your best explanation and how sure you are, and how to make it happen again. Before you change anything, say how we'll know it's fixed. Keep a fix small and to one feature, and match the code around it. Leave out of any patch or issue: my ROM, anything from the game, and personal details from the log.