> I think the version with a background character is perhaps easier to see. > It might be worth combining them, though: > > FOO: [*****:::::] Agreed. > > [[time passes]] > The air grow suddenly thin as you hear yourself yell, "...xyzzyz do!" > Your arm drops to your side, limply, barely clutching the verge. > > Your health has been replinished! > You feel somewhat tired. > > Just what I need, MORE text to have to write before releasing the silly mud. *laugh* I don't even know that I'll be using a count down. It was merely a thought. > For me (who else would I be speaking for?): bars have very limited > applicability to things that need to be observed at a glance. In that > capacity, the code's better left simple. For things that don't beg a > visual aid, like timed events, it'd be better to give the player something > to look at, since they're not really involved in the action at that time. Well, the one problem is that if you do it for battle spells the spam gets MIGHTY thick, so a counting bar makes more sense. -Mathew -- +---------------------------------------------------------------+ | FAQ: http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html | | Archives: http://post.queensu.ca/listserv/wwwarch/circle.html | | Newbie List: http://groups.yahoo.com/group/circle-newbies/ | +---------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 06/25/03 PDT