FAangband 0.3.6

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Seany C
    replied
    Quick notes on 0.3.6 (from char dump):

    Mostly a little bit easier so far - more useful egos. speed on DSMs makes them worthwhile again and lots of Rods of Perception are ace.
    Not sure from a couple of plays if they're unbalancing yet but *if* you were happy with the difficulty level for 0.3.5 and before, you might want to do something (not sure what exactly) to make the game a bit tougher again...

    Notable findings:
    * Lots more high-value items turning up around Anf 58 with autoscum on - monsters don't seem that much different from 0.3.5;
    * Shields of Preservation - lovely but almost over-powered;
    * Boots of Elvenkind - seem a lot more common than before - or just the RNG being nice?
    * Haven't tried archery enough to appreciate the differences - for non-Rangers, probably more relevant for non-thralls;
    * Ds are *nasty* - I thought I was safe with a Storm D and Taratol until it started to breathe Storm on me...
    * Thralls without Unlight (or very quick finds of stealth items) are still mega-difficult (as in previous versions) - Rogues/Necros/Assassins are way easier than other classes as thralls for that reason...
    * I've lost 29 thralls to Will'O'the'Wisps - nothing else close to double figures yet.

    Leave a comment:


  • Mr.Peanut
    replied
    I patiently await the next DS port. I only play roguelikes on portables so it is great to have another flavour available. It is very hard to port a roguelike to the DS. The screens are not quite big enough for a standard terminal; designing a good interface is a real challenge.

    Your approach of contextual touch buttons is good, as are the keyboard and zoom toggles. However, something really needs to be done to improve diagonal movement. Most roguelikes on the DS force the use of touchpad for diagonal movement. I personally hate using the touchpad for movement because it is not always accurate(especially in Faangband when not zoomed in) and causes a handcramping awkward style of continually swapping between stylus and and button usage. The stylus also obscures the map screen.

    By far the best solution to this problem was presented by Wosret on the first attempted NetHack port; a diagonal movement toggle button. When the button is held only diagonal movement is possible i.e. cardinal directions disabled on d-pad. I suggest that the right shoulder button be used as the diagonal toggle button. The zoom toggle could be changed to a combination of holding the right-shoulder button and pressing one of the four (A,B,X,Y) buttons.

    Another great improvement would be the option of a third zoom level somewhere in between the two present levels. Finally, the keys on the virtual keyboard should show some indication of which is being pressed. I know I have seen this feature before for this exact keyboard.

    Keep up the great work.

    Leave a comment:


  • Nick
    replied
    Originally posted by tigen
    I had the same compile problem I had in Oanband.
    Yeah, this should be fixed in the next version - probably by a move to the new V build system.

    I don't know if this is considered a problem, but starting a character in a "small" town can be a little frustrating. You can't buy spellbooks, and that general store place drives hard bargains. I couldn't get enough arrows.
    As buzzkill said, moving to a big town is the best plan. For the low/medium difficulty races, either Belegost or Khazad-Dum are the easiest to get to (Dwarves start in Belegost; any of the other low/medium races can get there without going over difficulty level 6).

    The other thing that I found a bit strange is the wilderness difficulty arrangement. Depending on what you want to do, you easily end up in areas that are too hard or too easy. I'm not sure what you'd do about that though. It occurred to me that you could implement a system where the difficulty levels in the overworld scale up over time, representing a spreading of evil. But I can imagine problems with that too.
    This is deliberate. The four hard starting races (High-Elves, Grey-Elves, Druedain and Edain) either have native telepathy (Druedain) or start off with a good weapon. Starting location is as big a consideration when choosing a race as bonuses.

    The other thing is that (unlike in Z and its children), you should think of the FA wilderness as an integrated part of the playing world, rather than on overworld that you have to go through to get to the dungeons. In particular, there's a lot of nice gear to be found in wilderness (particularly above level 10), and the different wilderness types (Mountain, Plain, Forest etc) will be easier or harder depending on races(and to a lesser extent class).

    Originally posted by buzzkill
    FA is a hard variant. What always frustrated me (as a non-scummer) was starting in a town surrounded by high level wilderness.
    It is hard (to get started at least); I started playing this version last night, and went through about 8 characters in very short time.

    And if you're going to play hard starting races, don't think of it as scumming. Your hometown is in a really dangerous area - your first forays into it need to be cautious. This is not Vanilla, or even O. "Stairscumming" is just the sensible thing to do to stay alive.

    Leave a comment:


  • buzzkill
    replied
    Originally posted by tigen
    I don't know if this is considered a problem, but starting a character in a "small" town can be a little frustrating. You can't buy spellbooks, and that general store place drives hard bargains. I couldn't get enough arrows.
    You'll find a larger town soon enough, Belgost is the first likely candidate IIRC. The world map never changes so once you locate it, you'll always kinda know where it is. You can move your home to a new (larger) town by pressing ctrl-h or $ while in the new town. I'm not too sure about those keystrokes. It's been a while.

    FA is a hard variant. What always frustrated me (as a non-scummer) was starting in a town surrounded by high level wilderness.

    Leave a comment:


  • Pete Mack
    replied
    try a lost soul character. It's either over so fast it's painless, or you get to cl 20 in no time. And you start with ESP and a little detection...

    Leave a comment:


  • tigen
    replied
    I had the same compile problem I had in Oanband. I'm surprised I'm the only one who runs into this. Anyway my fix was to swap the order of OBJECTS nad LDFLAGS.

    (src/Makefile)
    @@ -17,7 +17,7 @@
    -I.

    faangband: $(OBJECTS)
    - $(CC) $(LDFLAGS) $(OBJECTS) $(LDADD) -o $@
    + $(CC) $(OBJECTS) $(LDFLAGS) $(LDADD) -o $@
    @printf "%10s %-20s\n" LINK $@


    Other notes from a relative FAAngband newbie:

    I don't know if this is considered a problem, but starting a character in a "small" town can be a little frustrating. You can't buy spellbooks, and that general store place drives hard bargains. I couldn't get enough arrows.

    The other thing that I found a bit strange is the wilderness difficulty arrangement. Depending on what you want to do, you easily end up in areas that are too hard or too easy. I'm not sure what you'd do about that though. It occurred to me that you could implement a system where the difficulty levels in the overworld scale up over time, representing a spreading of evil. But I can imagine problems with that too.

    Leave a comment:


  • Psi
    replied
    Originally posted by Seany C
    One minor glitch - it's still not possible to access slots '2' and '4' in the quiver (as in 0.3.4)...
    Unfortunately I don't know enough about how the inputs work to fix that. Sorry (I'd love it fixed too!).

    Leave a comment:


  • Nick
    replied
    Originally posted by Donald Jonker
    Strange bug - faangband crashed after exiting after a death. The death dump, and scoreboard were all successfully displayed.. I wouldn't have known the program crashed hadn't winXP told me so.
    It used to do this after every exit in windows - anyone else seen it this time?

    Leave a comment:


  • Donald Jonker
    replied
    Strange bug - faangband crashed after exiting after a death. The death dump, and scoreboard were all successfully displayed.. I wouldn't have known the program crashed hadn't winXP told me so.

    Leave a comment:


  • Donald Jonker
    replied
    Originally posted by buzzkill
    I can see a whole new line of attack for the complainer. He can mumble about town scumming and stat potions and too much junk being left behind by inconsiderate (dead) monsters.
    Of course you realize that this means war...

    Leave a comment:


  • buzzkill
    replied
    Originally posted by Nick
    Not yet - I'll have to pay him some attention for 040.
    I can see a whole new line of attack for the complainer. He can mumble about town scumming and stat potions and too much junk being left behind by inconsiderate (dead) monsters.

    Leave a comment:


  • Seany C
    replied
    Originally posted by Seany C
    One minor glitch - it's still not possible to access slots '2' and '4' in the quiver (as in 0.3.5)...
    (edit: might be 0.3.5 rather than 0.3.4)

    Leave a comment:


  • Seany C
    replied
    One minor glitch - it's still not possible to access slots '2' and '4' in the quiver (as in 0.3.4)...

    Leave a comment:


  • Nick
    replied
    Originally posted by Pete Mack
    BTW the new V makefile model is infinitely cleaner than what you are using. If you switch over, you will never have to maintain individual OS makefiles again (knock on wood.)
    I'm planning to look into all the Vanilla improvements for 0.4.0. Thanks for the feedback - much appreciated.

    Leave a comment:


  • Pete Mack
    replied
    OK, I got things to compile, sort of, using Makefile.osx-ppc (which really should be Makefile.osx-native.) Using Makefile.osx-ub, I get a weird link error:

    ld: library not found for -lcrt1.10.5.o

    Unfortunately, with the native compile there are massive missing symbols. The following files are missing from the object file list:
    ui.o
    z-files.o
    randname.o

    Additionally, the file osx/Angband.icns has been renamed FAAngband.icns

    EDIT:
    BTW the new V makefile model is infinitely cleaner than what you are using. If you switch over, you will never have to maintain individual OS makefiles again (knock on wood.)
    Last edited by Pete Mack; February 9, 2009, 09:11.

    Leave a comment:

Working...
😀
😂
🥰
😘
🤢
😎
😞
😡
👍
👎
☕