FAangband 2.0.0

[swim]

Confirmed the crash is gone in my previous save. I'm going to start one from scratch now to test that too.

[Cuboideb]

Well done! I'm updating the android port.

[backwardsEric]

The latest builds should not have the crash on moving house, thanks to backwardsEric for finding and fixing the bug.

Cuboideb deserves most of the credit for the question above about the compiler; that's what triggered looking for side effects from using --enable-release. Without that, I probably would have read the assert(cave_find(...)) line a dozen more times and still not have realized there was a problem.

[Nick]

Cuboideb deserves most of the credit for the question above about the compiler; that's what triggered looking for side effects from using --enable-release. Without that, I probably would have read the assert(cave_find(...)) line a dozen more times and still not have realized there was a problem.

Let's just say we're all very clever except me

[tg122]

Thanks everybody!

[swim]

So far so good. Thanks everybody. I am really really enjoying this game.

[tg122]

Hey Nick, I'm not sure if this is a bug or not but I've noticed that rings and amulets seem to be auto ignored as soon as I walk directly over them, even before I have identified them. I just started a brand new character, and I saw a ring lying on the ground in the wilderness. As soon as I walked to it, it said Ring of Utility <ignored> then disappeared before I even had a chance to look at it, but I still hadn't identified any runes identified yet since the character was new. I also don't have the option to know all runes turned on. I remember a similar thing happened with an amulet the other day.

[Nick]

Hey Nick, I'm not sure if this is a bug or not but I've noticed that rings and amulets seem to be auto ignored as soon as I walk directly over them, even before I have identified them. I just started a brand new character, and I saw a ring lying on the ground in the wilderness. As soon as I walked to it, it said Ring of Utility <ignored> then disappeared before I even had a chance to look at it, but I still hadn't identified any runes identified yet since the character was new. I also don't have the option to know all runes turned on. I remember a similar thing happened with an amulet the other day.

Thanks for the report. This has been an issue for a bit; I thought it was fixed, but apparently not.

[Ingwe Ingweron]

Maybe ask Pav to update the Variants page so that 2.0.0 shows as the current version and that it links to the right place to download.

[Ingwe Ingweron]

average damage/round on weapons information does not update when @ wears jewelry (combat rings, physical prowess rings, etc.). How does one choose what to wield without accurate damage/round information?

[Nick]

Maybe ask Pav to update the Variants page so that 2.0.0 shows as the current version and that it links to the right place to download.

Done - I can edit those details.

average damage/round on weapons information does not update when @ wears jewelry (combat rings, physical prowess rings, etc.). How does one choose what to wield without accurate damage/round information?

That's odd. Noted.

[Nick]

Hey Nick, I'm not sure if this is a bug or not but I've noticed that rings and amulets seem to be auto ignored as soon as I walk directly over them, even before I have identified them. I just started a brand new character, and I saw a ring lying on the ground in the wilderness. As soon as I walked to it, it said Ring of Utility <ignored> then disappeared before I even had a chance to look at it, but I still hadn't identified any runes identified yet since the character was new. I also don't have the option to know all runes turned on. I remember a similar thing happened with an amulet the other day.

The latest builds have a change by backwardsEric that may fix this problem - let me know what you see.

[EugeneLesnov]

The last few days I have been trying to implement a weather system for wilderness like in TomeNet. Meh, this requires a deeper knowledge of C than I have =D

[Pete Mack]

Before you commit to C, you need to decide how it works. Just a random state on each map area? Fronts moving from west to east? Once you know your algorithm, the language shouldn't matter.

[EugeneLesnov]

Once you know your algorithm, the language shouldn't matter.

In perfect world - agree. But my everyday work is Java/Spring Boot. And it is quite difficult to delve into such a large project as FAangband (for me, meh). It's a completely different world for someone with a different specialization. Therefore, to implement some features, it takes more time than a person needs, who, for example, writes C code every day.