Few hours ago, DevilutionX package was updated.
Curiously, I never had an occasion to play Diablo. So, I decided to visit DevilutionX Github page and check for more informations or screenshots.
Unlike the package information, the readme there mentioned that you can use files from GoG or Battle.net versions. You can even directly extract mpq files from GoG installer.
Also and more interesting the readme says that the shareware version is playable. In ‘How to install’ section, I was even able to freely download the data file spawn.mpq.
The shareware version is, of course, limited but it gives you a good idea of the gameplay before spending 9 € on GoG for full game and Hellfire expansion.
DevilutionX launch script is checking for the full version data file and allows to the data folder if it doesn’t find it. That was nice and allowed me to drop the downloaded file there.
Unfortunately, it checks only for the full version and when I clicked on the menu entry, I was kicked out.
So, once the file copied, I had to start the game from terminal to bypass the script. I saw later that clicking on DevilutionX binary also works but the most convenient is to use Quicklaunch.
It would be nice to make the launch script also check for the shareware version and, to add the information to get spawn.mpq to the package description.
I tried to open an issue for this on Haikuports but it never posted it. 
2 Likes
The script was made before I started updating the package myself so I haven’t checked.
So… good catch! I’ll be looking into it 
Edit: Done! The package should be updated soon-ish
Also, as somebody who’s been playing Diablo I since 25+ years ago, the Hellfire expansion is just a big meme, it might ruin the game’s overall atmosphere for you 
(its final boss goes on a rant about Aerosmith tickets when the battle starts, just to make a quick example of how stupid it is)
(Never melee the yellow glowing zombies btw)
2 Likes
If you subscribe to GOG you will soon get a reduced price for Diablo for 1,99 Euro.
2 Likes
Good! My CD-ROM edition cost me about that at the thrift store where I found it and some other games mixed in with audio CDs. Unfortunately, it was the original 1.0 edition that if you opened a portal in front of a door, the door would become corrupted and unopenable.
Nice! I’d love me some Diablo… 
Unfortunately my fans are spinning up very quickly. The 8 llvmpipe threads are all fluctuate between 20-30% CPU usage.
I don’t remember fans kicking in with a previous DevilutionX version a few years back. Sadly, old recipes vor v1.2.0 don’t seem to build anymore, so I can’t check…
The newer versions might be more CPU-intensive than the older ones in general, it could also be that the fans got dirtier with time and less efficient?
Maybe it’s time to clean them up
Put the game on your wishlist and wait for promotion!
Usualy every few month it will go down up to 80% of the price!
Since the topic’s here, next version of the package (1.5.4-3) will “break” current installs, the config folder will move from ~/config/settings/diasurgical/devilution to ~/config/settings/devilutionx.
It’s a better path for the user but you will have to move data, config files and saves to the new folder if you got the game already set up.
Edit: running the script once will migrate the user data for you on current installs.
1 Like
Why not add an automatic migration?
If the old folder exists, but the new one doesn’t copy the config over.
If the new folder exists use it.
I don’t like piling scripts, the one already present is there because it was already there, that one will point out to people the fact the folder changed too, the install base is small, they can migrate it. Let’s not add scripts that will have to be removed later anyway.
Edit: edited the existing script with some commands to migrate existing installs if present as it was easy enough.
Setting some game resolutions (too high for your gear?) will crash game instantly. I guess it is a general problem with our SDL2 port.
1 Like