I'll accept that I'm an outlier. I'm not really playing Angband much right now, so detailed testing isn't in the cards. I'll shut up about randart availability for a bit.
So what else should we revert?
Collapse
X
-
OK, going way back to the original intent of the thread, here is what I (in my humble and not necessarily correct opinion) think should be reverted:
(snip)
The other part of Angband that, personally, I have no idea where it is going is with the object list. I know it can't or won't be undone, but since Angband is an inventory management game, it makes such a difference in game balance. From reading feedback the forum it seems like objects and object generation are in the middle of a complete re-write. I haven't looked at it enough to know what is going on or to have an educated opinion of the quality of the changes. But I think whatever is going on there needs to be finished before Angband can be re-balanced. Changing that affects every part of the game.
I also think you are spot on about the help files and newbies. Angband is like any other volunteer project in that what motivates volunteers is "real" changes, and writing help is not sexy. Takk has had great plans for improving the help files since he took over (look at tickets #11-14 which are all extant), but he can't find anyone to do it. If I can ever stop obsessing with randarts and power ratings for long enough, I'd love to do it - but I'm no more motivated to do so than anyone else.
I don't understand your final query about the object list. Do you actually mean object.txt, or do you mean the object list display (']')? AFAIK neither is the subject of serious on-going work: Ewert has made changes to rarities of certain items to try and address the surfeit of wearables and the deficit of consumables (which is a lingering result of the anti-TMJ changes in 3.1.0). That's all - nothing more wholesale than addressing that one problem. (There are always other suggestions like the dragonhide shields, but none of them are wholesale rewrites either.)"Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
-
Someone needs to code a utility to generate each level of the dungeon in turn, kill all monsters on each level, and accumulate statistics. I wonder how hard that would be to do.Comment
-
I'm playing with randarts, and they definitely seem much less common. I'm playing slow and careful, waiting for CL 50 before finishing, and would have finished already otherwise. I've only seen 28 randarts, and I would have expected to see 2 or 3 times as many standarts in the same time with the same kills. Given the amount of time I have had with the Palantir, more likely 3x than 2x.
Someone needs to code a utility to generate each level of the dungeon in turn, kill all monsters on each level, and accumulate statistics. I wonder how hard that would be to do.
Interesting. In the old days (3.1.1) the randart rarity was very closely tied to standarts. I broke that in 3.1.2 to try and make it more closely tied to the randart's power - because we were getting some uber-randarts too common and some crappy ones too rare. But I seem to have ended up with an overall increase in rarity, which surprises me (because I don't play enough standart games).
Since the base object rarity hasn't changed, it must be the calculation of a_ptr->alloc_prob in randart.c: r2017 tweaks this slightly. If you are now drowning in randarts, let me know. (Don't forget that the recent change to drop levels will have reduced the likelihood of deep artifacts dropping, for both randarts and standarts.)"Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
-
Current NPP does this, at least until I put in the new Angband birth.c. It is a fairly simple thing to add.NPPAngband current home page: http://nppangband.bitshepherd.net/
Source code repository:
https://github.com/nppangband/NPPAngband_QT
Downloads:
https://app.box.com/s/1x7k65ghsmc31usmj329pb8415n1ux57Comment
-
NPPAngband current home page: http://nppangband.bitshepherd.net/
Source code repository:
https://github.com/nppangband/NPPAngband_QT
Downloads:
https://app.box.com/s/1x7k65ghsmc31usmj329pb8415n1ux57Comment
-
Since the base object rarity hasn't changed, it must be the calculation of a_ptr->alloc_prob in randart.c: r2017 tweaks this slightly. If you are now drowning in randarts, let me know. (Don't forget that the recent change to drop levels will have reduced the likelihood of deep artifacts dropping, for both randarts and standarts.)Comment
-
Here's what I recommend for the birth screen: replace the yellow explanatory text (e.g. "Your 'race' determines various intrinsic factors and bonuses") with the race description from birth.txt, possibly slightly truncated. Those descriptions are generally very useful for telling new players "Okay, this race is probably going to be pretty bad at spellcasting; maybe I should stick to a stronger race for now." or "hey look, this race has See Invisible, which should make dealing with those poltergeists a lot easier." Do the same for the class selection.
Honestly I don't think anything more is needed. Certainly the skills shouldn't be shown, since they're horribly opaque and even veterans don't know how they correspond to actual numbers in-game. They'll just add confusion.Comment
-
Hi Jeff - thanks for that - it was very informative. I like almost all of your suggestions - the only one I disagree with is the "Of Resistance" ego. I never find it until I've already got something better, so I would deepen Elvenkind first and then see if Resistance needed any changing.
I also think you are spot on about the help files and newbies. Angband is like any other volunteer project in that what motivates volunteers is "real" changes, and writing help is not sexy. Takk has had great plans for improving the help files since he took over (look at tickets #11-14 which are all extant), but he can't find anyone to do it. If I can ever stop obsessing with randarts and power ratings for long enough, I'd love to do it - but I'm no more motivated to do so than anyone else.
I think it would be a fairly simple thing to code. If I ever have time I will blaze the path.
I don't understand your final query about the object list. Do you actually mean object.txt, or do you mean the object list display (']')? AFAIK neither is the subject of serious on-going work: Ewert has made changes to rarities of certain items to try and address the surfeit of wearables and the deficit of consumables (which is a lingering result of the anti-TMJ changes in 3.1.0). That's all - nothing more wholesale than addressing that one problem. (There are always other suggestions like the dragonhide shields, but none of them are wholesale rewrites either.)
And as for "too late to go back now" comment, I was thinking of the Angband 3.0.8~9 and beyond object list, where having everything in the dungeon safe to try and is double-edged at worst, and you barely have to identify anything any more. I haven't given it a fair chance, and the grumpy old man in me is saying "it can't work".NPPAngband current home page: http://nppangband.bitshepherd.net/
Source code repository:
https://github.com/nppangband/NPPAngband_QT
Downloads:
https://app.box.com/s/1x7k65ghsmc31usmj329pb8415n1ux57Comment
-
And as for "too late to go back now" comment, I was thinking of the Angband 3.0.8~9 and beyond object list, where having everything in the dungeon safe to try and is double-edged at worst, and you barely have to identify anything any more. I haven't given it a fair chance, and the grumpy old man in me is saying "it can't work".
I tried to think of a reason to keep the bad items beyond just flavor, and I couldn't manage it. And I don't think the bad items added enough flavor to be worth keeping, compared to the increased fluidity of gameplay without them.Comment
-
I also think you are spot on about the help files and newbies. Angband is like any other volunteer project in that what motivates volunteers is "real" changes, and writing help is not sexy. Takk has had great plans for improving the help files since he took over (look at tickets #11-14 which are all extant), but he can't find anyone to do it. If I can ever stop obsessing with randarts and power ratings for long enough, I'd love to do it - but I'm no more motivated to do so than anyone else.Comment
-
Most of the nasty stuff in Sangband can be thrown for some potential use. And consuming them won't (instantly) kill you.a chunk of Bronze {These look tastier than they are. !E}
3 blank Parchments (Vellum) {No french novels please.}Comment
-
Please, please do this. The help files date from 3.0.8, and many from even earlier! Please just take a text editor and send me update ones, and I'll commit them. That would be a great start - and all the html and context-sensitive stuff can come later when someone wants to code for it."Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
-
@jeff: I'm not convinced the object stuff will ever be "finalised" - we've made some significant changes since 3.1.0 despite a clear dearth of consumables. When Ewert's changes (or whatever equivalent) are implemented, it'll be a bit better but not perfect. I see Angband as like one of those giant puzzles, where you push one bit and something else moves out of place over on the other side. We'll be forever trying to get them all neatly balanced without anything being out of kilter - but that's the fun part."Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
-
Please, please do this. The help files date from 3.0.8, and many from even earlier! Please just take a text editor and send me update ones, and I'll commit them. That would be a great start - and all the html and context-sensitive stuff can come later when someone wants to code for it.Comment
Comment