Anarres

Please see screenshot. Everything is default as far as new UI features is concerned. https://imgur.com/2jRIWlb Update: seems to happen with other windows, but they're draggable to change size, so maybe it's no big deal. I'd think the defaults should look ok, though, and this is as close to default as I can get on an old character.

By "affect" hedges I assume you mean destroy hedges. If you mean something else please tell.

If it doesn't seem to reproduce, perhaps try queuing actions, then moving to the nearby tile during queue. We had it happen this way, and a third player in CA also mentioned he had it happen 1) with dig from hotbar. and 2) when moving tile (so the selected tile becomes nearby tile, not the tile you're standing on).

No, it doesn't. Can you check and give an example of management permissions on an item that would seem to include the right to change ownership?

Typically untamed horses are not vulnerable to mob attack. A horse hitched to tent is not attacked by (regular) mobs. Unless you're talking about rift mobs, those attack them yes. For rift, you need to be careful, ok, but you can lose a horse anyway to aoe. You don't need the fence, you can park far from rift area instead, but if you're worried you may be better off with a fence. A single fence for the whole party at rift should be enough of course. When you talk about "many people" who fence, are you talking about rifts? I am not aware of people who fence for camping, except in rare cases. I mean, for the night you don't usually need it, and people don't usually camp for more than one night (and that's the exception even, most return to their deeds as soon as they possibly can). Don't get me wrong, I'm all for features that help roaming, but I'm not sure why you think today people actually roam and fence because of it (not for some good reason that a "camp" would replace). Also, assuming they would, the suggestion seems to be that you need to have items like ropes in inventory, if I understood right? Dunno, typically once people find out / make / are given a halter rope, they don't need or carry ropes. Trying to think how I'd use such feature, I wouldn't have ropes, and if I'm not near ship, I wouldn't have a ropetool either, so if I figure during a trip that I want a camp not a tent (why?), oh well, gotta make a ropetool first...

