Autopelago 0.9.0

⚠️ UPGRADE NOTE

0.9.* is incompatible with 0.8.* and all other earlier versions. Using a 0.9.* game client requires a multiworld generated using a 0.9.* apworld.

Changes since 0.8.0

1. Added some options to the YAML that let you disable any category of buff / trap. The items will still exist, and this setting will not change their classification, the client will simply ignore the disabled ones.
2. #114: rat chat now has more fine-grained checkboxes so that you can turn off only certain specific types of messages.
3. #116: the actual content of rat chat messages can now be customized in the YAML.

Autopelago 0.8.0

⚠️ UPGRADE NOTE

0.8.* is incompatible with 0.7.* and all other earlier versions. Using a 0.8.* game client requires a multiworld generated using a 0.8.* apworld.

Changes since 0.7.3

1. #105: Add two checkboxes for disabling animations in the game screen.
2. Add some Easter egg suggestions from the community.
3. Remove the ® symbol from what is now just called "Pharaoh-Not Anti-Mummy Spray".
   • If non-ASCII characters were more significant here, then I might have been more inclined to leave it alone.
   • As this was literally the only non-ASCII character in all of Autopelago, it makes more sense to dump it and make things significantly smoother in the edge-cases where this gets run alongside an APworld or client that doesn't know any better.
4. Responses to @SlotName commands are no longer suppressed by the checkbox on the settings screen.
5. Slightly tweak the response to the @SlotName go command when the location is already being focused.
6. Add a @SlotName list command to have the rat say which locations it will focus on (up to the first 5).
7. #2, #83: You can now click an item in the side panel to directly request a !hint from the server.
   • It pops up an OK/Cancel dialog first, so that it's harder for a stray click to burn your hint points.
   • This does not bypass normal restrictions on hints: ALL that it does is send the !hint command, just like you could do yourself if you connected with the text client.
8. (APworld) Improved the descriptions of the different YAML options.

Autopelago 0.7.3

⚠️ UPGRADE NOTE

0.7.* is incompatible with 0.6.0 and all other earlier versions. Using a 0.7.* game client requires a multiworld generated using a 0.7.* apworld.

The 0.7.3 client CAN be used for a multiworld generated for any earlier 0.7.* version. The .apworld file has not changed since 0.7.0 and is provided here just for convenience.

Special Note for Existing 0.7.* Multiworlds

To those who have a multiworld in progress with Autopelago 0.7.*, please consider the following:

• If the multiworld has multiple Autopelago slots, all are encouraged to update to 0.7.3, at their earliest convenience. Once, immediately after the upgrade, the rats will all return to the beginning with no auras, and they will have forgotten about what to prioritize. After this speedbump, they should all proceed as normal.
• If the multiworld has only one Autopelago slot, then you are fine to finish it off with whichever version you started with. You could switch to 0.7.3 if you really want to, but you will encounter the same speedbump that I described in the other bullet point in order to fix a problem that doesn't exist, so it's your call.

Changes since 0.7.0

1. Possibly fixed a crash that could be triggered by as-yet-unknown circumstances. Superseded by 0.7.3.
2. Handle multiworlds where one or more of the games gives multiple different names to a single item or location.
3. Trying to run a 0.7.* client on a 0.6.0 multiworld would go back to giving an obscure error instead of the more friendly error that was added a little while back.
4. Per-game state is again stored using a key that's unique to the specific slot. Previously, it had erroneously been changed to just one constant value for all Autopelago games in the multiworld, causing them to overwrite one another.
5. The per-game state wasn't getting re-saved as often as it should have. It used to only happen when the rat received an item.

Other changes since 0.6.0

