Skip to content

Releases

Awake Launcher v3.3.3

Choose a tag to compare

@github-actions github-actions released this 14 Nov 13:48

Awake Launcher 3.3.3

Pairs with Awake Modpack Manager 1.2.1.

Fixed

  • Renaming an instance shared with Awake Modpack Manager now renames its folder even after File Explorer has been inside it. 3.3.2 fixed this only for ordinary instances; shared ones still failed with "Another program is using the instance folder".

If an earlier rename changed only the name and the folder kept its old name, rename the instance to something else and back.

Awake Launcher v3.3.2

Choose a tag to compare

@github-actions github-actions released this 14 Nov 11:53

Awake Launcher 3.3.2

Pairs with Awake Modpack Manager 1.2.1.

Fixed

  • Renaming an instance now renames its folder even after File Explorer has been inside it. Explorer keeps a folder open after you browse it, sometimes even once its window is closed, and Windows refuses to rename a folder while anything inside is open. The Launcher now asks Explorer to let go first. If a different program is using the folder, the rename still stops and says so.
  • Message boxes and text prompts no longer show black corners around their rounded panel. The 3.3.1 fix did not take effect.

If an earlier rename changed only the name and the folder kept its old name, rename the instance to something else and back.

Awake Launcher v3.3.1

Choose a tag to compare

@github-actions github-actions released this 13 Nov 19:06

Awake Launcher 3.3.1

Pairs with Awake Modpack Manager 1.2.1.

Fixed

  • A failed folder rename now says why. When the Launcher could not rename an instance's folder it only listed the old and new paths. It now gives the reason, most often that another program is using the folder. Windows refuses to rename a folder while a File Explorer window or another program is open inside it; close those and rename the instance again.
  • Message boxes and text prompts no longer show black corners around their rounded panel.
  • The icon in the update dialog is now drawn as a proper refresh symbol.

If only the name changed and the folder kept its old name, rename the instance to something else and back once nothing else is using the folder.

Awake Launcher v3.3.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 17:58

Awake Launcher 3.3.0

Pairs with Awake Modpack Manager 1.2.1.

Changed

  • Every message box and text prompt now uses the Awake popup look. Questions such as "Would you also like to rename the instance folder?", warnings, errors and the group and world name prompts used to open as plain system windows. They now open as the same dark rounded panel as the rest of the Launcher, with the title inside the panel and the Launcher dimmed behind it.

Fixed

  • The interface could disappear after the Launcher lost focus or was minimized, and only came back a moment after you returned to it. The Launcher now redraws its window whenever it is activated, deactivated, minimized or restored. We could not reproduce this ourselves, so please report it if it still happens.

Awake Launcher v3.2.4

Choose a tag to compare

@github-actions github-actions released this 12 Nov 12:40
b2e6e0a

Awake Launcher 3.2.4

Pairs with Awake Modpack Manager 1.2.1.

Fixed

  • Renaming a pack connected to the Manager now renames its folder too. In 3.2.3 only the displayed name changed, so the folder in instances kept the old name. The Launcher now moves the folder and updates the path the Manager saved for it in one step, so the pack stays visible in both programs.

Stop the game before renaming; a running pack keeps its folder name. If a pack's folder still has an old name from 3.2.3, rename the pack to something else and back.

Awake Launcher v3.2.3

Choose a tag to compare

@github-actions github-actions released this 11 Nov 16:17
cdc894f

Awake Launcher 3.2.3

Pairs with Awake Modpack Manager 1.2.1.

Fixed

  • Renaming a pack connected to the Manager no longer makes it disappear. The Launcher used to rename the pack's folder too, and then could not match it to the Manager's record, so the pack vanished from the list while its files stayed on disk. The name now changes and the folder stays where it is.

If a pack already disappeared this way, close the Launcher and rename its folder in instances back to the old name. It returns with the new name shown.

Awake Launcher v3.2.2

Choose a tag to compare

@github-actions github-actions released this 09 Nov 11:10
ba4fd1e

Awake Launcher 3.2.2

Pairs with Awake Modpack Manager 1.2.1.

