Sunday, April 27, 2014

Announcing ADOM 1.2.0 Prerelease 22...

Hi everyone!

I'm happy to announce the release of ADOM 1.2.0p22. A mere eight days after the (sadly quite unstable) release of ADOM 1.2.0p21 this prerelease hopefully will prove to be a lot more stable and enjoyable.

This prerelease is mostly "just" a bugfix release but we are pretty proud of the huge amount of bugs we managed to tackle within just eight days - as can be seen on the change log. Some of the most important fixes include:

A few minor adjustments also have been added, the most important probably being:

While none of these are spectacular all in all prerelease 22 contains a total of 89 issues have been tackled.

And now go downloading the latest version of ADOM and have fun playing it! And let us know what you think about it!


  1. Ah! I’ve completely forgotten about ADOM for quite a while.
    Now I’m a bit disoriented. I’m able to access Ancardia with one of my old mail addresses and can access the game however I’m not seeing any newsletter mails since back in 2013-10. Mind helping me change my mail at Ancardia to my new one and tell me how I sign back up for these newsletters again?

    Also is there some short summary of all the changes made since you started development again?

    Can’t wait to see what these “graph-eecs” are all about.

    All the best to my big developer hero.

  2. It appears that the game brakes itself sometimes when one is going downstairs on The Infinite Dungeons. It happened to me twice, with the message: "Computer is not reading adom.exe". It cannot be loaded, the character is gone forever (it was more frequent in the prerelease 21, but we had the opportunity to load the game there). Yet it does not happen when one is playing with the classic ASCII. The only safe solution for now is to save before going to The Infinite Dungeons, switch to ASCII, and switch it back in the wilderness.

    It did never happen to me in the past, so I guess it is the prerelease 22 thing. It could not be an accident because it happens when I am going ">", like in the 21 (where the crash information came from ADOM and where I could load the game).