Release Candidate

From PMDOWiki
Revision as of 15:15, 1 May 2024 by IDK (talk | contribs) (reporting issues)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Starting with v0.7.18, PMDO has the option to unlock the full game for playtesting.


This version of the game has all dungeons fully featured. You will be able to clear all main-path dungeons and see the credits roll. However, NPCs and questlines are still very much incomplete. Additionally, postgame dungeons that unlock after completing the credits are incomplete. This option exists for people who are not interested in the story and want to help improve the final release of PMDO by providing their playtest data and impressions.


If you would like to help with playtesting the full game, please follow these guidelines:

Before Starting

It is recommended that you start the game on a BRAND NEW SAVE FILE.Your existing file is saved in the SAVE/ directory, which you can copy to a safe location before deleting it.

Additionally, it is recommended that you CLEAR ALL REPLAYS before starting, to make it easier to send your entire adventure when finished. You can back up your existing replays in REPLAY/ before deleting them.

When playtesting the Release candidate, make sure you have all Mods turned OFF to test the game with its intended balance.

Unlocking

When you begin the game, repeatedly interact with the sign until it asks you to unlock the half-finished story.

Say yes, and the full game is unlocked! Play the game as you would normally, and once you reach the final staff roll or get bored, zip up your REPLAYS/ and send them to Audino.

You can reach Audino through Discord.

Reporting Issues

  • If you encounter an issue while playing PMDO, please send a bug report in the Discord.
  • Be sure to provide a version number, and any mods you used.
  • If the issue is not tied directly to a mod, try to reproduce it with as few mods as possible to help reduce guesswork.
  • Errors that use mods outside of the prepackaged list will be considered lower priority or moved out as an issue of that particular mod.
  • You may need to send additional information depending on the type of issue you encounter.

Save Corruption/Softlock

  • The save file is unusable, either on load or because you're stuck.
  • If this was achieved in dungeon, send the quicksave.
  • If this occurred in hub mode, send the SAVE file and LOG file.
  • These are HIGH PRIORITY due to potential for lost progress.

Desyncs

  • When playing a replay or reloading a quicksave, you get errors or desync.
  • Send the replay or quicksave that desynced.
  • If you were recording the original gameplay via screen capture, send that as well for an accurate comparison.
  • Desyncs are HIGH PRIORITY due to their capability to cause a lost run.

Game Crash

  • Send the LOG file. Also provide a description of what you were doing to cause it.
  • Send the SAVE file.
  • If this was achieved in dungeon, send the quicksave.

Error Message

  • Send the replay of the game run where the error occurred.
  • If it happened in hub mode, send the SAVE file before you save such that the save file is closest to the point of error.

Non-Erroring Issue

  • Things not behaving as they should but do not error, such as being poisoned by your own corrosion, dungeons not unlocking, item rewards not distributing, NPCs not appearing.
  • Send Replay or quicksave.

Spelling/Grammar Mistakes

  • Screenshot

Performance Issues

  • FPS drops, noticeably large amounts of lag that break immersion.
  • Press F1 to turn on FPS counter.
  • Send OS information?