Fixed (in the Manager's helper)

  • CurseForge mods install again. Installing from CurseForge in the Manager could fail with "CurseForge request failed (HTTP 302)".
  • The same mod from two sites no longer blocks a change. If a required mod is already in the pack from Modrinth or CurseForge, the identical file from the other site is not added again.
  • When two mods really would use the same file, the message now names them.

Nothing in Awake Launcher itself changes, and using it without the Manager still adds no background work.

Awake Launcher v3.2.1

Choose a tag to compare

@github-actions github-actions released this 09 Nov 06:57
1ed0a87

Awake Launcher 3.2.1

Pairs with Awake Modpack Manager 1.1.1.

Fixed

  • Packs can now connect to the Manager on more PCs. Choosing Manage here could fail with "Windows error 50", then say another program coordinates the instance. Packs installed through the Launcher were affected once a PC had installed more than one.
  • Packs hidden by that error come back. A failed connect could make the pack disappear from the Launcher. This version restores it the next time the Launcher starts, and your mods and worlds were not changed.
  • A file that can't be used safely now shows its name and the reason.

Using Awake Launcher without the Manager still adds no background work.

Awake Launcher v3.2.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 20:56
f8211bb

Awake Launcher 3.2.0

Pairs with Awake Modpack Manager 1.1.0.

New

  • Manage your existing modpacks from Awake Modpack Manager. Turn this on per pack in the Manager, and turn it off at any time. Your files stay in the Launcher's folder.
  • Play from the Manager. The Play button in the Manager starts the pack in Awake Launcher with your usual account, Java and GPU settings.
  • Instance images in the Manager. The Manager shows the same image as the Launcher.

While a pack is managed by the Manager

  • It keeps playing from Awake Launcher, and its Java and memory settings stay here.
  • Adding, removing or changing its mods happens only in the Manager, so one app at a time changes them.
  • Copy, export and delete are off for that pack until you stop managing it.

Every other pack is unaffected, and nothing changes unless you turn this on for a pack.

Using Awake Launcher without the Manager adds no background work: nothing polls or runs while no Manager is connected.

Awake Launcher v3.1.1

Choose a tag to compare

@github-actions github-actions released this 08 Nov 18:21
fe1acb0

Awake Launcher v3.1.1

This is a stable Windows x64 release of the Minecraft launcher. It is the first stable Launcher that can play Awake Modpack Manager projects. There was no 3.1.0 release; its build was stopped before publishing, and this version includes the fixes from that work.

Play your Manager projects

  • Open a Manager project in Launcher. Choose Open in Awake Launcher on a project in Awake Modpack Manager 1.0.0, or Link Existing Manager Workspace in Launcher's library. Launcher plays from the project's own folder and doesn't make a second copy.
  • Your account, Java and playtime stay yours. Launcher keeps those settings separately and never changes the project's files.
  • Safe while the game runs. Manager can't change a project's files until Minecraft has stopped, even if Launcher is closed while the game is running.
  • Mod installation, pack replacement, export and deletion are turned off for linked instances. Manage their content in Manager.

Fixes

  • Fixed a crash that could happen when a mods view was closed while its folder was refreshing.
  • Linked projects are now tracked on their actual Windows drive, so projects on a drive other than C: work correctly.
  • Short overlaps between Launcher and Manager on the same project now wait briefly instead of failing.
  • More reliable cancellation and clean-up for downloads and background tasks.

Connecting Awake Modpack Manager

Launcher only shares a data folder that other Windows accounts can't change. A normal install is always fine. A Compact or Custom data folder on another drive usually isn't private yet: Manager 1.0.0 explains this and offers Make folder private. Restart Launcher afterwards.

Before you update

Launcher offers this update itself, including on 3.1.0-beta.1 and beta.2. Your data location and instance folders are kept. No instances are migrated.

The installer isn't code-signed, so Windows SmartScreen may warn. Choose Setup.exe to install or update, or Windows-x64.zip for portable use. SHA-256 files come with the downloads, along with source archives, licence notices and source instructions. Manager's native helper isn't bundled with Launcher; its source archive is included as source material for the separate Manager release.