Skip to main content
⌖ OF Intel

GUIDES

OpenFront v0.36 keybinds and build-quantity controls: J/O/I donations, hold-H, and the multiplier cycle

What OpenFront v0.36 added to its controls — the three J/O/I player-interaction keys, hold-H stacking prevention, the build-quantity stepper, Alt+scroll fine control, the v0.36.4 multiplier-cycle setting, and how to remap or bypass them on AZERTY and other non-QWERTY layouts.

Guide Difficulty · Intermediate Published Nov 21, 2026 Updated Nov 21, 2026 Reviewed by OpenFront Intel editors #v0.36#controls#keybinds#ui#build#donations#settings

Direct answer: what did v0.36 change about OpenFront’s controls?

Version 0.36 changed OpenFront’s keyboard model in one coherent direction: it moved the repetitive, count-heavy parts of the game — placing many structures at once, donating troops or gold to a neighbouring player, and cancelling a placement before it lands — out of the mouse and into a small set of dedicated keys you press or hold. Before v0.36 you could not mass-place or mass-donate with a single repeated keypress; you clicked tile by tile, which made large defensive walls and diplomatic troop gifts slow, tedious, and easy to fumble under pressure while you were also watching the border and the chat at the same time. v0.36 adds three new player-interaction keys (J donates troops, O donates gold, I cancels the current build action), a hold-to-prevent-stacking key (hold H), a build-quantity stepper that walks the placement multiplier upward and caps it at 50 per placement, an Alt+scroll wheel path for fine adjustment of the same number, and — only in the v0.36.4 patch — a multiplier-cycle setting that lets you pick the walking sequence itself instead of accepting the default one-step walk. None of these replaced the existing hotkeys; the v0.35.0 control set survives intact, so a player upgrading from v0.35 keeps every piece of muscle memory they already had for moving, building, upgrading, and attacking, and gains the new layer purely on top, with no re-learning of the base bindings and no risk that a v0.35 macro or tutorial you already know suddenly stops working. The single most decision-relevant fact in this entire patch is that the build quantity is now capped at 50 per placement because the engine’s MAX_UPGRADE_AMOUNT constant is exactly 50, so any plan to build a whole defensive wall or a full ring of buildings in one press has to be split into two batches of 50 or cycled through the multiplier until you reach the total you want. That cap is the number that actually changes how you plan mass construction, and it is the reason a v0.35 habit of clicking a tile and hoping it places enough now produces a smaller, more deliberate result on every patch from 0.36.0 onward. Read this guide before your first v0.36 ranked or FFA match if you want to know exactly which keys do what, where the 50 cap bites into a defence plan, how the cycle setting changes the feel of a long build, and how to remap or bypass the new layer on a non-QWERTY keyboard instead of discovering those limits mid-game against an opponent who already knows them and is using them to out-build you faster than you can react.

Version boundaries: what is v0.36, what is v0.35, and what changed per patch

The version split matters because the new control layer did not all arrive in one patch, and several of these features only exist if you are on the right patch, which is easy to get wrong when the release numbers are close together and the patch notes for the smaller patches are sparse. v0.36.0 is the patch that introduced the J, O and I player-interaction keys, the preventStacking binding on the H key, the build-quantity stepper, and the Alt+scroll fine-adjust path; the source of record is the v0.36.0 tag’s UserSettings file, which lists preventStacking on line 28 and retaliateAttack on line 45. The retaliateAttack binding is also present in the v0.35.0 tag, on line 38, which proves that v0.35.0 already had the retaliate key but not the new interaction keys, so the diff between the two versions is precisely the J/O/I set, the hold-H binding, and the quantity tooling, and nothing else in the input layer. v0.36.1 and v0.36.2 were balance and bug-fix patches that made no keybind changes at all, so the control surface is byte-for-byte identical between 0.36.0 and 0.36.2, and you cannot use the presence or absence of a key to tell those three patches apart in a live game; if a friend says they are on 36, that tells you almost nothing about whether they have the cycle setting. The v0.36.4 patch is the one that added the buildMultiplierCycle setting — the function exists in the v0.36.4 InputHandler and the setting is documented in the v0.36.4 UserSettings — which lets players choose the multiplier walking sequence; that setting is carried forward unchanged into v0.36.5, the version the site’s release configuration currently pins. The practical consequence is version-dependent and easy to miss: if you are on 0.36.0 through 0.36.2 you get the new keys and the 50 cap but not the cycle setting, while 0.36.4 and later give you the extra knob on top, so a ranked lobby that mixes patch levels can produce a situation where one player can walk the multiplier in a custom sequence and another is stuck with the default walk. Always confirm the exact patch you are running before you rely on the cycle option in a ranked game, and read the companion hotkeys guide for the v0.35.0 baseline this whole section is diffed against, since the two pages cover different intentions and link into each other rather than duplicating each other, and keep the shortcuts table open in a second tab if you only need to look up a single binding fast while mid-game.

