| Last updated | 2 weeks ago |
| Total downloads | 626 |
| Total rating | 1 |
| Categories | Tweaks Networked Integration Assets Minis Props |
| Dependency string | LordAshes-CoreAssetsPlugin_CCM-2.0.0 |
| Dependants | 0 other packages depend on this package |
This mod requires the following mods to function
bbepisTaleSpire-BepInExPack
Unified BepInEx all-in-one modding pack - plugin framework, detour library
Preferred version: 5.4.10
LordAshes-FileAccessPlugin
Provides standardized methods for accessing both local file and url resources. Automatically handles searching local folders for assets.
Preferred version: 1.7.1
LordAshes-CommonCustomsMenuPlugin
Common menu for custom content plugins to register with.
Preferred version: 1.0.10
LordAshes-ReflectionPlugin
Provides reflection helpers to operate using types without needing to reference their assemblies at runtime.
Preferred version: 1.0.3README
Core Assets Plugin
This unofficial TaleSpire pluigin provides a Common Customs Menu (CCM) version of core Talespire Creature and Prop assets. Props spawned this way will spawn as mini converted props (i.e. movable with bases).
Install
Use R2ModMan or similar installer to install this asset pack.
Configuration
The plugin does not automatically extract portraits since this is normally a lengthy process. Instead a standalone executable
is provided to generate the core portraits. The executable, ExtractPortraits.exe, can be found in the plugin installation
folder. To run it, open a command prompt in the plugin installation folder and then execute the following command:
ExtractPortraits "TaleweaverFolder" "PluginsInstallFolder"
For example:
ExtractPortraits "E:\SteamLibrary\steamapps\common\TaleSpire\Taleweaver" "E:\r2modman\games\TaleSpire\profiles\RPG\BepInEx\plugins"
This will start the portrait extraction process. This process needs to be run only once unless BR adds more assets.
Usage
Core assets are included in the Common Customs Menu (CCM). Use the CCM menu to spawn them like any other CCM assets.
Registration
Registering assets is a length process. If all core assets where registered (or even checkede) on session startup, session startup would be significantly delayed. However, once registered, there isn't any need to re-regsiter the assets each time since the assets only change if BR adds more assets.
As such, the first time the plugin is run, it will register all core assets but then toggle the "Register missing assets" setting to false. This means that on successive starts, it will not bother to re-register the core assets since they were already registered and unlikely to have changed. When BR deploys additional assets, just go into the settings for this plugin, flip the "Register missing assets" to true and the plugin will re-regsiter all core assets on the next start. After that, it will, once again, toggle that setting to false so that succesive session starts don't re-register the assets again.
