bp1986

Got hit here again - [16:24:12] You must not move while doing that.

In the grand scheme of Wurm, branches are actually pretty recent. They seem to be intended as a last ditch effort for people who lost all of their tools and are building back up from nothing (crude axe/knife). Train up your woodcutting if you want good QL wooden items.

Out of curiosity, how many were spawned on each server?

So, simple suggestion here - we already have a visual percentage on the mission bar, so we don't need it on the mouse over as well. Instead, have a component counter (so instead of "50%", have it say "17 of 34" or some sort)

I have noticed today that there is a bit of an oddity in shipping papyrus vs archaeology journals with reports. Papyrus = 1c Blank report = 1c Journal with 85 reports = 1.85c So, for some reason, reports in a journal get the 1i bonus, but reports outside of a journal get normal shipping.

IMO, this is how it should break down: Metal class: 2.7 KGs Alloy class: 1 KGs Moonmetal class: 0.1 KGs Will still make the super common copper ones kinda useful without blowing moonmetal out of the water.

So a sermon but for crafters. Interesting idea, not sure how commonly it would be used, but would be very useful at impalongs - jesters providing entertainment(buffs)

IMO dispelling should just outright destroy it, like it does with any other cast. BUT, I feel that high level restoration should be able to attempt to salvage the rune. Something crazy like 90 restoration and 90 QL chisel should grant around a 10% recovery rate, IMO.

It would be cool if they separated out food and drink affinities. At the moment, there is nothing that booze can do for affinities that food can't do 10x better. If they worked in different pools and stacked, they could be very interesting for affinities.

Mixed feelings on this one, we have enough too much junk coming out of arch as it is. So +1 only if it is confined to the same tier as shafts, lumps, shards, ect, but will still be dumped on site when I find them.

Yea, there needs to either be a solid line of text stating that the report is complete or an ingame mechanic that shows the report as complete (changing color, changing name, ect) so we don't need to right click through them all. As far as I can tell, it is not explicitly dependent on the "and complete the location details in the report" (which is what I have been using in my WA trigger), but more of a checklist of things needed. It seems that the trigger for "and complete the location details in the report" is just the least common, so it *usually* happens near the end of the life of the report. But yea, major +1 for me, or I am going to have to start working on my own variant of WA that is capable of logging multiple lines into one item and multiple dynamic items.

1 - Strongly agree, we badly need some way to check these outside of manually finding the record(s) in question and right clicking through. 2 - The small tokens make sense to me for this. I don't think the book really needs to track beyond the lifespan of the report. If you need the report to find your way back to said deed, just store it outside of a book and use it for navigation and never actually collect the reward. 3 - Maybe, but only if they sort out how the client handles client-only items (see insanity hallucinations and how they stick around forever) - could be more annoying than interesting.

Conflict found between: https://www.wurmpedia.com/index.php/Dye#Vehicles.2FShips - Knarr - 25.440 kg https://www.wurmpedia.com/index.php/Knarr - Total Dye Needed: 240kg

Digging deeper At higher levels, we should be able to pull up more items per action. I propose that this work similar to how forage/botanize works where the action is extended out but has multiple "ticks" where something can be gathered. Each stage will extend your action by 1 base action time and give a chance to each extension to gather an item at increasingly higher difficulty. 1 skill - 1 base action time, 1 possible item gathered 30 skill - new action is +5 difficulty from base 50 skill - new action is +10 difficulty from base 70 skill - new action is +15 difficulty from base 90 skill - new action is +20 difficulty from base 95 skill - new action is +25 difficulty from base 99 skill - new action is +30 difficulty from base As I understand it, higher difficulty = better tier items. So to counter this, any "failure" will stop the action where it is - making it fairly uncommon for the +30 difficulty tick to even be attempted. Restoration basin A moderate sized tub that, when items are placed inside it and restored with the chisel/metal brush, the debris from the restoration will gather in the bottom of the basin. Debris removed during the chisel phase will gather as rockshards Debris removed during the metal brush phase will gather as dirt *I know that this was be a negligible amount of rock/dirt gathered through this process, and I feel that some people would be annoyed by the extra parts, so I suggest that these debris components ONLY appear when items are restored in the basin and are discarded automatically when restored elsewhere Prying off runes An insanely difficult action (like 90 restoration with a 90 QL chisel should only give about a 20% chance of success) but we should be able to remove runes from items so we can attach them elsewhere. Rune stacking The citizens of the past clearly found ways to get more than 1 rune on an object and I feel that we should be able to study their ways. At 70 restoration - a second rune can be attached to an object at a +20 difficulty At 90 restoration - a third rune can be attached to an object at a +40 difficulty The grinder I get a fair amount of stuff that is completely worthless to me and it either gets left in the field or flushed down the Vynora toilet. I propose that we intoduce another new item - the archaeology grinder - to help deal with these items. Whenever 100 identified fragments are placed into this machine and it is used, it will reduce all 100 fragments down into a single archaeology powder. Archaeology powder can be applied to tools to give 1 power to an archaeology imbue (max 100) which will slightly increase the performance of said tool in archaeology. Trowel/shovel - higher QL fragments and an increase in chance of getting higher teir items Chisel/brush - takes off a little more debris and increase chance of getting alloy For a fully upgraded set of trowel/chisel/brush, it would take 30,000 junk items. So get to work!