A branded horse is not vulnerable. Once you brand it, you can set permissions on it just like an owned item, and no one else can take it, lead it, tame it nor attack it. A horse, even unbranded, hitched to a locked tent or cart/wagon, is similarly invulnerable (except in rift areas, don't leave horses close). The newbie tent is invulnerable, and serves as hitching point for one animal. The crafted tent needs locked by you and it becomes similarly invulnerable.

Yes, yes and yes to all of them. Special mention for this darned thing: 😼 At least if we saw borders slopes, we'd see it.

I just checked these days that the 6h max SB bonus does apply both on Freedom and Epic. Of course I'll assume that all bonuses do (not items, not the temporary SB refill). I agree that the inconsistency of priest journal updating in real time for many things, but not updating in real time when it ended, is an UX issue, I hope it'll be taken into consideration. But at least, if bonuses apply now across any clusters, as it looks like, such surprises shouldn't be too nasty.

Will do, thank you! ...though I thought I recognize you, weren't you a dragon chasing my ship last time we met, mmm.

My character was HoTS on Affliction, and didn't cross to Epic for more than six-eight months. Today I made an Epic portal on Deli, and "used" it. It surprised me that it asked me to choose between home servers, as if it didn't know anymore that I was there before. I chose Affliction. It asked to choose kingdom, I chose Hots, and starting point, I had selected only one option available anyway. I crossed to Epic. I ended up in the cave far away from the start, where I was last time, months ago. (so it knew! something...). However, I got the message that I'm in enemy lands, and I still see Gl-Freedom and Freedom channels, and can speak in them. So it seems I'm still Freedom. That's VERY BAD, because I probably can't go back: there's no epic portal in my cave anymore, it may have been destroyed by a cavein or decay, no idea. And if I suicide to starting town, I will be likely the enemy and can't even go use it. Edited to add: I managed to reopen the old cave to the outside world, and grab a tree, so maybe I can make an Epic portal when servers come back. The toon still shouldn't be Freedom on Epic though. Character: Amath

I seem to recall you get this message for rocksalt, or a tile that has been rocksalt, mined out, then collapsed as rock. It is now a rock tile, but it still gives (or was giving a while back) the old message.

In the second example you can do a similar thing, you have to remove one of the V tiles first, then you can remove tile 1. Any of the V should do. It's like that old game with X and O, say you want: XO OX where X is a closed tile, O is an open tile. Such "diagonal of empty" is not supported in wurm, and always when you try to mine out the second O we'll get a message about "side shaft". If you need both O opened, you have to open an X first. Note: the message sounds like it's talking about dangerous shafts, but don't read it that way, it's talking about side things, diagonal things, it can't do. It can't make two caves meet only in one corner, diagonally adjacent.

Lets call the open tile before 3, on the same row with 3, "Z". So the row is XZ3X. If you mine 1, then want to mine 2, then Z and 2 would be openings that only touch in one corner, on diagonal. That is not supported by wurm. What you can do alternatively, is to mine 1, then 3, then 2.

Is your chest locked or unlocked? Past report that may be relevant:

Can't set volume: You can only change volume when the measuring jug is in your inventory. It is in inventory, empty. Tried full, empty, dropping it and repicking it up, nothing. Can't change volume anymore. Several players reported it on CA chat also.

Can we please get an answer to this? This is becoming critical: rift mats have decayed everywhere, around active beacons. Rift plants have been the first to go poof. Now there are almost none left, all over active Jackal where there have been plants before. They have decayed away, between the time we first explored the place, saw the beacon, saw a plant, and two days later when we organized an expedition to kill the defenders. Stone is next, it decays slower so we see some (lower and lower effective ql every day), but it will go away too. There are two issues at this point: first, rift mats around active beacons shouldn't decay as long as the beacon is active (as long as there are defenders), and now second... how about rift mats that no longer exist? Will new plants be "spawned" around Jackal?

We lost the first rig during attaching to the first knarr on Jackal. We took a deep deep breath, put together leftover mats, went foraging for the rest (not kidding) and imped more on every part of the second rig, so it'll end up higher ql than the first at least. No big difference but man, had to do something. Then our best skilled shipbuilder attached it at first try. Just to note, it's not repairable but it can be mended. FWIW.

We tested that it works normally if there is no ghostly beast vanishing by itself at its summoner's death. At a third beacon in the same area, we had a summoner as last mob, and watched its health. When it was low, it summoned a beast and we got away from the summoner (it also teleported soon), and killed the ghostly beast. Then finished the summoner. That ended the beacon fight successfully. Trouble is when the beast vanishes by itself, then it seems to languish around in limbo.

We fought mobs to two jackal beacons the other day. The last mob was a summoner. It summoned a "ghostly beast" right before it died. A single hit on summoner killed it, and the ghostly beast vanished. In my understanding, this is intended behavior so far. However, now the beacons cannot be closed, no option to burn hearts, no ability to harvest rift mats, no points awarded. Apparently the server thinks not all defenders have been defeated, but there's no other (visible) mobs anywhere. Our best guess is that probably counts the ghostly beast. This happened twice, two beacons are now unbeatable, same scenario. Combat log: https://pastebin.com/Jgji727q It can be seen that a beast was summoned and summoner killed before it.

Woot! Thank you so much for organizing a public fight, bob ❤️

After the hotfix, the behavior is similar, some rift beasts are bugged/unattackable, some are not. It's not obvious that the bugged ones are summoned by a beacon or just random, they can be met both near a beacon and out in the wild or water. We don't see the endless taunting in the log above, but we are still unable to attack:

Woohoo, grats!! Do you have title choices you're thinking about?

This sounds like a sensible idea but sadly it didn't work, no difference in behavior that we saw.

After the patch the other day, some rift beasts at Jackal beacons enter a bugged/blocked state: - they taunt a player endlessly, every second, and no one is able to attack them all the time (all attempts to swing are interrupted) - attempts to bash from combat window result in "[17:06:02] <Uisge> [10:05:44] That would be very bad for your karma and is disallowed on this server." There doesn't seem to be any reliable way to get them unstuck or attack them. According to players on Freedom, where it also happens, kiting aggressive mobs to them may get them unstuck and attackable. On Jackal, we don't seem to do even that. The Jackal beacon progress is blocked. There are tickets on this behavior, please acknowledge or suggest a course of action. Example of combat log: https://pastebin.com/Q5PYdY0N

This may seem like a small thing but it's really annoying. Both issues: close enough that you can 'take' should be the same with can drag, but it isn't; and, the message is inappropriate, leading to confusion as to what the problem really is. It has been recurrent in chat channels, and reported before.