Closed GoogleCodeExporter closed 9 years ago
Just a note that the time when you get max stamina is your local time, not the
server
time. So I guess when you post the issue, it was near 2pm at your place?
Original comment by ipodsee...@gmail.com
on 3 Mar 2009 at 6:24
No, it was in the morning, around 11 AM. If it is based off of local time why
is it
written in the exact same format as Server Time? It's confusing that way
because due
to the time zone differences, I've taken to playing FS in Server Time, rather
than
Local Time. That is to say, when I speak in my guild chat, talk on private
messages,
etc I try to keep it ST, so that I don't run into timezone problems. If it is
based
on local time, then I guess it's accurate, though I wish it would be based off
of ST
so as to avoid potential confusion. Such as knowing when your hunt is and being
prepared for it. I looked up at it, my first reaction was to look down at the ST
because I knew 14:00 hrs in ST was 8:00 LT, and I would be on my way to class
then,
so I made plans to try and burn a little stamina to push the time back. Had I
known
it was LT, and that I would be home by then, I might not have bothered. That
was last
night, and even then I had some inkling that something was off, but it wasn't
until I
saw my stam this morning that I knew what it was. Make sense?
Original comment by sbrown...@sbcglobal.net
on 3 Mar 2009 at 7:56
Somehow, you are the very first player who complains about this. Actually I
find it
very convenient in local time, so I don't have to do any conversion as you do
:). To
tell the truth, the only thing I need about time in FS is the max stamina time
(AH is
in time left, so it does not count) ... still not see why do you need those
other
times. Maybe you want some time to get used to FSHelper (sorry if you are
already
using for a long time)?
Original comment by ipodsee...@gmail.com
on 3 Mar 2009 at 8:50
So how do you coordinate a de-level hit with your guild if you only use LT? It's
possible if everyone knows what time zone you live in and can compensate, but
not
everyone does or can. That's one example of where ST is helpful in FS. Or say
you
need to discuss something with a guildie in real time(ish). Saying I'll be on @
xyz
LT doesn't do much good, I'd need to tell him in ST. I've gotten used to
converting
everything to ST when I play HCS. I look at logs (especially in the guild chat)
to
see if the request for buffs is current or an hour ago. And so on, and so on.
Can you
show me where (in the documentation) it says the Max Stam time will be set to
LT?
Because what it comes down to is how are we supposed to know that the time
shown is
LT and not ST, and get confused? Does it say it somewhere where a new user to
the
script could find it easily? I've been using the script practically from day 1,
though I honestly don't know if it was the first day or the third.. but it was
very
new when I started using it, and I haven't seen any comments anywhere that say
it's
based on LT.
Original comment by sbrown...@sbcglobal.net
on 3 Mar 2009 at 9:09
Documentation? What documentation?
Obviously it is local time. This is not a defect. It was supposed to be local
time
fro the beginning - I don't even know what the server time is (usually). I only
care
about when (in "real" time, local time that is) my stamina will fill, so I can
time
when I will play. You are obviously asking for a new thing, showing Max Stam At
in
server time. I've changed the relevant fields for this issue.
Original comment by GSchizas
on 4 Mar 2009 at 10:53
Original comment by GSchizas
on 4 Mar 2009 at 10:53
In my guild where we have members from all around the world we time bounties
etc by
making messages like this: 'In 24 hours I will put up xxx on the bounty board.
Please
let me know if you can/will participate or when a more convenient time would
be.'
I would certainly prefer the function of max stam to remain in local time.
Virtually yours,
Zennaro
Original comment by zennaro...@gmail.com
on 15 Jun 2009 at 10:19
I think max stam calc should be local time only.
Original comment by Brent.Me...@gmail.com
on 27 Sep 2009 at 9:42
closing multiple issues due to in-activity / not going to implement / no longer
relevant / etc.
Original comment by Vong.H...@gmail.com
on 10 Jan 2012 at 7:05
Original issue reported on code.google.com by
sbrown...@sbcglobal.net
on 3 Mar 2009 at 5:36