Cargo Race Setup and the Documentation Nobody Reads
Most people who pick up And Percy Cargo Race Instructions end up frustrated because they skim straight to the screenshots and skip the rules section. I made that mistake on my second run. The instructions are not hidden, but they are dense and the order in which the sections appear does not match the order you actually need to process them when you are sitting at the starting grid, five seconds before countdown. The document is a rulebook and a setup guide rolled into one. It covers how cargo manifests are assigned, how race routes are generated, how weight distribution affects maneuvering penalties, and the specific adjudication process for collisions and port violations. It also includes the configuration files for custom map sets, which is where most people go wrong if they are trying to run a private tournament. Here is the thing nobody tells you about cargo race mechanics: the instructions assume you already understand basic weight-to-drag ratios, but they never explicitly state that the penalty multiplier kicks in at exactly 110% of your vessel baseline tonnage. I found this out after three DNFs in a row because I kept loading slightly over spec and wondering why my speed dropped off a cliff on the third leg. The workaround was simple. I set up a quick spreadsheet that cross-references each route's weight threshold against the vessel class I was using, and I stopped eyeballing cargo assignments. That cut my average race time from around 45 minutes to about 22.
Setting Up the Base Configuration
You need the runtime environment first. The game ships with a portable launcher, but the instructions assume you are installing from source if you are modding anything. If you just want to run the default package, download the main archive from the official repository and extract it to a directory that does not have spaces in the path. The installer has a known issue with Windows paths that contain spaces, and it will silently fail during the manifest validation step. I wasted an afternoon on this before I saw the error log mentioning backslash conflicts. After extraction, run the configuration wizard. You will be prompted for your vessel class, your home port, and whether you are running solo or networked. The network mode requires a separate port configuration that is not documented in the main PDF. It lives in a separate text file called netconfig.txt in the root directory. You need to set your bind address and your matchmaking port. Default is 8765. If you are behind a symmetric NAT, this will not work without manual port forwarding, and the instructions only mention this in passing on page 47.
Loading Your First Manifest
Cargo manifests are the core of every race. Each manifest specifies a weight, a volume, and a set of time-sensitive waypoints. The instructions walk through the manifest editor, but they do not explain the priority scoring system, which is what actually determines your race outcome more than raw speed. Here is how it works. Every waypoint has a base score. Delivering early adds a bonus. Delivering late subtracts from your total. But the hidden variable is the weight penalty curve. When your cargo exceeds your vessel's optimal load range, the game applies a non-linear drag factor. It starts mild at 105% capacity, but by 120% you are looking at a 40% effective speed reduction. This is not intuitive from the UI. The speedometer does not adjust to reflect drag. You just go slower and wonder why. I built a reference table for my own use. It maps vessel class to optimal load range, then shows the drag multiplier at each percentage bracket above that. The table took me about 40 minutes to compile across five test runs, but it has saved me countless hours since. If you are serious about competing, do the same. Do not trust the in-game HUD numbers alone.
Common Pitfalls in the Instructions
The documentation has gaps. Not errors, but gaps. The section on collision adjudication assumes you know the difference between incidental contact and aggressive ramming. The rules differentiate between the two, but only in the appendix under dispute resolution, which most people never open. Incidental contact during a tight turn carries a warning. Intentional ramming carries a point deduction and a temporary speed cap for the remainder of the race. Another gap is the weather system. The instructions mention dynamic weather as a variable, but they do not explain how precipitation affects certain cargo types. Perishable goods degrade faster in rain. Heavy metals do not care. If you are running a mixed manifest and you do not know which cargo type you are hauling, you are flying blind. I learned this the hard way when a sudden squall on the northern route cost me three points because I had declared perishable without checking the manifest tags.
Advanced Maneuver Tactics
Once you understand the rules, the race becomes about positioning and pacing. The instructions cover basic steering and acceleration, but they do not get into drafting or slipstream mechanics, which are real in this game. When you trail another vessel within three ship-lengths, you gain a small but consistent speed boost. This is not advertised in the manual. It was discovered by the community and later confirmed by the developers in a patch notes comment. Here is a practical tip that the instructions would never give you: do not draft for the entire race. Use it on long straightaways where you need to close a gap, then break off before the next turn. Drafting reduces your lateral agility by about eight percent, and the turns in this game are tight enough that eight percent is the difference between a clean line and a wall bounce that costs you four seconds.
Running a Private Tournament
If you want to host a tournament, the instructions tell you to set up a dedicated server and invite participants. What they do not tell you is that you need to sync the rule set version across all clients. If one player is on an older build, the manifest randomization seed will differ and the races will be invalid. Always verify the build number before the first heat. I have seen leagues fall apart over this exact issue. The config file for tournament mode is tournament.cfg in the data directory. You need to set the number of heats, the scoring method, and the minimum player count. There is also a flag called strict_manifest, which forces all players to use the same cargo constraints. Leave it on unless you are running a casual event. Off, and players will exploit the system by choosing lighter loads on longer routes just to maximize their time bonuses.
Where to Get the Files
The main package downloads from the official site. Mod support and community maps live on the message boards. If you are looking for the standalone And Percy Cargo Race Instructions PDF, it is included in the download bundle under docs/ and also available as a separate one-click download. Some mirrors list it as part of the source release, but the full version with the recent rule updates is only in the latest patch bundle. The instructions are thorough once you know where to look, but they will not save you from not understanding the underlying mechanics. Read them once before you start. Then play until something breaks. Then read them again with that problem in mind. That is how I ended up knowing more about cargo drag curves and collision scoring than most people who have been racing for years.
Get the Full Details
