(Servlet) better error handling in console for `add_attribute_modifier` mech

[dusk ruin]

got a stack trace appearing in the console because of the add_attribute_modifier that has an existing ID already.
I was expecting a normal denizen error but seems to be printing the whole stack trace in the console.
Here's a sample log.

https://paste.denizenscript.com/View/119380

[haughty nest]

(Servlet) better error handling in console for add_attribute_modifier mech

[haughty nest]

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.

[dusk ruin]

!logcheck https://paste.denizenscript.com/View/119380

[leaden idol]

Log Check Results

Server Version

Paper version git-Paper-381 (MC: 1.20.4)-- (Outdated build, behind by 1... Current build is 382)

Plugin Version(s)

Citizens: 2.0.33-SNAPSHOT (build 3296) -- (Current build :white_check_mark:)
Denizen: 1.3.0-SNAPSHOT (build 6976-DEV) -- (Outdated build, behind by 2)
Depenizen: 2.1.0 (build 852) -- (Current build :white_check_mark:)

Checked For

@dusk ruin

UUID Version

4 (:white_check_mark: Online)

Java Version

17.0.5 :white_check_mark:

[pure gust]

Changed to Feature

Thread is now a Feature thread. This indicates a request for a new feature to the plugin, that both (A) does not already exist and (B) reasonably can be added. If you are unsure whether this applies, use </helpthread:1028674284870180883> to change back to a normal help thread.

[fallow acorn]

eh, sure, why not, added error handler ref #commit-log

[pure gust]

Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

@dusk ruin

[dusk ruin]

thanks! appreciate it!