1. I've got a grown-up code signing certificate for grown-ups now, so Windows Defender might stop trying so hard to defend you from this. Unproven: you may still run into some stuff (especially from Windows SmartScreen).
2. #108: Upon reconnecting, the rat will now immediately return to where it previously was.
3. #109: If we fail to read your last settings from the lastSettings.json file, then we'll actually log the error (unless the "error" is that this is your first time running the application).
4. #52: New YAML option to choose to generate only a subset of the game that stops at either the Secret Cache or the Captured Goldfish instead of going all the way.
   • As part of this, the Lockheed SR-71 Blackbird (formerly needed to get to "Moon, The") is no longer special. Instead, "Snakes on a Planet" is now the final location so that it's more consistent with how the other victory locations work.
5. #111: Errors that take you to the scary-looking error screen will now also be logged to the console.
   • Untested, but what's the worst that can possibly happen?

Autopelago 0.7.2

⚠️ UPGRADE NOTE

0.7.* is incompatible with 0.6.0 and all other earlier versions. Using a 0.7.* game client requires a multiworld generated using a 0.7.* apworld.

The 0.7.2 client CAN be used for a multiworld generated for 0.7.0 or 0.7.1. The .apworld file has not changed since 0.7.0 and is provided here just for convenience.

Changes since 0.7.0

1. Possibly fixed a crash that could be triggered by as-yet-unknown circumstances.
2. Handle multiworlds where one or more of the games gives multiple different names to a single item or location.

Other changes since 0.6.0

1. I've got a grown-up code signing certificate for grown-ups now, so Windows Defender might stop trying so hard to defend you from this. Unproven: you may still run into some stuff (especially from Windows SmartScreen).
2. #108: Upon reconnecting, the rat will now immediately return to where it previously was.
3. #109: If we fail to read your last settings from the lastSettings.json file, then we'll actually log the error (unless the "error" is that this is your first time running the application).
4. #52: New YAML option to choose to generate only a subset of the game that stops at either the Secret Cache or the Captured Goldfish instead of going all the way.
   • As part of this, the Lockheed SR-71 Blackbird (formerly needed to get to "Moon, The") is no longer special. Instead, "Snakes on a Planet" is now the final location so that it's more consistent with how the other victory locations work.
5. #111: Errors that take you to the scary-looking error screen will now also be logged to the console.
   • Untested, but what's the worst that can possibly happen?

Autopelago 0.7.1

⚠️ UPGRADE NOTE

0.7.* is incompatible with 0.6.0 and all other earlier versions. Using a 0.7.* game client requires a multiworld generated using a 0.7.* apworld.

The 0.7.1 client CAN be used for a multiworld generated for 0.7.0. The .apworld file has not changed since 0.7.0 and is provided here just for convenience.

Changes since 0.7.0

1. Possibly fixed a crash that could be triggered by as-yet-unknown circumstances.

Other changes since 0.6.0

1. I've got a grown-up code signing certificate for grown-ups now, so Windows Defender might stop trying so hard to defend you from this. Unproven: you may still run into some stuff (especially from Windows SmartScreen).
2. #108: Upon reconnecting, the rat will now immediately return to where it previously was.
3. #109: If we fail to read your last settings from the lastSettings.json file, then we'll actually log the error (unless the "error" is that this is your first time running the application).
4. #52: New YAML option to choose to generate only a subset of the game that stops at either the Secret Cache or the Captured Goldfish instead of going all the way.
   • As part of this, the Lockheed SR-71 Blackbird (formerly needed to get to "Moon, The") is no longer special. Instead, "Snakes on a Planet" is now the final location so that it's more consistent with how the other victory locations work.
5. #111: Errors that take you to the scary-looking error screen will now also be logged to the console.
   • Untested, but what's the worst that can possibly happen?

Autopelago 0.7.0

⚠️ UPGRADE NOTE

Incompatible with all previous versions. Using the 0.7.0 game client requires a multiworld generated using the 0.7.0 apworld.

Changes since 0.6.0

