Fan Site: NEMO's Ark

[pinkgothic]

I'm going to agree with Shione's view, it should be accurate display or no display. And no one likes underhanded things,

Apologies for picking only this part of your post out, but it left me a little confused, so I wanted to address it!

I suspect you and I simply use the term 'underhanded' to mean something different, but just in case we're on the same page regarding that word, since you don't seem to be using the term jokingly or tongue-in-cheekly (like I've been using 'nervous' in this thread, or 'sneaky' in the FAQ) and instead appear quite vehement, please allow me to defend myself:

The way this feature works was neither intentionally hidden (secretive) nor intentionally misleading (dishonest) and most especially not done with malicious intent, which is my understanding of the term. It's very deliberately been precisely and openly described in the FAQ, which I had hoped was sufficiently accessible (I was unfortunately wrong, as we've established). I apologise if you've gotten a different impression, but I would hope my prompt reaction proves that my intentions were always to be transparent about the algorithm and the reasons behind it and that I am not trying to be mean (indeed, the feature's intent - anti-forgetfulness - is quite the opposite; see the discussion starting at this post in the Daily Dragon Fix thread over on the Dragon Cave forums).

If you mean the active counter being intentionally hidden (even in a world with perfect FAQ information accessible and known to the user) is underhanded, I would like to politely and gently disagree - to me, this isn't particularly different from any other implementation detail somewhere being hidden for gameplay reasons ("gameplay" in this case is "click every day", and the reasons are expanded on in the FAQ entry), such as how many views at which point in time makes a Dragon Cave dragon sick, or how many views at which point in time makes a Dragon Cave dragon mature.

However, those example features are not confusing and being confusing was definitely a problem here. Confusion is never desirable! So I try to fix it as soon as I can (and removing it was the best bet given the stated goals of the feature).

Can we agree? <3