WraithSlayer Posted July 19, 2015 Posted July 19, 2015 I have quite a few mods that were built for 1.39b, but seem to be working correctly with 1.59c for the time being. However, I've read that there some things in the latest versions of the framework that have become deprecated (such as mod events using 'HookAnimationStart' instead of 'AnimationStart', and so on) and will potentially stop working in future versions of the framework. Is there a list of these deprecated methods somewhere so that I can find them in my mods and correct them before a new framework update breaks them?
Guest Posted July 19, 2015 Posted July 19, 2015 The full list of "No more working" items is not yet ready. I am comparing 1.59c and 1.60 beta 2B for my internal use. A huge amount of old array management functions are deprecated now (and they should use PapyrusUtils.psc). There are notes from Ashal inside the code (with a funny indication: "DEVELOPMENT DEPRECATION, MOTHER FUCKER"
Ashal Posted July 19, 2015 Posted July 19, 2015 It's unlikely the deprecated functions will be actually removed, not unless I decide to throw out the entire framework and start again from scratch, which is very unlikely at this point. I fear breaking compatibility with various mods whose authors are no longer around to maintain them to much. Deprecation warnings in logs will also be disabled in final non-development builds. One of these days when I get around to catching the documentation up, deprecated functions will be removed or noted heavily there so people avoid using them. (such as mod events using 'HookAnimationStart' instead of 'AnimationStart', and so on) Not sure which one you are saying is the deprecated on but just in case, the deprecated on is "AnimationStart." "Hook_____" are the new hook events, though the only real difference is that "HookAnimationStart" sends a more convenient set of arguments to the event instead of the arbitrary ones the old "AnimationStart" does. The new ones may or may not be a little bit faster as well, since the old ones are sent last.
WraithSlayer Posted July 19, 2015 Author Posted July 19, 2015 It's unlikely the deprecated functions will be actually removed, not unless I decide to throw out the entire framework and start again from scratch, which is very unlikely at this point. I fear breaking compatibility with various mods whose authors are no longer around to maintain them to much. Deprecation warnings in logs will also be disabled in final non-development builds. One of these days when I get around to catching the documentation up, deprecated functions will be removed or noted heavily there so people avoid using them. Ah, thanks Ashal. In that case I guess I need not worry so much about getting all the mods to stop using older functions. (such as mod events using 'HookAnimationStart' instead of 'AnimationStart', and so on) Not sure which one you are saying is the deprecated on but just in case, the deprecated on is "AnimationStart." "Hook_____" are the new hook events, though the only real difference is that "HookAnimationStart" sends a more convenient set of arguments to the event instead of the arbitrary ones the old "AnimationStart" does. The new ones may or may not be a little bit faster as well, since the old ones are sent last. Indeed. I actually started this thread after stumbling into this one while searching as to why some new SL mods add "Hook" as a prefix for mod event registering.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.