You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cabinet sorter currently relies mostly on external cabinet info files. Text Mod Loader does not have access to these, it needed to grab metadata from the mod file itself, thus the BLIMP Standard was born. It would be good for cabinet sorter to be able to read these tags too. BLIMP tags should probably be considered more authoritative than cabinet info files, as they're one step closer to the actual mod contents.
Text Mod Loader only uses the @author, @description, @main-author, @title, and @version tags, but while writing up the standard I included several other tags based on what's cabinet info files use. If need be we can still adjust the handling of these - @contact in particular's probably the most different.
The text was updated successfully, but these errors were encountered:
Heh, yeah, I knew that this was going to be on my plate shortly, if it wasn't already. :D
Indeed, for sure, I'll get working on this in the upcoming week. This would've been a good weekend for it but I took a little weekend trip and I'm not really codeable at the moment. WIll start taking a look shortly, though!
Cabinet sorter currently relies mostly on external cabinet info files. Text Mod Loader does not have access to these, it needed to grab metadata from the mod file itself, thus the BLIMP Standard was born. It would be good for cabinet sorter to be able to read these tags too. BLIMP tags should probably be considered more authoritative than cabinet info files, as they're one step closer to the actual mod contents.
Text Mod Loader only uses the
@author
,@description
,@main-author
,@title
, and@version
tags, but while writing up the standard I included several other tags based on what's cabinet info files use. If need be we can still adjust the handling of these -@contact
in particular's probably the most different.The text was updated successfully, but these errors were encountered: