[Announce] NPPAngband and NPPMoria 8.0.0 (Qt Port) released

[jevansau]

Is there a way to change the quiver ordering?
The default seems to be most valuable first, which is the opposite of what I want for the F command.

[nppangband]

Is there a way to change the quiver ordering?
The default seems to be most valuable first, which is the opposite of what I want for the F command.

Yes. Inscribe the arrows with "@#", with # being the slot you want to arrows to be in. It can be either a letter or a number.

[nppangband]

Crash when closing the map window.

This is fixed. Both the map window and the overhead window had the same issue.

[takkaria]

Yes. Many thanks. The funny thing (to me) is that the "broken" Qt code that locates the path to the binary I mentioned above would actually work if the directory structure was arranged like that.

So if I understand it correctly, it is just a slightly different directory structure? Is there anything more to it than that? Does it still have to be put into a .dmg file for others to use, or can it just get zipped up at that point?

There isn't anything more to it than that, I think, but I'm not an expert either!

DMG files are just what Macs tend to use instead of zips to distribute software. There's no point in putting an executable into a zip and then into a dmg - it just means you have to extract the app from two different containers instead of one.

[jevansau]

Hi,

I encountered a level - I think a pristine wilderness with a player ghost zombie challenge, where it would repeatedly crash. i didn't quite manage to figure out the cause, and unfortunately I forgot to take a copy before I found a way off the level. I did see some 'nothing' terrain types nearby, but it seemed that entering combat caused an immediate crash.
Probably a separate issue, but I get crashes when Windows is low on memory.

Enjoying the playstyle, but finding the new interface takes some time to get used to.

I also just had a crash when inscribing some ammunition with @0. I did have 2 stacks of the same ammunition in my quiver.

[nppangband]

Hi,

I encountered a level - I think a pristine wilderness with a player ghost zombie challenge, where it would repeatedly crash. i didn't quite manage to figure out the cause, and unfortunately I forgot to take a copy before I found a way off the level. I did see some 'nothing' terrain types nearby, but it seemed that entering combat caused an immediate crash.
Probably a separate issue, but I get crashes when Windows is low on memory.

Enjoying the playstyle, but finding the new interface takes some time to get used to.

I also just had a crash when inscribing some ammunition with @0. I did have 2 stacks of the same ammunition in my quiver.

Thank you. I found the cause of the 'nothing' terrain types yesterday, and you are correct that was causing the crash due to divide-by-zero errors. NPP 8.0.1 will be out shortly. I will look at ammo inscription first.

[nppangband]

I also just had a crash when inscribing some ammunition with @0. I did have 2 stacks of the same ammunition in my quiver.

I could not duplicate that crash, but I did find a way the game could conceivably crash while inscribing ammo. Let's hope that is it.

[jevansau]

Thanks for the quick response.

I seem to have had more issues with missile inscriptions becoming corrupt, and have a corrupt savefile - don't know if this is related or not. I got an error on saving the character and now the savefile won't load.

I'll attach it in case it helps you find the cause.

[nppangband]

Thanks for the quick response.

I seem to have had more issues with missile inscriptions becoming corrupt, and have a corrupt savefile - don't know if this is related or not. I got an error on saving the character and now the savefile won't load.

I'll attach it in case it helps you find the cause.

What area you inscribing the ammunition with that is causing the crash? Is it something you can duplicate?

I am sorry about the corrupted savefile. Did you say you got an error while saving the character? If so, what was it?

I looked at the savefile. Somewhere in the middle of reading all the store's inventory the remaining data in the file becomes all zeroes. This doesn't make a whole lot of sense at first glance but I will keep looking at it.

[jevansau]

Don't worry about the savefile. I'm grateful for a new variant to play.

I had originally inscribed some ammunition in the quiver with @0. This went smoothly until I had used all the inscribed ammunition. At this point, the next ammunition in the stack seemed to gain an odd and changing inscription, so I'd think maybe a bad pointer.
In the attached corrupted savefile, I had stored the ammunition with the bad inscription in the home. On reflection this was a poor choice.

[nppangband]

Don't worry about the savefile. I'm grateful for a new variant to play.

I had originally inscribed some ammunition in the quiver with @0. This went smoothly until I had used all the inscribed ammunition. At this point, the next ammunition in the stack seemed to gain an odd and changing inscription, so I'd think maybe a bad pointer.
In the attached corrupted savefile, I had stored the ammunition with the bad inscription in the home. On reflection this was a poor choice.

What most likely happened is the inscription got overwritten then the string may not have been properly terminated in the savefile, and so it read the rest of the savefile as the inscription for that object in your home.

I just uploaded a new version. It should take care of the crashes with inscriptions. I don't know if it would cause a memory leak, but it could have corrupted the inscription string. (Technical explanation: C++/Qt has a standard library command "firstIndex" that returns the position of a specified character in a string. If the character isn't found, then it returns "-1". I found several places in the quiver sorting code where it did not check if the value was in bounds before deleting a character. Also, there was some code that read the next character after that index, without first checking the next character was in bounds. Either of those could definitely cause a crash, and possibly a memory leak. We will see if that fixes it).

[nppangband]

There isn't anything more to it than that, I think, but I'm not an expert either!

DMG files are just what Macs tend to use instead of zips to distribute software. There's no point in putting an executable into a zip and then into a dmg - it just means you have to extract the app from two different containers instead of one.

I gave it a shot, but it is does not work. Who makes that folder for Angband? Is it Nick?

[Nick]

I gave it a shot, but it is does not work. Who makes that folder for Angband? Is it Nick?

In a sense, but more precisely it's Makefile.osx and its author. If you read through the comments and commands below

# Installation.

it actually gives a pretty good description. Notice that the making of the .dmg is under the heading

# In the unlikely event that tar+zip isn't enough...

- an event which is now the norm

[bio_hazard]

Note- OSX- I just tried to play again after properly saving (no crash this time), and again, I get the limits.txt error. To summarize- it seems like the application can find /lib only the first time it is opened, and fails on subsequent launches.

If it matters, when trying to open, it defaults to root.

e: sorry- this belongs in the 8.0.1 thread