Identify by use
Collapse
X
-
Suppose you first learn a {blessed} weapon whose random ability is SI. If the next weapon lacks SI, surely it cannot be {blessed}? Just imagine coding to deal with that without implicit assumptions about the edit files.
Perhaps someone will come up with better hacks. I probably should have added "if it has a stealth bonus, learn the ego" but at the time that was too hackish even for me as an acknowledged zealot. I have since changed my mind.
Or you could just do it right, and assume the player knows the edit files.
I also discussed what I called "rune based" in rgra. Each object flag is a rune, and the player can see the runes on objects that are picked up. That's a radical change, but can be made consistent without reference to edit files. It kind of renders egos obsolete.Comment
-
Because of the code differences, I probably won't copy the V implementation, so I'm more concerned with getting straight how I want it to work at the moment. In particular, individual objects in FA now keep their flags etc with them, rather than having to appeal to object kind - which means that learning single properties of objects is a possibility.One for the Dark Lord on his dark throne
In the Land of Mordor where the Shadows lie.Comment
-
I'm not planning to remove ID completely; in particular the player will never learn an ego type unless a example has been ID'd at some point to set everseen to true.
Because of the code differences, I probably won't copy the V implementation, so I'm more concerned with getting straight how I want it to work at the moment. In particular, individual objects in FA now keep their flags etc with them, rather than having to appeal to object kind - which means that learning single properties of objects is a possibility.
I don't think there is much point in going half-way. Perhaps you should go with "learn any flag, notice the ego". The biggest difference is on weapons with a wis bonus and SI. There are a couple more ego separations you get for free, but overall I do not think it would be a big deal, assuming your ego list is similar to V.Comment
-
You still have not addressed the issue that you ID a blessed weapon with SI and a *slay undead* also with SI. Unless you are presuming that the ID spell spits out edit file info, rather than object info, how do you model that the player can suddenly tell that SI is part of the definition of {*slay undead*}, but not part of the definition of {blessed}? If you can't model it, it is hard to code it.
Code:A priestly weapon that increases wisdom and bears a hidden power.
assuming your ego list is similar to V.One for the Dark Lord on his dark throne
In the Land of Mordor where the Shadows lie.Comment
-
I'm seeing it largely as a housekeeping thing - if you have something that's obviously a Gondolin weapon, then it gets labelled as such. If that's what you meant - I wasn't quite sureOne for the Dark Lord on his dark throne
In the Land of Mordor where the Shadows lie.Comment
-
Another way would be that they learn, regardless of whether it is correct or not. So in your boots example, a player who has seen Slow Descent but not Stability, and learns FF, would identify the boots as Slow Descent. Maybe this could be a tentative identification (like in UnAngband). Then when the player learns RNexus, the boots revert to unidentified ego.Comment
-
There is also the question of how to fix V. Things that are obviously gondolin when you wield them do not currently get marked until you learn a slay.
In V, with the current egos, I think that the following is enough for me to personally figure out any ego, although it is possible I am overlooking something.
(1) learn an ego when you learn any slay or brand
(2) learn an ego when you learn any two flags that affect the player (e.g. not IGNORE_ACID)
The only time a single flag doesn't determine things that comes to mind is for the +int and +str *SLAY egos, and you get the +str differentiated as soon as you have a chance to notice regen. Why not just say "learn any flag, notice the ego", the way that learning any effect learns awareness of a flavor?
When I coded the current scheme, I was worried about learning FF on boots or seeing blessed with SI on a weapon, but given the current V paradigm that when you have learned all flags you get the ego, those cases are already covered so there is no point worrying about them.Comment
-
I'm planning to have ID-by-use in some form in 1.1. I'll probably base it on the V system, but there are complications because there's a lot more randomness of egos in FA.
In V, with the current egos, I think that the following is enough for me to personally figure out any ego, although it is possible I am overlooking something.
(1) learn an ego when you learn any slay or brand
(2) learn an ego when you learn any two flags that affect the player (e.g. not IGNORE_ACID)One for the Dark Lord on his dark throne
In the Land of Mordor where the Shadows lie.Comment
-
Comment
-
Comment
-
It's not obvious until you learn the second flag. Most egos are obvious after a single flag.
The question is whether to require learning 2 flags to notice an ego, which is annoying for wisdom or beauty or elvenkind, or to allow noticing with a single flag which e.g. gives away int vs magi on wield.Comment
-
Identify by use isn't really my style of play, since I've been conditioned since Moria not to wield anything I haven't spent an identify scroll on... and I don't play Ironman. However I just noticed that the following "hint" messages seem to be out of order when changing weapons:
You were wielding The Lucern Hammer 'Turmil' (2d5) (+10,+6) [+8] (+4) (s).
It coats itself in ice!
It glows!
You are wielding a Rapier (1d6) {special} (a).
You do not feel comfortable with your weapon.
"It" above appears to be referring to the former weapon, not the one just wielded. I think these hints should appear after the "You are wielding" message.Comment
-
Try it, you'll like it Just keep some remove curse scrolls handy. It's certainly not as big a deal as before and fun to watch items get slowly identified when you hit different monsters.Comment
Comment