That's a fair stance, but that's an issue in spectrum. And that means that within the range of too much and too little, their should be a just right amount.
The idea was that by connecting the amount of durability returned when repairing to crafting, then players who don't want to worry or needle over it would just have enough to keep equipment upkeep between city visits without tedious clicking and crafters would have more than enough to keep up the durability bonus between battles without worry and/or could self buff at risk of their weapons with far greater management
Consider for a moment how often you need to repair something, consider if you had one hammer to repair all worn equipement two times that cost 30 gold.
Would you ever feel pressured over the worry of equipment breaking?
Well, that could work for me I guess. But balancing all that and adding new skills and repair charges is a lot of work that I'd rather see going to a mechanic I actually like instead of something I at best barely care about and at worst just want gone.
Thank you, this is the kind of stuff I've been trying to convey that others seem to disregard.
Like i've said, your feelings are mirrored by many saying 'just remove' it. I find the idea that they dont even want to contemplate trying to fix things slightly unbearable and that they are more willing to work to remove it, since that requires work of it's own, slightly annoying.
To others the concept of keeping durability in is slightly more important. So I feel more would be happy if things were simply changed and fixed.
As to whether that work should go here or other problems? I leave that to the devs. Personally, I'm the kind that would work continuously on one mechanic, no matter how others see it, till I got it right before moving on.
The fact that it's kind of a controversy an the devs care and seem to want it in makes me inclined to think they may slate this higher.
Lots of things need work and some are obviously higher priority: Ex. Stat system
But i can not comment on how the general priority list should go for them; not my place.
All, I've done is try give feedback on how to fix something that's 'broken'....which is really how I see this should be discussed.
How to fix it, not whether it's important or not, and certainly not whether it's inconsequential enough to be removed......Those later considerations are dev ones as far as I'm concerned
