CrEaToXx Posted December 6, 2022 Share Posted December 6, 2022 Ints are internally converted to floats. All the engine does, if you catch a value by int, is to not count anything after the period. So technically it would look like that: "1.", while in Skyrim and SSE an int was an actual integer. F4SE isn't to blame. It's functions are still fully operational. The problem lies with MCM not properly making use of all F4SE functions, like it did for Skyrim. And I think the problem is rooted inside the .swf, not the .dll. At least that's my guess when I reviewed the action script in Adobe. Link to comment Share on other sites More sharing options...
RaidersClamoring Posted December 6, 2022 Share Posted December 6, 2022 Ints are internally converted to floats. All the engine does, if you catch a value by int, is to not count anything after the period. So technically it would look like that: "1.", while in Skyrim and SSE an int was an actual integer. F4SE isn't to blame. It's functions are still fully operational. The problem lies with MCM not properly making use of all F4SE functions, like it did for Skyrim. And I think the problem is rooted inside the .swf, not the .dll. At least that's my guess when I reviewed the action script in Adobe. This is good to know. Then I don't have to worry about using floats as shortcuts to formIDs, as when temp hijacking global variables and other assets that can only be floats (upfront). GetFormFromFile(MyOnlyOptionIsAFloat as int, PluginName) Link to comment Share on other sites More sharing options...
Recommended Posts