Toaster Profiler

ToasterProfiler An on-demand frame profiler for Puck supporting both the client and dedicated server. Find out what a hitch actually was: a GC pause, the GPU, an engine subsystem, or one specific method. Everything is triggered from in-game chat and dumped to plain text files. The killer feature: it catches hitches you already felt A lightweight shadow recorder keeps a rolling buffer of the last ~16 seconds. When a frame goes over ~25 ms, the profiler automatically dumps the lead-up, the spike frame, and 120 frames after it — folder named with the frame number and severity. Felt a stutter? It's usually already on disk. No need to reproduce it. Commands Type in chat: [\]/profile dump — snapshot the last ~16 s (for a hitch you just felt) [\]/profile start — clean profiling window (default 30 s) [\]/profile stop / /profile status [\]/profile shadow on|off — toggle the auto-dump on >25 ms spikes [\]/profile server — same thing, but capturing the dedicated server, triggered from any connected client's chat What a capture tells you Each capture is a folder of three text files: [\]summary.txt — per-method time table (calls, p50/p95/p99/max), Unity engine markers (GC, physics, render, GPU), a one-line CPU-bound vs GPU-bound verdict, top allocating frames, worst GC frames, per-event-name and per-handler EventManager cost, and a frame-time distribution with over-budget counts (how many frames blew the tick budget, and by how much). [\]frames.csv — one row per frame: frame time, allocations, the 3 heaviest instrumented methods that frame, GC activity, GPU time. The file for drilling into a specific hitch. [\]samples.csv — raw per-call durations for when you need them. What it can instrument Targets live in a plain targets.txt (Type::Method, one per line) and are reloaded at every capture start — no restart needed. A default list of known Puck hotspots ships with the mod. It can patch game code, its own code, and other installed mods, so "which mod is eating my frames?"