The decision framework: which new control for which job

The new layer gives you three jobs to assign: mass construction, diplomatic transfer, and cancellation, each with its own key and its own failure mode, so the first skill to build is not finger memory but the habit of asking which job you are doing before you press. Mass construction is the job where the build-quantity stepper and the 50 cap live, and it is the one where the new controls change your numbers the most, because a wall that used to take one careful long click now takes a sequence of presses that each move you toward the total in controlled steps rather than one uncontrolled burst. Diplomatic transfer is the job where J and O live, and it is the one where the new controls change your risk the most, because a misplaced troop or gold donation is a gift you cannot take back, and the keys make the gesture fast enough that you can do it mid-fight without dropping your other inputs, but also fast enough that a misclick under pressure can send your whole border guard to the wrong player. Cancellation is the job where I lives, and it is the one where the new controls change your safety the most, because the ability to abort a placement before it lands removes the class of mistakes where you committed to a building on the wrong tile and had to rebuild, which used to cost you the full material cost of a wrong guess. The decision framework therefore is: before you mass-build, ask whether you can afford to split the build across two presses of 50 or whether the situation needs the whole amount in one turn; before you donate, ask whether the recipient is the player you mean and whether the amount is the gift you intend, because J is troops and O is gold and pressing the wrong one spends the wrong resource; before you place, ask whether a wrong tile would cost you more than a cancelled placement, because if the answer is yes, the I key is your insurance and you should hold it ready. A good working rule is to learn the three keys as a set, not one at a time, because they only become fast when you can donate and cancel in the same beat without looking at the keyboard, and that set-level fluency is what separates a player who uses the new controls from a player who merely knows them. If you are coming from a long v0.35 habit of careful single clicks, the retraining is real but short: the new layer does not ask you to forget anything, it asks you to add a second speed for the jobs that used to be slow, and once that second speed becomes automatic, the old careful clicks become the fallback you use only when the situation is too risky for a fast press. The whole framework comes down to one habit: name the job, then press the matching key, and let the 50 cap and the multiplier do the counting for you instead of your mouse doing the counting tile by tile.

The new controls in detail: every key, what it does, and the 50 cap

The table below is the full reference for the new v0.36 control layer, and every row is a fact you can verify against the v0.36.0 and v0.36.4 tag source and the release notes for the range, which is why the guide leads with it rather than burying it in prose. J donates troops to the player your cursor is over or the player the donation flow targets, which is the same pattern the existing gold-donation flow used, and it spends your troop resource in one press rather than building a chain of movements. O donates gold on the same pattern, so the two keys are a pair and pressing one when you meant the other spends the wrong resource, which is the most common expensive mistake a new v0.36 player makes in the first few matches. I cancels the current build action, so if you have a placement in progress on the wrong tile, I is the cheap way out that refunds the action before the material cost is committed, and it is the key you want to have ready in any fight where a wrong placement would cost you more than a cancelled one. Hold H triggers preventStacking, which the v0.36.0 UserSettings file binds to the H key and which stops a second structure from stacking onto the same tile by toggling the canUpgrade flag on the placement preview off and removing the upgrade cost, so the preview stops offering the stacked build and you are left with a single clean placement. The build-quantity stepper walks the placement multiplier upward in steps and caps the value at 50 because the engine’s MAX_UPGRADE_AMOUNT constant is exactly 50, which means the stepper cannot push you past 50 in a single placement and any larger build has to be two or more placements or a cycle through the multiplier. Alt plus the scroll wheel is the fine-adjust path for the same number, and it is the tool you use when the stepper’s step size is too coarse for the exact total you want, because Alt+scroll lets you nudge the value by smaller increments than the stepper does. The buildMultiplierCycle setting, which arrived in v0.36.4 and is documented in the v0.36.4 UserSettings and carried into v0.36.5, lets you choose the walking sequence the multiplier uses, so on a patch at or above 0.36.4 you can make the stepper walk in a custom order rather than the default one-step walk, and on 0.36.0 through 0.36.2 you are stuck with the default and have to plan around it.

