Don't ask questions and then run

[Kaylakaze]

The reason SoftDeletes works like that is because it triggers the deleted trigger and intentionally does not trigger the updated one. This is standard Laravel behavior that any package would recognize. You're adding a custom trigger that no package will recognize and anyone using your package would expect that "updated" would be triggered ESPECIALLY since it's triggered on unarchive.

Why do I care? So you can either fix your code or people can at least understand the flaws/shortcomings in your code so they don't end up with non-logged changes like in my system.