weapons and garbage that charges only while wearing

[kiryan]

should not lose their charge when fumbled, when you die, or when you rent?

especially the ones that are 1/week and not !drop. (ic2 axe)

Why should you have to curse it to be able to proc it once in a blue moon.

Also, might be cool on all items to give them a % chance to become fully charged in shorter durations and not be so boringly predictable.

[Pheten]

Would also be cool if there was a way for us to see how far charged they were. Throw in some code so when you examine the item you see this:

Examine sword
This sword is made of fine steel and glows with a blue aura.
This item hums with power ready to be released!

or
This item has a weak aura of power about it.
ect ect.

so we can judge a little.

[Birile]

Would also be cool if there was a way for us to see how far charged they were.

Isn't there verbiage that hints at this when you try to use one of these items and it's not fully charged that gives you an idea of how long 'til it can be used again? It's been a long time since I've tested this, forgive me if I'm way off-base. :)

And I agree with Kiryan's concern, to lose a charge if you fumble something, die or rent out really kinda blows. Can it be coded so it only loses its charge once the proc is released?

Oh, and the variable charge time is a neat idea, too, but only if it were possible for the item to charge in a longer-than-normal amount of time, too, not just shorter!

[Vena]

wear charge items were made so to keep people from stockpiling an item and unleashing the charges consecutively.

One mistweave blind ok, a bag of 26 charged mistweaves bad.

course, they couldve just figured out some way to implement unique / lore items (can only have one on your person) to alleviate the 8 swiftwinds in your hole type issues.

[Ashiwi]

Verarb could sure fit an awful lot of misties in there...

::sniffle:: Now look, I'm getting all misty over V and his misties.

[Birile]

wear charge items were made so to keep people from stockpiling an item and unleashing the charges consecutively.

Precisely.

Everyone understands this. The problem arises when the code involved causes items to lose their charge in the cases Kiryan listed. I think that definitely warrants looking into and re-coding or adding to the code to keep it from happening.