ControlDefault key or inputWhat it doesVersion it exists from
Troop donationJDonates troops to the targeted player in one pressv0.36.0
Gold donationODonates gold to the targeted player in one pressv0.36.0
Cancel buildIAborts the current placement before the material cost commitsv0.36.0
Prevent stackinghold HToggles the placement preview’s canUpgrade off so no second structure stacks on the tilev0.36.0
Quantity steppermultiplier cycle inputWalks the placement quantity upward, capped at 50 per placement by MAX_UPGRADE_AMOUNTv0.36.0
Fine adjustAlt + scroll wheelNudges the placement quantity by small increments for an exact totalv0.36.0
Multiplier cycle settingsettings menuChooses the walking sequence the multiplier usesv0.36.4

Scenario: a 1v1 ranked game with a fast diplomatic gift

Assume a standard 1v1 ranked map, you are at roughly 40 gold and 30 troops, your neighbour to the east is a small early player who just took a hit from a third party and is about to fall, and you are considering an early alliance. Before v0.36, the gift of troops that seals that alliance meant moving a border guard or building a small chain of donations, which took several turns and gave your opponent a window to read your intent and react. On v0.36, the gift is a single press of J with the cursor over the eastern player, and the whole diplomatic gesture lands in one beat, which changes the timing of the alliance in a way that matters: you can offer the troops in the same turn the third party stops, so the gift lands while the eastern player is still alive and grateful, and a gift that lands on a dead player is worthless. The number that governs this is the troop amount you donate, and because J spends troops in one press, the amount you send is the amount you have selected in the donation flow, so the discipline is to set the amount first and press once, not to press J and then worry about the size. The second number is the cost of being wrong: if you press O instead of J, you donate gold instead of troops, and a gold gift to a player who is about to fall buys nothing, while a troop gift to a player who is about to fall buys an ally, so the key-choice error is the expensive one and the amount error is the recoverable one. The decision is to hold J for the ally you mean, confirm the cursor is over the right player before the press, and treat the gold-donate O as a separate deliberate action, because in a fast ranked game the two keys are close enough that a panicked press can pick the wrong resource, and the only cheap way to avoid that is to make the donation a two-step habit: select the amount, then press the matching key, with a single moment of checking the cursor in between. The 50 cap does not directly govern a donation, but the same discipline of one deliberate press rather than a repeated burst applies, because a donated amount you cannot take back is exactly the kind of cost where the new single-press model is a feature and a repeated-press habit is a liability.

Scenario: a defensive wall on an FFA map with the 50 cap

Now assume an FFA map, you are mid-game with a growing threat on your northern border, and you need a continuous wall of defensive structures along the north to stop a push before it reaches your core. The wall you want is 90 structures long, and this is the scenario where the 50 cap bites, because the build-quantity stepper caps each placement at 50 by MAX_UPGRADE_AMOUNT, so you cannot place the whole 90-length wall in one press. The plan is therefore two placements of 50 and 40, or a cycle through the multiplier if you are on v0.36.4 or later and you have set a walking sequence that reaches 40 cleanly. The number that governs this is 90, the total length of the wall, and the number that constrains it is 50, the per-placement cap, so the arithmetic is 90 minus 50 is 40, which means two placements and a final short one, and the mistake to avoid is assuming the first press places the whole wall, which it does not. The decision is to walk the multiplier up to 50 for the first placement, place it, then set the remaining 40 for the second placement, and the hold-H key is your safety in this scenario, because on a defensive wall a stacked structure on the wrong tile is a gap in your defence, and holding H while you place the second segment prevents a second structure from stacking onto a tile that already has the first, so the wall stays continuous rather than developing a double-occupied tile and an empty gap. The Alt+scroll fine adjust is the tool for the 40 remainder, because the stepper’s default step size may not land cleanly on 40, and Alt+scroll lets you nudge the quantity to exactly 40 so the second placement fills the remaining length without overshooting the cap. The whole scenario is the cleanest demonstration of why the 50 cap changes mass construction on v0.36: a wall that used to be one uncontrolled long click is now two deliberate placements bounded by the cap, and the player who plans the 50-and-40 split before the first press builds the wall faster and cleaner than the player who presses and discovers the cap mid-build, and that speed difference compounds across a long FFA game where the player who finishes defensive construction first can redirect the troops they would have spent on the wall to offence, so the cap is not just a build inconvenience, it is a timing lever that rewards the player who reads it correctly.

