Budda

Just an update to the goals part: The other 3 tome related goals (mage, magus, diabolist) will also reroll - as well as a few pvp specific ones (HotA, deed draining). Other (currently) incomplete-able ones and bugged ones will be fixed.

If you complete it before the update, it will remain as your personal goal as completed. Only those that have one of the above ones as incomplete will have it removed and rolled as something else.

That code is unused after the valrei update.

More of a bug than anything else, moving to bugs section.

Will have another look at this - the way it decides the one person to get most of the rank gain and affinity is a bit weird and I don't like it (this is how its always been, not a new thing).

Do you have a bug in my office or something? I was just talking about this sort of idea to Retro yesterday as we were building a spawn town on WU.

The heal is cast power dependant - though it may be a bit low for the super low end powers. Based on your heal amount here it looks like your cast was a power of 7. Will add in a min heal to bring it more in line with LoF for low power casts.

I found an old home video of Emoo's early years. https://i.imgur.com/Vqpie8A.gifv

Other servers too - moved the topic to Town Square to make that more obvious.

There's not a whole lot to show atm. The last year has seen a lot of other things take precedence over me spending as much time as I would like on the UI (though that is slowly changing now), so the majority of changes have been either backend changes to support the new UI, planning how we want things to change, or implementing the early versions of some of those things. Early versions are just that, early. I'd much rather not show off things that look terrible (even if they function fine) and they're still likely to change before their final version. Like Retrograde said, some of the plans and things we've been working on have already made it out to the live client, as they were things we recognised as not needing to wait for the new UI - and there will likely be more of those things before we finish too. When we have something that I'm happy to show (and Saroman has had his pass at making it look not terrible), rest assured that it will be shared. Edit: Having said that though, I am interested in any ideas people bring up in this thread - so please do continue in this thread with things you find silly or unintuitive that we could address with the new UI (or even things we could change with the current client).

Might take a while for them to get there, but they _should_ prefer less deep water when they move, so hopefully they'll start heading back towards the land.

Are you sure about that?

Hoods, helms and hats not showing their dye when worn was an issue that was fixed in today's update.

Just tested this and it seems to work as intended, lead doing more damage than iron. Can you double check this? Also in the future please report bugs in the bug section - I'm terrible at keeping track of random posts like this, nearly lost it in everything else.

Sorry my bad there, was doing a check backwards. Fixed for next update later this week.

Destroy damage, so mostly mauls (though you can mostly use any item technically).

Normal wounds (bruises, cuts, holes) still have a chance to cause new wounds in the same position instead of stacking 100% of the time, as they always have. The bug fix is mainly aimed at other wounds that sometimes didn't stack as they should have, where the code wasn't checking for all wounds, but only one in that position. It is still a 30% chance to create a new wound (bruise, cut, or hole wounds) instead of stacking on an existing wound as it has always been.

Will be fixed in the next update - that place option was intended for items on ground only, not items inside containers such as forges.

That would mean all missions that don't gradually complete (i.e. missions that go from 1% -> 100% instantly) would never get a full chance to be completed. There is no way to track if someone is close to completing those sorts of missions so it isn't fair to just cut those off like other missions that can track properly.

This will be addressed. Locking this post.

Just FYI for some of these reported ones - only those that can actually have progress added to them will be cancelled after half of the time - so build missions etc won't cancel. The give and create item missions listed here should be though. Will look into it.

So the old timer code for mining had a minimum timer of 4.5s before bonuses are applied, with an absolute minimum of 2.5s. With the change I made it so your base timer is calculated based on your skill/ql and bonuses, then that is added onto the base 2.5s time (so there is no 2s buffer that bonuses take out of). What you're seeing here is the diminishing returns you get at these very high skill and ql levels. With 99.999 skill and a 95ql pickaxe (no enchants or anything), your timer would be about 3.06s, and swapping that for a 97ql pickaxe the timer would go down to 2.83s (due to how ql comes into play when getting skill for these checks). Removing the base 2.5s timer we get 0.56s and 0.33s to work with on the bonuses. 100 WoA or BotD would make the biggest difference here, cutting those down to 0.28s and 0.165s, but other bonuses like runes and rarity only do about 10% each, which isn't much when you're getting this low. We could change this back to the minimum no-bonus timer is 4.5s to give the bonuses more to work with, but I think it is a more fair system like this - where bonuses matter more for those that haven't maxed out their skill or item QLs. Edit: Some more numbers now that I'm looking at it - previously if the average of your skill + pickaxe ql was over 93.3, you were wasting your time as it would not lower the timer any further. Now over that mark you'll still see timer reductions without having to use any bonuses.

*slips on keyboard and adds a new pierce weapon*

Then everything is working as intended.