Patch Notes Archive

Home » Updates » Patch Notes Feed » Dungeon Souls » Dungeon Souls v1.0.5.2 – Hotfix

Patch notes are imported from steam. There may be errors. This mostly exists so I can stay on top of them to update the features in our tags and scoring categories (which I do manually), but since many of you liked the idea of staying up to date with all the games in one place I'm working on making this data automated (right now I manually hit it every couple days) with better info and linking in with the game views.

There will be more data and proper atribution here (original author, steam link, original post date, etc) real soon, I promise. This is just like a technical test to see if they're coming in ok at all.

Dungeon Souls » Dungeon Souls v1.0.5.2 – Hotfix

Scope

Details of this section:
This section contains the scope of what patches were made in the current version.

This hotfix brings some fixes and feedback changes.

Bug Fixes & Feedback Changes

Details of this section:
This section contains the bug fixes that were applied in issues detected in the previous versions.

  • Fixed a bug where players would get teleported to quicksave portal when picking potions far away from “The Gate”.
  • Fixed a typo on Power Bow’s description.
  • Fixed a typo in “Lil’ Pumpkin”‘s recipe description.
  • Fixed a bug where ability descriptions would reset after quickloading.
  • Fixed a bug where pets would reset after quickloading.

Known Issues

  • In some systems (both operative system and hardware components), the game has severe lags spikes for brief periods of time. This usually has to do with malfunctioning input devices, but a fix is being developed. If this occurs to you, please send an email to laminastudios@gmail.com with the operative system you have and hardware, as well as any relevant information (the time you were playing at and what were you doing).
  • Currently, to some players, Steam functionalities are not working under Linux systems, as well as a few in-game functionalities (such as minimap). We are working into resolving this issue.