"quest" issues

Started by LociOiling

LociOiling Lv 1

What used to be "filters" and "conditions" and then became just "conditions" is now "quests".

This has created a few issues.

  1. When quests are disabled, the score appears as number such as "3809320-0".
[img_assist nid=2005039 title=Oddly formatted scores desc= link=node align=left width=488 height=640]



1a. The term "condition" is still used, inconsistent with "quest".
1b. Can a quest be disabled? (philosophical)

  1. In some cases,appears in red, yet some quests appear disabled.
[img_assist nid=2005041 title=Quests active, but not all enabled desc= link=node align=left width=488 height=640]


2a. The term "residue" is still being used in two spots, why not go with "segment" instead if we're trying to simplify?

  1. Even when there's no penalty, quests show in red with score of -0. So there's no way to complete the residue count quest.

3a. The residue count penalty is described as "3.2*nres^1, where nres is the number of residues". That's a good one. Possibly not all users are familar with the use of ^ here, and it's also a little ambiguous as to whether it represents exponentiation or bitwise OR.

[img_assist nid=2005042 title=Some quests have no end desc= link=node align=left width=488 height=640]

LociOiling Lv 1

On the devprev hotfix, 20180416-5eaeddec33-win_x86-devprev, the quest terminology has been removed, and we're back to "conditions". The formatting of the scores has been corrected, although on 1507b, I'm still seeing Residue IE and Residue Count as -0 instead of just 0.

Of course, some love minus zero, with no limits.

LociOiling Lv 1

Closing this one, 20180426-5042fb62a9-win_x86-devprev seems to have restored the conditions box to its previous state.