File information

Last updated

Original upload

Created by

Heromaster Antono and CGi

Uploaded by


Virus scan

Safe to use

About this mod

The APPS - Framework is a collection of tools and settings mainly aimed for modders while allowing players to change how mods interact with the functionality this framework is providing. The current release is a beta version.

Permissions and credits

Info Manager
For modders:
This module allows you to make use of a more convenient way to push infos, warnings and errors from your mod through the framework. You can choose what kind of messages you want to provide and how you want to provide them.

For players:
For each and every mod which is redirecting messages through the framework you can set up how you want to be informed. You can just accept what the mod author has set up or change the settings to your liking.
You are even able to completely disable logging for your game session (a game session is valid until closing the game) while in-game. So, if you want just to play and don't care about any error output you can do so. And if you change your mind you can also turn it back on, on the fly.

Init/Uninstall Manager

For modders:
If your mod needs to set up some things before it can be fully activated, you can pass the framework your init quest. It will then be displayed for the player in the MCM menu in a list, together with all the other init quests from other mods. The ordering of this list can be easily changed through the menu. Mods' init quests will be chained and called one after another to allow for a more safe way to init your mod.

You can be sure that every mod, which allows their initialization process to be handled by the framework, does not interfere with your initialization. You can also provide a tooltip to let the player know if your mod needs to be placed in a specific order.

The more mods support this way of initializing , the less bugs will happen through this critical stage of the mod because it will be more unlikely that the Papyrus engine will skip some of the code due to technical reasons. Also, since the player can set up them in a specific order (and if the order is setup the way your mods need it) you can make sure that your mod will be installed after or before certain mods, if you require it.

You can also provide the framework with an uninstall quest so you don't have to write an extra MCM menu just for deinstalling your mod.

For players:
You can change the order in which mods should be initialized. You can build an initialization chain for them or you can manually initialize them. You have control over when these mods should be initialized.

Relationship module

For modders:
This module allows you to create versatile relationships and combine it with the Skyrim's internal relationship system. Or you can decide to make those working independent from each other.Relationship points are from -499 to 499 and represent a similar structure as the vanilla system. With this module you are able to add or subtract relationship points which are calculated against a multiplier. The default multiplier value going from 0 - 100/-100 is 1.0 while from 100 to 200/-100 to -200 is 0.5. That means if you add 100 points to an actor this would result in 100 points if the current rank is 0 and 50 points if the current rank is 1.

You can set a sync mode between this system and the vanilla system. Values are: 0 - disabled, 1 - from RS mod to vanilla only, 2 - from vanilla to RS only, 3 - both ways. The sync mode can be set globally which will then be applied to every actor. You also can set on specific actors which does overwrite the global setting.For example: You set global sync mode to 0 but also set a local sync mode for Heimskr to 3. The local value wins and ignores the global value.You also can fine tune the relationship multipliers globally/locally. Same rules applies as above. A multiplier must be a positive float number and can be set for each rank to rank.

All those settings are regulated by priorities. You can change the values as you like, but if your mod has not the highest priority, your changes will not be applied. The user decides, which mod he wants to have the highest priority. Your values will be saved and when the priority order changes and your mod is now on the highest priority your changes will be applied immediatly w/o needing an interaction from your mod. Only one mod can have the highest priority at all time. Let's say there is Mod A and Mod B. Mod A has the highest priority and changes local relationship multipliers on different actors, nothing else. Mod B changes the global relationship multiplier and a local relationship multiplier which conflicts with one of the changes of Mod A. What happens now, that the global relationship multiplier will be applied from Mod B (because Mod A hasn't set any global relationship multipliers) and all of the local relationship multipliers are applied by Mod A including the one which conflicts with Mod B.


You can change the relationship points two ways: One way is with the function ModRelationshipPoints() which applies the multiplier and the second one is by using the function SetRelationshipPoints() which sets the relationship to to passed value w/o modifiers.

You also can ask the framework for how many relationship points are needed for the next or previous rank.Those functions can be used by any mods w/o registering to the module in the first place. You only need to register your mod if you are planning to change the default settings.

For players:
You can set up the priority order and have the control about which mod should change the values. In the next mini releases we will work on the MCM menu, where you can see, what the mods do change exaclty and use those informations to arrange the priority order.


The documenation can be seen here: Documentation