100% crafting failure rate - no loss of items

1. Title: 100% crafting failure rate
   
2. Reproduction Rate:100%
3. Blocker? No
4. Details:100% of all crafting attempts, across all skills (refining and production) fail. These failures occur at multiple crafting stations, both public and my own tables. My crafting items are not destroyed in the process, but skill ups still occur. I can sit and fail over and over and get a lot of skill ups without losing anything.
   
5. Steps to Reproduce:Attempt to craft any item at a crafting station, regardless of success chance.
   
6. User Specs: Win 10, Intel i7 2.6Ghz, 8MB RAM, Nvidia 840M

 

This is currently happening to me right now in game. I am trying to make maple timber and I failed every time but my milling is now up to 58 and I have not consumed any fuel or resources. This gain rate was in 5 mins of refining.

 

Could you both verify if this issue is still occurring? We're not observing it via internal testing on latest patch 412. Thank you for reporting.

 

Dang, now I want to gm all my crafting before they fix this. 8^p

 

This appears to have been resolved for me in patch 412.

 

Issue appears resolved to me. Thanks for the fix

 

Just tried over at the public crafting stations in Brookside. Specifically the tanning and the Smelting tables. Tried to craft copper ingots and leather. Many attempts zero production.

 

Screen shot taken 9:30 am 6 May so you know the bug is still there. This time on my lot in Brookside on an expert craft station. Note my Alchemy skill level is now 70 and I have not produced one single thing from a crafting table or lost a single resource.

 

Just adding that this issue has reappeared for me as well as of build 414 - 100% failure rate for any crafting attempt.

 

One last update - I am able to craft in other towns, and also craft on my own stations when I place them in my basement. The 100% failure rate (at least for me) appears to be confined to the overland Harvest town map - both my own tables and the public town tables.

 

When elaborating on a re-occurring bug that is supposedly fixed, it might be a good idea to tag @Attenwood to get his attention.