ID:2834375
 
Not a bug
BYOND Version:514
Operating System:Windows 11
Web Browser:Chrome 107.0.0.0
Applies to:Dream Seeker
Status: Not a bug

This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
Descriptive Problem Summary:
winset() seems to not work if called too early during client init.
tested in local with ss13 while "hosting" directly with dream seeker so it might be impacted by long load times.

Numbered Steps to Reproduce Problem:
1. Call winset to change map.zoom in client/new
2. Winget is called to verify what it is
3. Instead of the value set by winset, it's the skin's default.
4. Notably, this happens when said code runs before dreamseeker window is actually open, verified by the auxtools debugger.

Code Snippet (if applicable) to Reproduce Problem:
Can provide if necessary.

Expected Results:
winset zoom to be there

Actual Results:
zoom = 0, which is the skin's default.

Does the problem occur: Seems to be very time

When does the problem NOT occur? Waiting a few seconds to do said winset calls

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)

Unknown

Workarounds:
Spawn() for a small while.

Oh, notably, I'm winsetting with winset(client, null, "command=\".winset \"").
Wait, re-testing, might be something wrong with my winset.
disregard, winset with list2params(list("command" = str)) instead and it worked, going to assume I typo'd the \ and "'s or something.
Lummox JR resolved issue (Not a bug)
client/New() is too early to call winset() anyway; that should be handled in mob/Login().
generally all of our client/New winset code happens after the ..() which is what calls mob/login so that shouldn't be a factor but i don't know about this specific case.