Maaack's Godot Game Template: menus, options and a scene loader for Godot 4.7

What the template actually removes from a jam schedule

Every small Godot project needs the same set of screens before it needs a game: a title screen with Start and Quit, an options screen with volume sliders, a pause menu bound to a key, a credits roll, and a loader that swaps scenes without a visible hitch. The README states the objective plainly: setup menus and accessibility features in about 15 minutes. That is the whole pitch, and it is a narrower one than the name suggests. This is not a gameplay framework, not a character controller, and not a level editor. It is the shell around the game.

The intended audience is a solo developer or a small team starting a jam entry who would otherwise spend the first day wiring button signals. The README also says the template is game agnostic, working in 2D or 3D, and that it supports target resolutions from 640x360 up to 4k. That resolution claim matters more than it reads: menu layouts that break at 640x360 are a common source of last-minute jam pain, and the options menu is where a game normally exposes the settings that keep a low-resolution build usable.

The template is also explicitly positioned as scalable enough for commercial games, with the README listing shipped titles that use it. Treat that as a statement of intent rather than a guarantee. The structure supports extension, but extension is work you do.

Template or addon: two install paths with different consequences

The project ships in two forms, and choosing between them is the first real decision. As a template, it starts a new project from scratch: the Godot Project Manager's Asset Store tab, search for Maaack's Game Template, download, name the project, Install & Edit. As an addon, it goes into an existing project under addons/ and is enabled from Project > Project Settings > Plugins.

The addon path is the one with friction. The README warns that contents must land in addons/ and that you should check for conflicts, naming addons/plugin_updater/ as a conflict that is safe to ignore. It also notes you may see errors before reloading the project, and that the setup wizard starts the first time the plugin is enabled, with a window appearing behind it that you need to close. Those are small things, but they are the kind of small things that make a first-time user think the install failed.

There is a second, lighter option in the same family: Maaack's Minimal Game Template, which the README points to for users who want a minimal set of features. The plugin suite documentation at addons/maaacks_game_template/docs/PluginSuite.md describes other parts. If you only want the scene loader, taking the whole template is the wrong trade.

Installing it and running the setup wizard

For a new project, the README's steps happen entirely inside the Godot Project Manager, so there is no shell command to run. The sequence is: open the Asset Store tab, search for the template, download it, choose a project name and destination, then click Install & Edit. After the editor opens, the remaining work is the setup wizard.

The wizard is opened from the editor menu. The README gives the exact path:

Project > Tools > Run Maaack's Game Template Setup...

Running it is the step that actually configures the project. According to the README, the setup copies example scenes out of /addons/ into a folder you choose, project root by default, and those copies are the ones you edit. That is the moment the template stops being a dependency and becomes your code, and it is worth watching which files appear before you change anything.

For an existing project the plugin is enabled from the project settings, and the README describes the wizard starting automatically on first enable. If you are adding the addon rather than starting fresh, expect to reload the project once and to dismiss a stray window behind the wizard.

Beyond setup, the README links a documentation set rather than inlining instructions: BasicSetup.md, FeatureList.md, MainMenuSetup.md, OptionsMenuSetup.md, GameSceneSetup.md, UpdatingCredits.md, BlendingMusic.md, AddingUISFX.md, LoadingScenes.md, InputIconMapping.md, JoypadInputs.md, GameSaving.md, HowPartsWork.md, MovingFiles.md and UploadingToItchIo.md. Two more cover distribution: BuildAndPublish.md for CI/CD and AutomaticUpdating.md. The breadth of that list is the real feature inventory.

How the parts are meant to fit together

The repository layout shows the split directly. The addon lives under addons/, while scenes/, scripts/, resources/ and assets/ sit at the top level alongside project.godot, default_bus_layout.tres and default_env.tres. The audio bus layout and default environment are ordinary Godot project files, which tells you the template configures buses and environment settings rather than only adding scenes.

The workflow the README describes is copy-then-edit: the wizard moves example scenes out of /addons/ into your project, and you modify those copies. That keeps the addon directory as an upstream source you can update, while your edited scenes live in your own tree. The README points to MovingFiles.md and HowPartsWork.md for the details of that separation, which is the part worth reading before you start renaming things.