1. I've got a grown-up code signing certificate for grown-ups now, so Windows Defender might stop trying so hard to defend you from this. Unproven: you may still run into some stuff (especially from Windows SmartScreen).
2. #108: Upon reconnecting, the rat will now immediately return to where it previously was.
3. #109: If we fail to read your last settings from the lastSettings.json file, then we'll actually log the error (unless the "error" is that this is your first time running the application).
4. #52: New YAML option to choose to generate only a subset of the game that stops at either the Secret Cache or the Captured Goldfish instead of going all the way.
   • As part of this, the Lockheed SR-71 Blackbird (formerly needed to get to "Moon, The") is no longer special. Instead, "Snakes on a Planet" is now the final location so that it's more consistent with how the other victory locations work.
5. #111: Errors that take you to the scary-looking error screen will now also be logged to the console.
   • Untested, but what's the worst that can possibly happen?

Autopelago 0.6.0

⚠️ UPGRADE NOTE

Incompatible with all previous versions. Using the 0.6.0 game client requires a multiworld generated using the 0.6.0 apworld.

Changes since 0.5.0

1. Added some command-line flags to let you turn off various rendering modes, in case your graphics driver is unreliable. These should only be used if you run into issues. Run with --help to see what you can disable.
2. Move the "Back to Main Menu" button to a different place in the main game screen. In its old location, there was a little buffer around it where you could click on it to replace the world map with a completely empty tab.
3. #67: Tweak the behavior so that the game can keep going after goal completion. The rat will still make a beeline for the goal as soon as all the requirements are satisfied.
4. Add an earlier and more explicit check for compatibility. If the server's .apworld doesn't match, a very specific error message will explain this to you.
5. Perhaps improved startup time (unproven).

Autopelago 0.5.1

This is a quick fix to hopefully help someone whose system appears to support Vulkan, but which crashes at startup for Vulkan-sounding reasons. If you're on 0.5.0 and this doesn't sound like your situation, then you have little to no reason to update to this.

Compatible with Autopelago 0.5.0.

The fix here was to add command-line flags to let you disable any of the various graphics APIs that the Avalonia project chose not to enable by default (probably because of this), as well as a --no-gpu nuclear option just in case nothing else works.

Pass the --no-vulkan argument, for example, to disable Vulkan-based GPU acceleration. Run with --help for a full list of options.

Autopelago 0.5.0

⚠️ UPGRADE NOTE

Incompatible with all previous versions. Using the 0.5.0 game client requires a multiworld generated using the 0.5.0 apworld.

Changes since 0.4.0

1. Smart / Conspiratorial auras shouldn't move the rat towards already-checked locations anymore (#100).
2. Gigantic performance improvements to rendering, across-the-board (#104, in part).
3. Replaced the "Forklift Driver Certification" filler item, since a progression item already had the same idea (#102).
4. Lower the minimum width / height of the window, for the sake of HiDPI displays like the one that we tested this on (#101).
5. Allow customizing the player token. You can have one of three icons, and in any color (#50).
6. Remove the placeholder dots from the game map that would still show through some of the landmark icons. These were originally there to help show me where the landmarks should go, but they haven't been needed for months (#106).
7. Significantly rewrite the path finding code (again) after a bug report sent me on a fruitless search through some of the most complicated code in this application. I never found it, and it's still among the most complicated (though the rendering performance optimization is getting there now), but at least the code is simpler now... maybe I accidentally fixed it?
8. Slightly nerf the "Energized" buff: during a single round, it can now only activate a limited amount of times. Previously, an extremely long move with very high NRG would let the rat basically run across the entire map in a single round.
9. Probably(*) fix some reported issues where the Pause button would stop all the animations, but the rat would still dutifully go around the map doing its checks.
   • *I can say confidently that I made at least one change that fixed at least one potential cause of this issue. I am less confident that it's impossible for this to happen now in a different way.
10. Start bringing in game-specific Easter egg item ideas that @skidznet has vetted.

Autopelago 0.5.0-beta.1

Changes since 0.4.0

1. Smart / Conspiratorial auras shouldn't move the rat towards already-checked locations anymore (#100)
2. Gigantic performance improvements to rendering, across-the-board.