Samool

Error codes 35 and 28 should be fixed now - if it isn't make sure to try to reinstall the client (if you're using our standalone launcher) or verify files on Steam (if you're playing through Steam). If it still is not working, can everyone having the issue post more details on their OS? Which version of Windows (or distro of Linux) you are using and whether it's 64-bit or a 32-bit install.

Will be fixed with a client update going out in a moment.

Make sure you have Steam Overlay enabled in Steam settings as it requires that to show the purchase site.

We're not currently planning to add that.

If you want to share accounts, which we don't recommend although we still allow it for sharing with up to 2 other people, your best bet is to use our standalone launcher and register regular Wurm Online accounts.

There will be a tutorial on Golden Valley, and there'll be NPCs to set your starting faith on Harmony.

This will likely be some time before the launch, but until we specify it here, assume it's not safe to start a character. We'll make sure we post a notice once you can create a character that'll be able to go to the new servers.

No, you create characters through the launcher when using the Steam client.

Starting tomorrow, new characters will start on Golden Valley and the portals there will have the new servers as added destination choices.

No, you cannot. The servers are connected via a portal. Ignore the sailing indicators, those are not indicative of anything and might disappear soon.

Small update out now, with another one to come this week still. Changelog:

Can you post your console.log file? I can't seem to reproduce this blocky issue with the same UI scale setting, must be something else to it.

The new UI client together with some fixes will be the default by Friday, but the old client will still be accessible through the choose client dialogue.

The controls might be a bit unforgiving, but it should be possible to play Wurm Online using mobile devices via Geforce Now once it releases on Steam.

Is that the full console log from the file or from the in-game console? It doesn't seem to contain the OpenGL/graphics driver information, I think that only shows in the actual file.

Can you post the entire console.log file? Seems it might be related to the graphics drivers but would like to verify that, and if we can fix it.

@Lotus1 @Damascus Can you both post your console.log files? It's quite an odd issue, likely depending on the exact OpenGL version available or the graphics drivers in general, the log should help pinpoint it.

That's very likely accidental, we're aware of the bug with certain structure textures failing to load, but there's no possibility the different launcher affects that. The memory settings in the "new" native launcher are also the exact same as in the JNLP launcher, so that should not affect the heap crashes at all, unless you were using the low memory client shortcut - but that also acts the same as its JNLP counterpart. Looking into the issues with launching JNLP as it's still a supported, albeit an unrecommended way to play the game.

There's an arrow to go back to the cluster selection screen in the top right corner, when you open the portal it should show both clusters.

Can you expalin what's broken there? I seem to be missing that. Try verifying the packs in the launcher, that seems to be a corrupt graphics packs issue. You can do that by using the gear button next to the progress bar in the launcher and pressing Verify in the window that pops up.

The UI would not affect mailing times. Yes, that's fixed with the input box bugfix.

New hotfix coming out in a minute, changelog below: Thanks for all the feedback so far. We'll be working on adding back some better font size options for certain windows such as chat and inventory type windows, as that seems to be a common request, and we're still going through some other issues. Additionally, we're looking at giving the default and repeat actions a bit of a redo as it seems the implementation is much less than ideal, but that may take some more time. If there are any critical ones we've missed, feel free to also repost the issue into the client bugs section, we're working through all the posts here but some reports may require some more information on the problem and it'd be easier to follow up on them that way.

It's pretty foolproof - our shop won't allow you to purchase items for a Steam account, and you won't be able to buy from the Steam store on non-Steam accounts. At the start we'll be using the Steam microtransaction systems that require you to be logged in to your character, if we also use the Steam store through DLCs (like EVE does), we'll make sure it's clearly stated that it only applies to those accounts.

Should no longer be an issue after the hotfix released just now.

Fixed now!