timestamp editor never functions

[EntranceJew]

in my server if i change the hour of a timestamp from "09" to "08" it does not ever function and says it is not a valid timestamp.
this frequently happens on my server when i specify "cst", as i do not know what timezone the bot believes my server is in.
2023-01-17T09:00:00-0600 afaik this should work,
from: 2023-01-17T09:00:00+00:00

(2023-01-17T08:00:00+00:00 did not work for me)

[Mayerch1]

You can set/get your current timezone with /timezone <arg> and /settings. (The upcoming menu will show your current timezone, when pressing the button, the bot will display your current local time)

For editing the ISO-Timestamps, the local timezone is not automatically applied, so you need to specify your timezone offset in the string.
For this reason, the bot is discouraging you from using this raw-edit (as it's often faster to just recreate the reminder).

I cannot reproduce your issue on my side.
Creating a reminder /remindme 1h test will set the following iso-timestamp
2023-01-17T13:46:20.108104+01:00 (timezone is set to CET)

If I want to send the reminder in the next 5 minutes instead, I can modify the timestamp to
2023-01-17T12:50:20.108104+01:00

It's important to keep the timezone offset, and still use the local time (12:50 is my local time for this case).
The new time is immediately in effect and displayed in the Reminder Info Box (next in 2 minutes).

Are you perhaps using an interval/repeating reminder?

[EntranceJew]

https://imgur.com/0ZXSg5B

no, none of what you said happens.

[Mayerch1]

Seems like you don't have a timezone set, therefore the bot is interpreting your inputs as UTC.
The bot does not support timezones when parsing your input.

You need to set the timezone using the slash-commands, for example /timezone CST6CDT

[EntranceJew]

why doesn't it populate the editor field with something that can be changed? why do i have to change the format for it to accept its own default value?

i would have never guessed that timezone name by myself, even as a technical user, and it isn't listed on the bot's setup instructions.

if the user i was creating a reminder for was not in the same timezone as the reminder i was creating on their behalf then i would have to sit down and figure out the offset for the server to their timezone. the bot ignoring "cst" and coming up with its own interpretation is less useful considering the path to correcting it is to just delete it and recreate it and not use the "edit" function it insists i use.

it is a miserable experience.