Disarm Snippet v1.0

[Pyrogasm]

Effect shown, if <empty string> will fall back to default

I don't think that's a good idea. I might want to disarm a unit without showing any effect at all, and the only way I could do that is to pass an invalid string which is not something a GUI user is likely to think to do. Also not having a debuff on the UI to show the unit is disarmed is potentially good or potentially bad depending on user preference. I would make that an option.

 

[Daffa]

I don't think that's a good idea. I might want to disarm a unit without showing any effect at all, and the only way I could do that is to pass an invalid string which is not something a GUI user is likely to think to do. Also not having a debuff on the UI to show the unit is disarmed is potentially good or potentially bad depending on user preference. I would make that an option.

How about making the default string as empty if that helps? User can always specify the default string themselves depending on their map. Oh yeah, the buff shenanigans. I need to think how to handle it instead of letting users handling it on their on, both this and Stun Snippet, though it is beyond the original concept of these snippets.

 

[Wrda]

Default string as empty string would work. It only saves one line of setting the variable but that's whatever.

• Set VariableSet DisarmSnip_DEFAULTAttachPoint

Did you mean DisarmSnippet or is it intentional because it would be so big?

Approved

 

[Daffa]

Did you mean DisarmSnippet or is it intentional because it would be so big?

Intentional due to length. I recall I hit limit with DisarmSnippet for that one

 

[Wrda]

Moved to Awating update as requested by the resource owner.
Short explanation: Clash of a dependency's different versions when imported with other resources of the same owner.