Quote:
Originally Posted by Kich
[You must be logged in to view images. Log in or Register.]
If the keywords weren't highlighted, then the way to initiate the conversation would have to be way more simple. Getting information out of some NPC's can come down to literally, phrasing a certain sentence perfectly with no alternative. It's annoying that some conversations can't be continued unless you figure out the whole sentence they want you to say. Keywords needs to be emphasized.
Particularly, in Kaladim trying to get the aviak chick talon quest, I mean obviously you can just hand them to him, but if you want to actually go through the whole conversation, you have to be extremely thorough in how you respond to him (I tried about 14 variations of the exact same sentence before I got through to him). And I'm sure many others.
I'd be fine if they removed the []'s so long as the conversations were such that, if you just said one of X keywords, it would follow through in that regard.
|
How easy it is to interact with an NPC comes down to how well the EVENT_SAY portion is written. If it's too hard to interact with an NPC, it means the if() is way too specific, and, that's the kind of thing that people don't make bug reports about.
if($text=~/i want to destroy the krag chicks/i || $text=~/I will destroy the krag chicks/i){
That means you have to say either one of those two sentences, to the letter. When I do EVENT_SAY, I try to put as much thought into making it as intuitive as possible for the player.
Here's a line from Weaponsmith Grugl in cabeast. The pikes are referred to numerous ways in quest text and item names. Footmans pike, footman's pike, footman pike, etc. Written like this, as long as someone spells footman and pike right, it doesn't matter if they tell him they want the footman'z motherfucking pike.
if(($text=~/footman/i) && ($text=~/pike/i)){
But don't think that it has anything to do with what's in brackets. Those are really just there to coach you along.