A number on a game screen can be only two characters wide, yet keeping it sharp while objects move behind it takes more work than drawing those digits once. On 10 November, the Defold Foundation released version 1.14.1 of its game engine, adding runtime vector fonts, faster animation-related processing and more precise information about where user inputs originate. The update is aimed at people building games for phones, browsers and computers, rather than at players installing a new title.
On a phone, the stake amount may appear between animated reels and the control that begins the next round; in slot games, those labels must remain legible even while the graphics fill most of the display. Defold’s changes concern how a game engine renders text and handles inputs.
New fonts, old browser limits
Before this release, Defold projects commonly relied on font textures prepared in advance. Version 1.14.1 adds runtime vector rendering and the option to generate glyphs as needed. Newly created font resources now default to Vector mode, while existing resources configured for signed distance field (SDF) rendering continue to work as before.
A label can now scale from phone to tablet without a separate pre-rendered texture for every size. The release adds emoji support, too, though longer translated labels still need room.
There is a compatibility boundary. Vector fonts require newer shader features and cannot be used with OpenGL ES 2.0 or WebGL 1. Defold also excludes those older shader targets by default in new builds. A project still serving older browsers has to account for that; the engine does not silently switch a vector font back to SDF on an unsupported device.
What a 95% speed figure measures
The largest number in Defold’s release notes is a roughly 94–95% improvement in particle-vertex generation during a test involving 200,000 particles. That measurement came from an M1 Pro system using Metal and the engine’s tested default materials. It is not a claim that a finished game will run at nearly twice its former frame rate.
Another benchmark involved 100,000 game objects. Updating their transforms and animations was between 1.17 and 3.25 times faster, depending on the test case. Textures, game logic and drawing still take time in a finished scene.
| Change in 1.14.1 | What the release establishes | Important boundary |
| Runtime vector fonts | Sharp text across varying sizes | Requires newer graphics features |
| Particle processing | Around 94–95% faster vertex generation in one benchmark | Not an overall frame-rate figure |
| Object transforms | 1.17–3.25× faster in measured 100,000-object tests | Depends on the scene |
| Input-source reporting | Distinguishes touch, mouse, keyboard and gamepad | The game still handles each action |
| MP4 capture | Records desktop debug sessions | Not a universal recording feature in published games |
Existing games would need to be rebuilt and tested to benefit from the changes.
A finger, a mouse and a camera cutout
On a phone, a tap can be translated into a mouse-style event. Defold’s new action.source field helps developers tell whether input came from touch, a physical mouse, a keyboard or a controller. That matters when one action must not be counted twice, or when different input methods need different responses.
The visual element of a timed selection has to stay separate from its accepted action. On a compact touchscreen, where a changing figure sits beside a control, adults who play Aviator see the multiplier rise during a round while a cash-out request must be accepted before that round ends. A smoother animation does not alter the result generated by the game.
Betting and casino interfaces contain several kinds of information that can look similar on a small screen. In sports betting, a quoted price may change before a wager is accepted, while the stake entered and the confirmed bet remain separate records. A result shown on a sports scoreboard does not itself establish whether a selection has settled. Casino screens also distinguish the amount staked, the outcome of a completed round and the balance recorded afterward. Clear labels, timestamps and confirmation messages help keep those stages distinct. Defold’s sharper fonts and input-source reporting provide technical tools for displaying and handling information; the application still determines how each action is recorded.
Two other changes concern mobile displays. HTML5 developers can set minimum and maximum rendering pixel ratios, limiting how many pixels are drawn on high-density screens without changing the canvas’s physical size. On supported phones, the window.get_reserved_areas() API supplies information about display cutouts and other areas where essential controls should not be placed.
The engine supplies the boundaries; the project still has to place its buttons sensibly.
Changes outside the game window
The release extends beyond the game screen. Defold now supports native Lua debugging through the Debug Adapter Protocol, allowing breakpoints, step-by-step inspection and examination of variables. Its editor can also inspect meshes and materials inside glTF and GLB assets and import Draco- or Meshopt-compressed files. That support concerns asset import, not decompression of those formats during gameplay.
Desktop debug builds can record MP4 footage for reviewing a scene or reproducing a visual issue. Windows projects can select OpenGL, Vulkan or DirectX 12 in the app manifest, with OpenGL remaining the default. Developers maintaining older targets still have migration work to do, particularly around font shaders and legacy graphics support.
For mobile and browser teams, the most consequential details may be the least spectacular ones. A value that remains readable, a tap registered once and an interface that avoids a camera cutout are all small results of decisions made in the engine and the project. Defold 1.14.1 supplies new tools for those decisions; it does not make the testing optional.