The menu layer itself is not described mechanically in the README. What is documented is the set of screens and the setup documents for each: main menu, options menu, pause menu, credits, scene loader. The scene loader has its own page (LoadingScenes.md), as do input icon mapping and joypad inputs. If you need to know whether the loader preloads or streams, the README does not say; LoadingScenes.md is where that answer would be.

One structural detail worth noting: the template is described as working with multiple target resolutions, which means the menu scenes carry anchors and container settings that you inherit. Replacing a menu scene wholesale is easy. Restyling one while keeping its layout behaviour is the slower job.

Where the template stops helping

The README is honest about scope, but the boundary is easy to miss. This is a menus-and-shell template. If your problem is a third-person camera, a dialogue system, an inventory, or save-file versioning, the template does not solve it. GameSaving.md exists, but the README does not describe what it covers, so do not assume it is a migration-safe save system.

The bigger risk is integration, not missing features. Adding the addon to a project that already has a main menu, a pause handler and an autoload singleton for game state means two systems doing the same job. The README's own conflict note is limited to addons/plugin_updater/, so it gives no guidance on scene or autoload name collisions in an existing project. If your project already has a scene named the same as one the wizard copies out, you are on your own.

There is also a version constraint. The README states the template is for Godot 4.7, with 4.4+ compatibility. That is a narrow band, and it means the template tracks a recent engine line rather than supporting older 4.x releases broadly. Check your engine version before installing, not after.

Finally, the setup wizard is a one-way door in practice. The README does not document an uninstall or rollback path for the wizard, and it does not describe what happens if you run it twice. If you are experimenting, do it on a copy of the project.

Compared with the minimal template and with hand-rolling

The closest alternative is not another engine's template, it is Maaack's Minimal Game Template, linked from the README. The difference is scope, not approach: same author, same addon family, fewer features. The README frames the minimal variant for users who want a minimal set of features, and the full template for covering a typical game jam while remaining scalable. If you want the scene loader and nothing else, the minimal template is the smaller dependency.

The other alternative is building the shell yourself. That is genuinely viable in Godot: a main menu is a Control scene with buttons, a pause menu is a CanvasLayer toggled by an input action, and options are a few sliders writing to a config file. What you get from the template is not a technique you could not write, it is the accumulated detail: input icon mapping, joypad inputs, music blending, UI sound effects, and resolution handling from 640x360 to 4k. Those are the parts people skip and then retrofit.

What you give up by hand-rolling is the documentation set. Fifteen linked pages describing each subsystem is a real asset when you come back to the project in three months. What you give up by adopting the template is control over the structure of your menu scenes and the assumption that its layout choices suit your art.

Licence, updates and the cost of staying current

The repository is MIT licensed, and the README links both a LICENSE.txt and an ATTRIBUTION.md inside the addon directory. MIT is permissive, which is why the template can be used as the start of a commercial project, but the ATTRIBUTION.md file existing at all is a signal that some bundled material may carry its own terms. Read both files before shipping; nothing here is legal advice, and the README does not summarise what the attribution file requires.

The maintenance picture is concrete: the last push was on 2026-08-13, the same day as the v1.5.3 release, following v1.5.2 on 2026-08-10 and v1.5.1 on 2026-08-03. Three releases in eleven days is a burst of activity, not a steady cadence, and a single burst tells you little about the next six months. The repository is not archived.

The upgrade cost depends on which install path you took. If you started from the template and edited the copied scenes, an addon update touches addons/ and leaves your scenes alone, which is the point of the copy-then-edit design. The README also documents AutomaticUpdating.md and a plugin_updater addon, and mentions addons/plugin_updater/ as a conflict that is safe to ignore during installation. That updater is the mechanism to look at if you plan to track upstream. If you edited files inside addons/ instead, you have forked the addon without a merge path, and the README's MovingFiles.md is the page that describes how to get out of that state.

Editorial conclusion

Adopt it if you need a menu shell, options screen and scene loader in Godot 4.7 and you are willing to run the setup wizard and then edit the copied scenes. Skip it if you want a minimal base with no menu layer, or if your project already has its own state machine and UI flow, because merging two menu systems costs more than writing one. Before committing, open the setup wizard at Project > Tools > Run Maaack's Game Template Setup... on a throwaway copy and check what it copies into your project root, then read addons/maaacks_game_template/docs/HowPartsWork.md to see how the addon parts are meant to be separated.

Frequently asked questions

Official sources

1. Official README
2. Project repository
3. Release notes