I may not have had a full understanding on that one but it may still be a good idea to look into scaling to make sure that everyone is fair.

Hello, I recently decided to upgrade my stills to 90 QL and have been rather disappointed with the results. I started into some research on this to see if I can track down what happened. First issue - the amount of product per pole/the pole frequency I have been noticing a steady growth of 0.01 of product per about 90 seconds through visual observation. I live on Deli, so results may vary for others. Over the course of an hour, I am seeing about the same results. So the problem here is that QL does not seem to matter, in just under an hour, my three tester stills produced... 90 with iron fo - 0.38 KGs 90 - 0.37 KGs 70 - 0.38 KGs *I am willing to believe that the 0.01 variance is due to just awkward poling at the time In the code, I see this is hard coded as using only 10g per pole per the following line in pollDistilling() int usedWeight = Math.min(10, oldWeight); How I would fix this? Create a few new variables where we determine how many expected poles should have happened since the last pole, then multiply the weight by this number: *Create new element on the item for lastPole float poleScale = (item.lastPole - Now) / expectedPole; //(yes, I think this will not work in its current state, going to need proper conversions, but you get the idea) int usedWeight = Math.min(10 * poleScale , oldWeight); item.lastPole = Now; What would this do? This would allow me to run my stills at the same effective rate on Deliverance as it would on Xanadu or any other server without increasing the numbers of poles needed on the server. Second issue - Fuel scaling by QL does not seem to work in stills Since we have established that QL of still does not effect number of ticks or amount of product produced per tick, logically I can just load up my tester stills and just wait for burnout. To get a decent metric, I have allowed my three tester stills to run through a kindling (lighting), a peat (right after lighting) then run all the way to natural burnout). 90 with iron fo - 1.12 KGs 90 - 0.99 KGs 70 - 1.02 KGs From what I am seeing of these results, it looks like the iron fo is a wise investment as the still did burn longer and got around 10-13% more product. However, the QL had little to NEGATIVE effect on production. Considering all other furnaces scale burn time with QL, this feels like a bug (and may actually belong in the server bugs forum). How I would fix this? I feel that this could be attacked by either correcting how long the fuel lasts in a still scaling on QL or scaling the product by QL of still. I have limited understanding of the furnaces in the source code, so not even going to attempt source code work for burn time. As for scaling on the QL of the still... (continued on first issue) float qlScale = ... //arguments could be made on how to handle this int usedWeight = Math.min(10 * poleScale * qlScale , oldWeight); Proposed qlScale: 1 QL = 1 50 QL = 1.1 70 QL = 1.2 90 QL = 1.4 --could be judged on a curve or could just be hard set numbers --additionally, this could even be raised a bit due to the difficulty of improving these things Ideas? Concerns? Questions? Edit: I had some questions about my test, so I would like to take a moment to clarify a few things: All stills are in the same building (third floor) and in a cave. They are all within 1 tile of eachother. I stayed in local (and in the cave) the entire burn time. Test was not done during backup lag. Test was done on deliverance. Edit2: Doing further testing of a 90 QL still vs a 27 QL still... currently they are mostly matching eachother in speed 90QL = 0.17 so far 28QL = 0.18 so far Total for runs: 90QL = 1.00 KG 28QL = 0.76 KG So, I guess QL does seem to matter, but the suggestion still stands that no increase in performance between 70 and 90 QL is kinda lame and needs some love.

Still hopeful that a dev sees this and makes it happen!

[18:29:08] Merchant_Battlebooze says, 'Please empty the sealed small wine barrel [mead] first.' I want to set up a bartender who will sell my barrels of booze, but my merchant won't take them. Please allow these items to be sold on merchants!

Xanadu:Fogshore(underground):Wine Cellar Double door (sandstone) lost the lock as well Don't remember the exact QL of the lock, but chances are it was pretty good (70+ QL)

Are there any plans to make the bugged barrels actually finish fermenting? Or are we stuck with these forever?

Steps to reproduce -activate woodscrap -right click on a stack of barrels that contain unfermented drink -create fermenting drink Expected result -create the first fermenting drink -stop further actions as your woodscrap has been used Actual result -create first fermenting drink -actions continue and produce the fermenting drink barrels from your unfermented drink barrels despite you no longer having the woodscrap Priority/risk -Low - All this does is save on woodscrap and make the fermentation process a bit quicker for the user

If you still have the following items, please COD them over to Battlepants and I will accept them tomorrow evening. If not, please PM Battlepants in game (or this account here) and we can try to work something else out. Thank you. Bronze Runes of libilla 40c 10,05ql(29%) 13,36ql(35%) 13,87ql(35%) 14,42ql(37%)

I would probably go with "body" since it feels like more of an overall body development. Also, it tends to grow a bit faster than body control.

My vote is for lead. It is called "plumbing" after all.

One existing workaround for this is to put the seeds into a container and then putting said container on a toolbelt. When you activate that slot on the toolbelt, it will activate the first item in the pile within that container.