User manual
How Vegan's Loadbook works, section by section. The same words ship inside the app, so this is always the real thing.
Getting started
The two jobs Loadbook does — predicting a load and refereeing your range data — and how to pick a mode on first run.
Read →Loads & development
What a Load is, why loads are immutable history, and how the prediction card and workbench explore a charge without ever recommending one.
Read →Range data & statistics
Logging chronograph strings, why raw shots are immutable, and statistics built to stay honest on small samples.
Read →Ammo & firearms
How loads, ammo, and firearms relate — matched by cartridge — why one ammo carries many loads, and why a velocity belongs to the load, not the ammo.
Read →Finding a load for a velocity
The reverse candidate explorer — survey the powder-and-charge candidates that could reach a velocity you enter — and why it lists candidates, never recommendations.
Read →The trajectory calculator
Solving drop, windage, and a shot solution — what every column means, and where the model is least trustworthy.
Read →Truing to your dope
Correcting the model to match what your firearm actually did — and which input gets corrected, and why.
Read →Custom drag functions
Using your bullet's own drag coefficient versus Mach directly — how to import one, and why provenance is required.
Read →Powder grades & calibration
What Estimated, Provisional, and Calibrated mean — and why measured beats fitted beats estimated.
Read →Sync & backup
Account-free sync through your own cloud folder, one honest limitation, and plain-JSON export you can read without the app.
Read →Units & conventions
Per-quantity display units, why raw velocities are stored exactly as measured, and the conventions worth knowing.
Read →The command-line tool
vlb — a headless, scriptable view of the same loadbook the apps keep: survey candidates, predict a load, list your data, log a string. Referee, not cheerleader, on the command line.
Read →The honesty boundary
The rules this app holds itself to — intervals, pressure as a percentage only, immutable data, and no promise of safety.
Read →