Skip to content

@charges, use, @runout #223

@MadamButterfly

Description

@MadamButterfly

I was trying to verify that @charges, use and @runout were working the way I thought they were before I filed a report. However, today they are not working at all.

Previously, @charges would deduct appropriately with 'use'. But when the last charge was used and Charges became 0, it would not do @runout until you used the object one more time before it would do @runout. Would prefer to see it check charges after every use and trigger @runout WHEN charges hit 0, not after.

However, today, an object set with @charges and @runout, 'use' did not trigger the deduction of @charges at all, but it did emit the @use message.

I can find nothing in my @list options or config files associated with blocking 'use', @charge or @runout. If these have been made defunct in the hardcode, consider removing help files? Or update help files if specific flags are required to make these work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions