FAangband 1.2

[LostTemplar]

not when there are -more- messages pending,

that is why I use macros, with a lot of space in front of it, so it cleans all that stupid -more- first.

[Derakon]

As for how to create macros, I haven't played FA recently but I'd assume they're under the '=' options screen now. At least, that's where they are in Vanilla, and Vanilla and FA have been pillaging each other for quite some time.

Also they're keymaps instead of macros now. Functionally identical except that keymaps can only trigger when the game is waiting for your next in-game command (so e.g. not when there are -more- messages pending, or when you're looking at your inventory screen, etc.).

[LostTemplar]

@ is used in inscriptions (} key) e.g. @z1 on the stack of rods, then " z1. " in macro, so it fires a rod at nearest monster, same for ammo.

[imsabbel]

Is there any documentation about the changes to the inventory system, especially the quivers? I was trying to create macros, but the "@" key just gives me "Press ? for help", where it tells me to press @ for macros.

I am really rusty when it comes to macros, but I remember that i had some years ago that I could shot ammo from different quiver slot using different keys. And that you could get ammo to be put in specific slots by naming them in some way...
---
In a different matter, I realized that i cannot play any class without strong ID anymore - I wonder how I ever managed to stand ye old (Z)angband.

Also, the squelch system is fantastic.

[LostTemplar]

Btw we already have desperate adventurer, so esterling player may not be so bad, just remove crash.

[imsabbel]

There is timed autosave, but you need to set it - '=', 'x'.



This is a great bug - I had it seriously back in the 0.3.x series, but it only pops up occasionally now. The main cause has been not wiping the player from the grid-by-grid monster array. I'll try to track it down again.

Well, I realize there is autosafe... but I did not realize that options reset after making a new character - so it was disabled again after my first one was killed.

That "Easterling Player" bug occured after i fell down some trapdoor, i.e. no normal level change.

[Nick]

I have the same issue. I play on a laptop where I do use the top numeric keys to move around and every time I move using the top numberic keys, it moves twice. The same issue happens when I type a number in a store, or in the options menu. The movement delay is already at 0. Also, I'm using Windows XP. I'm pretty sure this was introduced in 1.27.

Thanks, and sorry I missed the original comment. I'll look into this one too. I think we're going to need a 1.2.8 before long; as well as the various bugs, LostTemplar has been doing some interesting stuff I may want to pull in.

[tg122]

I'm getting a weird input bug; when I use the keys at the top of the keyboard to type a number, it enters twice - for instance, if I try to buy 3 items at the store, it types in 33. This applies to moving around too, though I don't normally use those keys to move.

I have the same issue. I play on a laptop where I do use the top numeric keys to move around and every time I move using the top numberic keys, it moves twice. The same issue happens when I type a number in a store, or in the options menu. The movement delay is already at 0. Also, I'm using Windows XP. I'm pretty sure this was introduced in 1.27.

[Nick]

Had a rather funny crash right now (and then realized that there is no autosave. Bye Bye my ranger - he just found a bow of accuracy +12 +12 at lvl 10...)

There is timed autosave, but you need to set it - '=', 'x'.

He encoutnered a white @, which read "Easterling Player" in a cavern. After bumping into it, the game crashed hard...

This is a great bug - I had it seriously back in the 0.3.x series, but it only pops up occasionally now. The main cause has been not wiping the player from the grid-by-grid monster array. I'll try to track it down again.

[Nick]

The (M) for map or dungeon display, everything else is okay except for that map, it dosen't display the characters correctly, and looks like it is missing certain walls and is jumbled together to be hard to read the map, this could be a vista issue, V works fine for me though so I don't know what the difference is.

I think the issue is that I have played with the way the map is drawn - in particular, with the choice of what terrain to display. It seems to be a problem across all platforms. Thanks for pointing it out.

[imsabbel]

Well, I just downloaded it yesterday from the homepage.

Let me look...

The Zip says FAngband127

[LostTemplar]

He encoutnered a white @, which read "Easterling Player" in a cavern. After bumping into it, the game crashed hard...

Impressive bug. Was it 1.1.6 or 1.2.x version ?

[imsabbel]

Had a rather funny crash right now (and then realized that there is no autosave. Bye Bye my ranger - he just found a bow of accuracy +12 +12 at lvl 10...)

He encoutnered a white @, which read "Easterling Player" in a cavern. After bumping into it, the game crashed hard...

[Malak Darkhunter]

Which map?

There are ongoing font issues with Vista - particularly if you use the 8x13 font - but I will check and see if the pref file needs fixing.

The (M) for map or dungeon display, everything else is okay except for that map, it dosen't display the characters correctly, and looks like it is missing certain walls and is jumbled together to be hard to read the map, this could be a vista issue, V works fine for me though so I don't know what the difference is.

On a side note i disable font-win under pref files in all my windows compiles versions to get ascii characters to display correctly.

[Nick]

But I noticed something odd in the monster lore list in the latest FA version, and I am not sure if its intentional or not:

I am pretty sure that years ago, if you had a terminal set to monster recall, you got the info of the monster you were browsing in the lore list in that window.

Not, it does not, so you have to press return everytime to see the stats/etc of the monster.

Is this intentional, or would it be possible to change it back to the seamless style?

This is not intentional, and is probably a result of poor implementation by me of the latest Vanilla display code. I'll need to fix that.