I
Iros
Guest
New update v1.52: https://mega.nz/#!aQdXiZYA!aJnVbQH5kWSi5sC6QMdgPmjKmhfUdsP-87R70j90ub4
-Support audio preview (e.g. for music mod) in config screen
-Support tags in XML to specify load order rules, to say a mod should come before/after other mods
1) Audio preview files:
Add a attribute 'PreviewAudio' to your Option tags, e.g.
Code: [Select]
The file must exist in the mod of course. The audio does not play automatically, but the user can click a button to preview what that music sounds like.
2) Specify mod ordering:
Add tags to the mod like this:
Code: [Select]
This sets the mod to say it must come AFTER a particular other mod in the load order, and BEFORE another mod in the load order.
If the other mods are not active, it will not complain at all. But if they are, it will warn the user if the order is not correct.
For now, it will only warn, not try and correct the order. That may come later. It is not super simple because if lots of mods have order constraints, there may not be a correct order, and it can be complicated to calculate.
@EQ2Alyza: I expect you will make the most use of these tags, let me know if you have any questions
@Insight: I would not suggest changing any of the XML formats as the core 7H libraries use them internally. Of course perhaps we will add new fields in the future.
@Eeketh: Not sure there is much to be done right now? Thank you for the offer of help though. There are probably many other tools that could use some coding help though. Perhaps it is a good idea to ask mod authors what tools would help them.
-Support audio preview (e.g. for music mod) in config screen
-Support tags in XML to specify load order rules, to say a mod should come before/after other mods
1) Audio preview files:
Add a attribute 'PreviewAudio' to your Option tags, e.g.
Code: [Select]
Code:
<Option Value="0" Name="Orchestral" PreviewFile="preview\orchestral.png" PreviewAudio="orch\jukai.ogg"/><Option Value="1" Name="Lifestream" PreviewFile="preview\lifestream.png" PreviewAudio="ls\ayasi.ogg"/>
2) Specify mod ordering:
Add tags to the mod like this:
Code: [Select]
Code:
<OrderConstraints> <Before>73271161-6402-46a9-8cd8-72bf3c19a9c5</Before> <After>bc6f1dec-5cef-4f16-934e-4959aca1ea57</After> </OrderConstraints>
If the other mods are not active, it will not complain at all. But if they are, it will warn the user if the order is not correct.
For now, it will only warn, not try and correct the order. That may come later. It is not super simple because if lots of mods have order constraints, there may not be a correct order, and it can be complicated to calculate.
@EQ2Alyza: I expect you will make the most use of these tags, let me know if you have any questions
@Insight: I would not suggest changing any of the XML formats as the core 7H libraries use them internally. Of course perhaps we will add new fields in the future.
@Eeketh: Not sure there is much to be done right now? Thank you for the offer of help though. There are probably many other tools that could use some coding help though. Perhaps it is a good idea to ask mod authors what tools would help them.