Failure modes and counterplays: when the new keys hurt you

The new controls fail you in specific, predictable ways, and the counterplay for each is a small habit rather than a big retrain. The first failure is the resource mix-up, where you press O when you meant J or J when you meant O, and the cost is that you donate the wrong resource to the wrong player, which is a gift you cannot take back; the counterplay is the two-step donation habit, select the amount and the resource first, confirm the cursor, then press, because the single-press model is only as safe as the selection that precedes it. The second failure is the cap surprise, where you expect the build-quantity stepper to place more than 50 and it does not, because MAX_UPGRADE_AMOUNT is exactly 50; the counterplay is to plan the split before you build, so a 90-length wall is 50 plus 40 from the first decision, not discovered after the first placement lands and leaves you 40 short. The third failure is the stacking mistake, where a second structure lands on a tile that already has one, creating a gap and a double-occupied tile in a defensive wall; the counterplay is to hold H while you place in dense areas, so the placement preview’s canUpgrade flag stays off and the second structure cannot stack, which is the entire job of the preventStacking binding. The fourth failure is the layout trap, where you are on an AZERTY keyboard and the physical key you think is J is not J, which is covered in the remapping section; the counterplay is to remap by physical position or to use the settings menu rather than assume the character layout. The fifth failure is the version trap, where you rely on the buildMultiplierCycle setting and you are on 0.36.0 through 0.36.2, which does not have it; the counterplay is to confirm your patch before a ranked game and to plan around the default walk if you are below 0.36.4, because the setting is the one v0.36 feature that is genuinely version-gated and the others are all present from 0.36.0. None of these failures is a reason to abandon the new layer; each is a reason to add one specific habit to the way you use it, and once those five habits are in, the new controls are strictly faster and safer than the v0.35 click-by-click model they replaced, which is the point of the whole patch.

AZERTY and other layouts: why the physical key matters more than the letter

The new layer binds to physical key codes, not to the letters that the current keyboard layout prints, which is the detail that makes the layout section of this guide non-obvious and worth reading before you assume everything just works on a non-QWERTY board. The source binds preventStacking to the H key code and the interaction keys to the J, O and I key codes, which means the game tracks the physical position on your keyboard rather than the character your operating system produces when you press that position, so on a QWERTY board the physical H produces the preventStacking action and the physical J, O and I produce the donation and cancel actions, but on an AZERTY board the same physical positions produce different letters, and the game still fires the same actions because it is watching the key code, not the letter. This is the same model the rest of OpenFront’s hotkeys have always used, which is why a v0.35 player on AZERTY already had this exact behaviour for the base bindings, but the new layer adds three more physical positions to the set, so an AZERTY player who has been comfortable with the v0.35 layout now has three additional keys to locate on their board, and the comfortable QWERTY assumption of J being the key right of H no longer maps cleanly to the letters an AZERTY player expects. The practical guidance is to learn the new keys by their physical position on your specific board, not by the letter a QWERTY reference shows, because a QWERTY guide that says press J is telling a QWERTY player the physical position and telling an AZERTY player a different physical position, and the one that is actually correct is the one that matches the key code the game is watching. If you are on AZERTY and the new keys feel wrong, the fix is not to change your operating system layout, it is to either remap the three new actions in the settings menu to physical positions you are comfortable with, or to use the settings menu to confirm which physical positions the defaults are bound to on your board, because the settings menu reads the same key codes the game does and will show you the true binding rather than the letter a layout assumes. The version note here is that this behaviour is identical across v0.36.0 through v0.36.5, so the layout handling did not change with the multiplier-cycle patch, and an AZERTY player on 0.36.4 has exactly the same physical-key model as one on 0.36.0, with the only difference being the extra cycle setting, which is a menu option and not a key binding. The decision for an AZERTY player is to treat the new keys as three physical positions to learn on their board, to confirm the defaults in the settings menu, and to remap any of the three that feel wrong, because the new layer is only as comfortable as the player’s familiarity with the physical positions it is bound to, and that familiarity is the one thing a reference table cannot give you on a non-QWERTY board.

Related content

Continue reading
OpenFront AFK Teammate Takeover: Absorb a Disconnected Ally for Zero Troop Loss

A Team-mode decision guide for what a teammate's disconnect does to your win/loss position, when absorbing their land is free, when it is a trap, and what the 30-second mark and the ranked 2v2 rules actually change.