This chapter is a directory, not a certification program. The sites below may offer free and paid assets, incompatible versions, or changing terms. When a resource looks useful, open its source and license, run the demo where possible, then test how it behaves in your own layout. Do not treat a beau...
The Iron Sepulcher is Standard of Iron's undead faction. It has no economy, recruitment loop, or player-selectable slot. Undead troops reach the battlefield through undead zones authored on the map: dormant sites that awaken, raise a garrison, and turn part of the terrain into a temporary strategic ...
This document is the permanent contract for direct commander control: what playable means, how the mode is validated, and which runtime rules make the result reliable. tools/arena/rpg_gate_manifest.json is the live record of scenario status...
Standard of Iron runs one strategic AI instance per computer-controlled owner. The AI is deliberately separated from the live ECS world: the world-owning thread builds an immutable snapshot, worker code reasons from that snapshot, the result is converted into typed AI commands, command conflicts are...
How a creature in Standard of Iron goes from "this unit is attacking" to moving geometry on screen — and why it is fast enough to do for thousands of units at once...
Everything the player hears goes through one path: a cue is requested by gameplay or QML, the cue registry picks a resource from the manifest, AudioSystem decides whether it may play, and the miniaudio backend mixes it. Music and ambience beds are chosen by tags in the manifest rather than by ID in ...
Asynchronous programming is a technique for achieving concurrency without forcing one operation to block progress while it waits for another to finish. Instead of requiring each task to complete before the next can make progress, asynchronous code can suspend waiting work and continue with other rea...
The Message Passing Interface (MPI) is a standardized, portable interface for message passing across a wide range of parallel-computing systems. It provides library routines for building parallel applications whose processes communicate by explicitly sending and receiving data. The MPI standard defi...
Multithreading lets several threads make progress within one process. Threads share its address space and resources such as open files, while each thread has its own stack, registers, and execution position...
Multiprocessing runs work in several processes, each normally with its own virtual address space. Separate address spaces help contain accidental memory changes and failures. CPU-bound work can run across multiple cores when enough independent work is available...
The CUDA and OpenCL listings in this chapter are platform API and kernel mechanics, separate from the C++20 application examples. CUDA kernels need a CUDA toolchain, and OpenCL examples need its runtime and headers. Raw device allocation, transfer, and launch calls are shown to explain the GPU execu...
Integration of VTK with a variety of tools and libraries provides flexibility and power that can significantly broaden the scope of visualization projects. These integrations allow you to combine VTK’s 3D rendering capabilities with platforms that excel at data analysis, computational processing, an...
Large datasets can be divided so queries touch less data and maintenance works on smaller units. The terms are related but not interchangeable...
An object authored in map JSON has to become two things that agree with each other: a physical body on the ground and a model on the screen. This document explains the coordinate contract that keeps them aligned, how object footprints are validated, and how the placement audit detects geometry that ...
How the game is profiled, what was found on the heaviest mission, and why the hot paths look the way they do. Source files carry no comments (the formatter strips them), so the reasoning behind each optimisation lives here...
A search may need values, coordinates, or an ordering. These are different outputs. Decide which one you need before choosing where, nonzero, argsort, or searchsorted...
Joining arrays is a modeling choice. Does the new data add observations, add features to existing observations, or add a new experiment axis? Those choices call for different shapes, even when all inputs contain the same number of elements...
Reshaping preserves the number of elements...
For A ∈ ℝ^(m×n), x ∈ ℝⁿ, and b ∈ ℝ^m...
Indexing answers two questions: which values are selected, and whether the selection shares storage with the original. The second question determines whether a later assignment changes your input...
An array has three separate properties: its shape says how values are indexed, its dtype says how each value is represented, and its data contains the values. Choosing the wrong dtype can change an answer even when the shape is right...
A real matrix A ∈ ℝ^(m×n) maps n-component input vectors to m-component output vectors. The formula...
A statistic summarizes the data you actually have. A probability model describes how data might be generated. A sample's mean is not required to equal its model's mean, and changing an axis, denominator, or weighting rule can change which quantity you are computing...
A real coordinate vector v = (v₀,…,vₙ₋₁) is an ordered list of n components. A NumPy array of shape (n,) is a convenient representation, but NumPy's shape rules are part of the calculation: they are not mathematical row/column notation inferred from how an array is printed...
Running your own Git server is about owning your source of truth. Your repos live where you decide, under rules you set, at a pace you control. That means you decide who can read and write, how code moves to production, and how the system grows as your team and projects grow. It’s pure Git under the...
Git stores your project as a graph of immutable objects. Instead of storing changes as a sequence of file diffs, Git stores snapshots of your project. Each snapshot is built from content-addressed objects, meaning each object is identified by a hash of its contents (more precisely, a hash of a short...
Some git commands are powerful but risky because they can rewrite history, move branch tips, or discard work. Used carelessly, they break open reviews, hide teammates’ changes, and make it hard to trace what actually shipped. Treat history edits as exceptional: prefer additive fixes for shared code...
Tags mark exact commits. They’re perfect for releases, rollbacks, changelogs, and CI/CD triggers. Unlike branches, tags don’t move—ever—so you can always point to the exact build you shipped...
Git offers several ways to inspect and understand what has changed in your codebase. Mastering these commands helps you monitor progress, spot issues early, and keep your project history organized. Think of it like reading the "track changes" feature in a word processor, but for your entire code pro...
HEAD is Git’s pointer to the snapshot you’re currently working on—the bookmark of your checkout. Most of the time, HEAD points to the tip of a branch (like master or main). When you commit, HEAD (and that branch) advance to the new commit...
Git branches are lightweight names that point to commits. Think of them as parallel timelines: you can try ideas on a branch without touching main, then merge back when you’re happy...
When collaborating on a project, it's essential to keep your local repository updated with changes made by others in the team. Git provides powerful commands to facilitate this process...
Git is a version control system (VCS) created by Linus Torvalds, the same person who developed the Linux kernel. It’s a tool for tracking changes to files over time, mainly used in software development but useful for any project that involves evolving files...
In Git terminology, "stashing" refers to temporarily saving changes that are not ready to be committed. This allows you to switch branches or make other changes without losing your work...
The three core actions you’ll perform most often in Git are staging, committing, and undoing changes...