Ostentatio

It would help if anyone experiencing this issue could mention which GPU drivers they have installed, including the version number if possible.

Could you give an example of a cake it does work on?

Thanks for the reports! I can confirm that there is indeed a bug preventing planting of catseyes and waystones due to a recent change. A fix is in the works as we speak.

For the special actions you perform on the holy site itself, you will always be able to perform that action just as often no matter how many other people are there and doing the same. Terraforming, deeding land, and building structures/fences will all be blocked in the vicinity of the site.

The cooldown period between switching faiths has not changed. The ability to build a colossus should not have been affected by any recent changes.

This would be something else entirely, unfortunately. The crashes relevant to this thread are those that are a simple crash to desktop with no message from the Wurm client at all.

@WittleBunnBun,@Zerobyteand anyone else suffering a similar problem of the Wurm client crashing with no error message or warning: The next time it crashes for you, I recommend going into your Wurm install folder immediately following the crash and grabbing your console log, then pasting it into a spoiler here. It'll be called something like "console.<character name>.log". And if there's a recent file there with a name starting with "hs_err", the contents of that would be helpful as well. It would also be good to know the following information, if you can provide it: Computer specs (Operating system and version, graphics card model, amount of RAM, and anything else you wish to provide) When this problem started occurring Which client you're running (normal live client, low memory, etc. - if you don't know it's probably the normal live client) Server Account name Whether or not you've tried any particular workaround, such as in the game's settings, and whether or not that helped Please note that any hs_err logs are not generated directly by Wurm, so unlike the console logs, they will NOT redact your Windows (or Linux/MacOS) username. If you upload a log of that nature and don't want your username to be visible, feel free to search for it in the file and replace it with just "USERNAME" or something similar.

And sold! Didn't expect to get an offer for the whole lot so soon.

SLEEP POWDER CLEARANCE SALE!!! (artist's rendering) I have 50 sleep powders in my inventory and they need to go away! Free delivery to any Xanadu starter deed, flat 1s delivery fee to any other Southern Freedom Isles deed that is coastal or on a highway. Base price: 1s each If you buy 10 or more: 95c each If you buy 20 or more: 90c each If you buy the entire lot: 85c each with free delivery anywhere on Southern Freedom Isles! Will not deliver to Chaos. Sorry. This sale will be taking offers here until the timer ends in about 3 days after this post, so that orders for larger amounts will be prioritized over smaller orders. Ignore the part of the timer that says it's an auction. (EDIT: Already sold the whole lot!)

For anyone still having this problem, please post which graphics card you're running Wurm on, if possible. Also let us know if disabling FBO support in the Compatibility settings tab helps; this will have undesired effects, but it has improved stability for some and it would help to know who that works for.

This will be fixed, of course, but in the meantime, logging off and logging back on should show the goal as completed.

What do you mean by "odd alcohol power"?

Thanks for the report! I can confirm this journal goal is indeed bugged and that it will be fixed shortly.

Thanks, it is indeed intended to tell you what the appearance of the guard tower is, but that doesn't appear to be working properly here! The cause of this has been identified and it will be fixed. Edit: Forgot to mention these, which also have fixes in the works.

Do you remember if you foraged multiple items during that action, and if so, were the supreme berries the last thing you got on that action?

I can confirm that this is a bug, but just with how it's displayed. For journal goals with multiple distinct parts, like this one, or "mine copper and tin", it's showing as 100% complete in the client even if you've only done one of those things. Just to be extra clear, it won't actually consider the goal complete unless you do in fact milk a cow, bison, and sheep. Milking only one will make it highlight in green due to the bug, but it won't actually count toward progress. Actual progress is being tracked correctly. Thanks for the report! We're working on a solution so it will display properly in the future.

Thanks, I can confirm this is indeed a bug. I believe this is the only recipe-related achievement affected by it.

Thanks for the report. I can confirm there's a bug here preventing that particular achievement from triggering.

Thanks for the feedback. What's going on here is that the "Libila's Game" is a Libila colossus that had been renamed by a GM or developer, so the text winds up being unclear because it just uses the item's name. This is a situation that will happen less often on the live servers, but just to avoid any confusion, we'll be adding some clarification to the text in situations like these, where the type of item isn't clear from the name due to a custom name being applied. In those cases, especially when it's not an item that could get a custom name through normal play, we'll be adding text saying what type of item it is. In this case, it would end up saying something like "a colossus of Libila named 'Libila's Game'". It's definitely a source of confusion we'd like to avoid.

Thanks for the report; after the "and" it's supposed to mention a nearby village. We'll have that fixed shortly.

If this has generated any console log errors that you still have, please post them here in case it's indicative of the same problem.

Are you sure it's happening when the wound heals? From what we can see, it should only interrupt an action when getting worse. Let us know if it happens on a healing tick as well.

To anyone experiencing this crash, it would help greatly to know exactly what you were attempting to build, and how, and whether you were running the new UI or the legacy client.

Thanks for the report! This was unintended and will be fixed with a graphics pack update on Thursday the 23rd. No other items have been affected as far as we can tell.

I agree that does look small in that screenshot. What resolution and UI scaling options are you using there?