Page 2 of 2
Re: Changes with this Armageddon
Posted: 29 Feb 2016 04:06
by Mersereau
If you don't like the narrator, don't grab any frying pans and start swinging them.
Re: Changes with this Armageddon
Posted: 29 Feb 2016 05:44
by Dhez
I think the reason why this 'Yikes!' stands out to individuals such as Rincon and I, although it is difficult to properly place one's finger on it, is something other than not liking the narrator, misinterpreting these words as if our characters would say them, or something of the sort.
I've given the matter some thought and believe the reason for it becoming disruptive to the immersive environment comes down to a switch between two different narrative modes. The invisible narrator suddenly becomes quite visible.
From my experience with the game's content, I find it easier to place myself within this fictional world when it is 'shown' to me and it subsequently prompts me for interaction rather than when it specifically 'tells' me what has happened, more so when this suddenly very much come alive narrating voice makes use of expressions contrasting greatly with a medieval fantasy setting.
Re: Changes with this Armageddon
Posted: 29 Feb 2016 06:20
by Mersereau
If it's that big a deal code a trigger to gag the entire statement and enter your own.
Re: Changes with this Armageddon
Posted: 29 Feb 2016 06:26
by Dhez
Mersereau wrote:If it's that big a deal code a trigger to gag the entire statement and enter your own.
It's not a big deal. Simply sharing perspectives on something other than the usual topics.
Re: Changes with this Armageddon
Posted: 29 Feb 2016 06:53
by Ody
Mersereau wrote:If it's that big a deal code a trigger to gag the entire statement and enter your own.
What about people on the people on the web cliant? We can't exactly do anything to fix that.
Re: Changes with this Armageddon
Posted: 29 Feb 2016 09:25
by trick
Ody wrote:Mersereau wrote:If it's that big a deal code a trigger to gag the entire statement and enter your own.
What about people on the people on the web cliant? We can't exactly do anything to fix that.
We can, we can...
gwc.output.replace() can do just that. However, Dhez raises a point. Obviously not an issue, but a point.