Frictional Wiki - User contributions [en]

AMFP Asset pack installation and usage

2024-01-13T13:38:03Z

KiraImmortal: /* Links: */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents (Non Omnis Moriar demo):===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but had to be manually copied into each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

=='''Releasing a Mod:'''==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

<u>'''More asset packs on the workshop:'''</u>

- Amadeus assets (Reminiscity): https://steamcommunity.com/sharedfiles/filedetails/?id=3124494981

- In Lucy's eyes assets (Redline Games): https://steamcommunity.com/sharedfiles/filedetails/?id=3126000385

That should be it, cheers and happy modding!

AMFP Asset pack installation and usage

2024-01-13T13:37:33Z

KiraImmortal: /* Links: */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents (Non Omnis Moriar demo):===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but had to be manually copied into each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

=='''Releasing a Mod:'''==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

More asset packs on the workshop:

- Amadeus assets (Reminiscity): https://steamcommunity.com/sharedfiles/filedetails/?id=3124494981

- In Lucy's eyes assets (Redline Games): https://steamcommunity.com/sharedfiles/filedetails/?id=3126000385

That should be it, cheers and happy modding!

LucysEyes Asset pack installation and usage

2024-01-10T15:41:02Z

KiraImmortal:

<big>'''These assets are the property of Juras Rodionovas and Redline Games. Some sounds are the work of NiksonX, Ghost Lady edits were made by Reminiscity. Make sure to credit the authors if you're using their work through this package!'''</big>

=='''In Lucy's Eyes asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Lucy assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3126000385'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 patch beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3126000385" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story / moddb release, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Lucy, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

Amadeus Asset pack installation and usage

2024-01-10T15:40:39Z

KiraImmortal: /* Releasing a Mod: */

<big>'''These assets are the property of Reminiscity. Additional music made by Kevin Macleod and Krzysztof Penderecki. Make sure to credit the authors if you're using their work through this package!'''</big>

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3124494981'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 patch beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story / moddb release, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

Amadeus Asset pack installation and usage

2024-01-10T15:40:07Z

KiraImmortal:

<big>'''These assets are the property of Reminiscity. Additional music made by Kevin Macleod and Krzysztof Penderecki. Make sure to credit the authors if you're using their work through this package!'''</big>

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3124494981'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 update beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story / moddb release, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

LucysEyes Asset pack installation and usage

2024-01-10T15:39:45Z

KiraImmortal:

<big>'''These assets are the property of Juras Rodionovas and Redline Games. Some sounds are the work of NiksonX, Ghost Lady edits were made by Reminiscity. Make sure to credit the authors if you're using their work through this package!'''</big>

=='''In Lucy's Eyes asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Lucy assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3126000385'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 update beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3126000385" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story / moddb release, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Lucy, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

LucysEyes Asset pack installation and usage

2024-01-10T15:36:03Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

<big>'''These assets are the property of Juras Rodionovas and Redline Games. Some sounds are the work of NiksonX, Ghost Lady edits were made by Reminiscity. Make sure to credit the authors if you're using their work through this package.'''</big>

=='''In Lucy's Eyes asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Lucy assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3126000385'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 update beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3126000385" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story / moddb release, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Lucy, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

Amadeus Asset pack installation and usage

2024-01-10T15:35:36Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

<big>'''These assets are the property of Reminiscity. Additional music made by Kevin Macleod and Krzysztof Penderecki. Make sure to credit the authors if you're using their work through this package.'''</big>

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3124494981'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 update beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story / moddb release, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

AMFP Asset pack installation and usage

2024-01-10T15:34:57Z

KiraImmortal:

HPL2/Third party tools

2024-01-10T15:33:30Z

KiraImmortal: /* Asset pack / Dependencies (Steam Workshop) */

=Third Party Tools=

Information on some of the third-party tools that can be used to create models, graphics and art for the game and what specific things you will need to setup to make it all work.

==COLLADA==

All 3D models regardless of program used must be able to export to the [http://collada.org Collada] format.

Note: The 1.3 patch for Amnesia allows support for [http://en.wikipedia.org/wiki/FBX FBX] formats.

==3D Programs==

#[[Blender]] - Open-source 3D modeling program that comes with built-in support for [http://collada.org Collada].
#[[Autodesk_Maya|Autodesk Maya]] - Professional 3D modeling program with [https://collada.org/mediawiki/index.php/OpenCOLLADA OpenCOLLADA] plugin support.

==2D programs==

#[[GIMP]] - Open-source 2D '''G'''NU '''I'''mage '''M'''anipulation '''P'''rogram.
#[https://krita.org/ Krita] - a free and open source image editing program with focus on painting. It is more similar to Photoshop than GIMP.
#[[Adobe_Photoshop|Adobe Photoshop]] - Professional image editing software.
#[[Paint.NET|Paint.net]]

==Audio programs==

#[[Audacity]]

==Text/Script coding programs==

#[[Notepad%2B%2B|Notepad++]]: Advanced text editor, crucial for script writing.
#[[Geany|Geany]]: An alternative for Notepad++.

'<nowiki/>''Mac OS X alternatives'<nowiki/>''''':'''

#[[:hpl2:third_party_tools:text:textwrangler|TextWrangler]]: A good alternative to Notepad++ on Windows.
#[[TextMate|TextMate]]: A nice and smooth code editor with many customization options.

==Script examples/source code==

#[[HPL2/HPL2_Helper_Scripts|HPL2 Helper Scripts]] is a package of .hps files containing script classes and functions that may be useful to HPL2 modders and custom story creators, for ATDD version 1.5 and later.

==Asset pack / Dependencies (Steam Workshop)==

#[[AMFP_Asset_pack_installation_and_usage| AMFP Asset pack installation and usage]] - A complete package of assets unique to the machine for pigs, exactly as they work in aforementioned game, with minimal overhauls and quality of life improvements. Now fully integrated into the 1.5 update steam workshop functionality.
#[[Amadeus_Asset_pack_installation_and_usage| Amadeus asset pack details]]
#[[LucysEyes_Asset_pack_installation_and_usage| In Lucy's Eyes asset pack details]]

LucysEyes Asset pack installation and usage

2024-01-10T15:32:51Z

KiraImmortal:

<big>'''These assets are the property of Juras Rodionovas and Redline Games. Some sounds are the work of NiksonX, Ghost Lady edits were made by Reminiscity. Make sure to credit the authors if you're using their work through this package.'''</big>

=='''In Lucy's Eyes asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Lucy assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3126000385'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 update beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3126000385" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Lucy, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

LucysEyes Asset pack installation and usage

2024-01-10T15:32:35Z

KiraImmortal:

<big>'''These assets are the property of Juras Rodionovas and Redline Games. Some sounds are the work of NiksonX, Ghost Lady edits were made by Reminiscity. Make sure to credit the authors if you're using their work through this package'''</big>

=='''In Lucy's Eyes asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Lucy assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3126000385'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 update beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3126000385" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Lucy, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

Amadeus Asset pack installation and usage

2024-01-10T15:31:59Z

KiraImmortal:

<big>'''These assets are the property of Reminiscity. Additional music made by Kevin Macleod and Krzysztof Penderecki. Make sure to credit the authors if you're using their work through this package.'''</big>

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3124494981'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 update beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

Amadeus Asset pack installation and usage

2024-01-10T15:31:30Z

KiraImmortal:

<big>'''These assets are the property of Reminiscity. Additional music made by Kevin Macleod and Krzysztof Penderecki. Make sure to credit the authors if you're using their work.'''</big>

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3124494981'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 update beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

LucysEyes Asset pack installation and usage

2024-01-10T15:30:10Z

KiraImmortal: /* In Lucy's Eyes asset pack installation and usage. */

<big>'''These assets are the property of Juras Rodionovas and Redline Games.'''</big>

=='''In Lucy's Eyes asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Lucy assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3126000385'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 update beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3126000385" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Lucy, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

LucysEyes Asset pack installation and usage

2024-01-10T15:28:25Z

KiraImmortal: Lucy's Eyes asset pack subpage created

=='''In Lucy's Eyes asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Lucy assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3126000385'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 update beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3126000385" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Lucy, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

HPL2/Third party tools

2024-01-10T15:26:23Z

KiraImmortal: /* Asset pack / Dependencies (Steam Workshop) */

Amadeus Asset pack installation and usage

2024-01-10T15:25:18Z

KiraImmortal: /* For more detailed information on workshop asset packs */

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3124494981'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 update beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for the complete explanation and showcase based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

Amadeus Asset pack installation and usage

2024-01-10T15:23:52Z

KiraImmortal: /* Releasing a Mod: */

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3124494981'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with 1.5 update beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for a full explanation and a showcased based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

Amadeus Asset pack installation and usage

2024-01-10T15:23:26Z

KiraImmortal: /* Releasing a Mod: */

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3124494981'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

=='''Releasing a Mod''':==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for a full explanation and a showcased based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

Amadeus Asset pack installation and usage

2024-01-10T15:22:34Z

KiraImmortal: /* Releasing a Mod: */

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3124494981'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for a full explanation and a showcased based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

Amadeus Asset pack installation and usage

2024-01-10T15:22:20Z

KiraImmortal: /* For more detailed information on workshop asset packs */

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3124494981'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the original AMFP asset pack page by KiraImmortal for a full explanation and a showcased based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

Amadeus Asset pack installation and usage

2024-01-10T15:20:53Z

KiraImmortal: /* Amadeus asset pack installation and usage. */

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from

inside the workshop folder into your main folder, it will overwrite nothing!

'''Path to the mod files are in:'''

'''''- Steam\steamapps\workshop\content\57300\3124494981'''''
===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the AMFP asset pack page by KiraImmortal for a full explanation and a showcased based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

Amadeus Asset pack installation and usage

2024-01-10T15:20:16Z

KiraImmortal: /* Amadeus asset pack installation and usage. */

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from
inside the workshop folder into your main folder, it will overwrite nothing!<blockquote>'''''Path to the mod files are in:'''''

'''''- Steam\steamapps\workshop\content\57300\3124494981'''''</blockquote>

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the AMFP asset pack page by KiraImmortal for a full explanation and a showcased based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

Amadeus Asset pack installation and usage

2024-01-10T15:19:13Z

KiraImmortal: Amadeus asset pack subpage created

=='''Amadeus asset pack installation and usage.'''==

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

If you are working on a project that would heavily depend upon Amadeus assets, feel free to unload all the content from
inside the workshop folder into your main folder, it will overwrite nothing!

Path to the mod files are in:
Steam\steamapps\workshop\content\57300\3124494981

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

- First, your resources must contain this line on top:

<code><Directory Path="../3124494981" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the Amadeus asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from Amadeus, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

=='''For more detailed information on workshop asset packs'''==

Visit the AMFP asset pack page by KiraImmortal for a full explanation and a showcased based on the asset pack itself:

https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage

HPL2/Third party tools

2024-01-08T16:43:39Z

KiraImmortal: /* Asset pack / Dependencies (Steam Workshop) */

=Third Party Tools=

Information on some of the third-party tools that can be used to create models, graphics and art for the game and what specific things you will need to setup to make it all work.

==COLLADA==

All 3D models regardless of program used must be able to export to the [http://collada.org Collada] format.

Note: The 1.3 patch for Amnesia allows support for [http://en.wikipedia.org/wiki/FBX FBX] formats.

==3D Programs==

#[[Blender]] - Open-source 3D modeling program that comes with built-in support for [http://collada.org Collada].
#[[Autodesk_Maya|Autodesk Maya]] - Professional 3D modeling program with [https://collada.org/mediawiki/index.php/OpenCOLLADA OpenCOLLADA] plugin support.

==2D programs==

#[[GIMP]] - Open-source 2D '''G'''NU '''I'''mage '''M'''anipulation '''P'''rogram.
#[https://krita.org/ Krita] - a free and open source image editing program with focus on painting. It is more similar to Photoshop than GIMP.
#[[Adobe_Photoshop|Adobe Photoshop]] - Professional image editing software.
#[[Paint.NET|Paint.net]]

==Audio programs==

#[[Audacity]]

==Text/Script coding programs==

#[[Notepad%2B%2B|Notepad++]]: Advanced text editor, crucial for script writing.
#[[Geany|Geany]]: An alternative for Notepad++.

'<nowiki/>''Mac OS X alternatives'<nowiki/>''''':'''

#[[:hpl2:third_party_tools:text:textwrangler|TextWrangler]]: A good alternative to Notepad++ on Windows.
#[[TextMate|TextMate]]: A nice and smooth code editor with many customization options.

==Script examples/source code==

#[[HPL2/HPL2_Helper_Scripts|HPL2 Helper Scripts]] is a package of .hps files containing script classes and functions that may be useful to HPL2 modders and custom story creators, for ATDD version 1.5 and later.

==Asset pack / Dependencies (Steam Workshop)==

#[[AMFP_Asset_pack_installation_and_usage| AMFP Asset pack installation and usage]] - A complete package of assets unique to the machine for pigs, exactly as they work in aforementioned game, with minimal overhauls and quality of life improvements. Now fully integrated into the 1.5 update steam workshop functionality.
#Amadeus asset pack details
#In Lucy's Eyes asset pack details

HPL2/Third party tools

2024-01-08T16:42:37Z

KiraImmortal: /* Asset pack / Dependencies (Steam Workshop) */

=Third Party Tools=

Information on some of the third-party tools that can be used to create models, graphics and art for the game and what specific things you will need to setup to make it all work.

==COLLADA==

All 3D models regardless of program used must be able to export to the [http://collada.org Collada] format.

Note: The 1.3 patch for Amnesia allows support for [http://en.wikipedia.org/wiki/FBX FBX] formats.

==3D Programs==

#[[Blender]] - Open-source 3D modeling program that comes with built-in support for [http://collada.org Collada].
#[[Autodesk_Maya|Autodesk Maya]] - Professional 3D modeling program with [https://collada.org/mediawiki/index.php/OpenCOLLADA OpenCOLLADA] plugin support.

==2D programs==

#[[GIMP]] - Open-source 2D '''G'''NU '''I'''mage '''M'''anipulation '''P'''rogram.
#[https://krita.org/ Krita] - a free and open source image editing program with focus on painting. It is more similar to Photoshop than GIMP.
#[[Adobe_Photoshop|Adobe Photoshop]] - Professional image editing software.
#[[Paint.NET|Paint.net]]

==Audio programs==

#[[Audacity]]

==Text/Script coding programs==

#[[Notepad%2B%2B|Notepad++]]: Advanced text editor, crucial for script writing.
#[[Geany|Geany]]: An alternative for Notepad++.

'<nowiki/>''Mac OS X alternatives'<nowiki/>''''':'''

#[[:hpl2:third_party_tools:text:textwrangler|TextWrangler]]: A good alternative to Notepad++ on Windows.
#[[TextMate|TextMate]]: A nice and smooth code editor with many customization options.

==Script examples/source code==

#[[HPL2/HPL2_Helper_Scripts|HPL2 Helper Scripts]] is a package of .hps files containing script classes and functions that may be useful to HPL2 modders and custom story creators, for ATDD version 1.5 and later.

==Asset pack / Dependencies (Steam Workshop)==

#[[HPL2/AMFP_Asset_pack_installation_and_usage| AMFP Asset pack installation and usage]] - A complete package of assets unique to the machine for pigs, exactly as they work in aforementioned game, with minimal overhauls and quality of life improvements. Now fully integrated into the 1.5 update steam workshop functionality.
#Amadeus asset pack details
#In Lucy's Eyes asset pack details

HPL2/Third party tools

2024-01-08T16:40:53Z

KiraImmortal: /* Asset pack / Dependencies (Steam Workshop) */

=Third Party Tools=

Information on some of the third-party tools that can be used to create models, graphics and art for the game and what specific things you will need to setup to make it all work.

==COLLADA==

All 3D models regardless of program used must be able to export to the [http://collada.org Collada] format.

Note: The 1.3 patch for Amnesia allows support for [http://en.wikipedia.org/wiki/FBX FBX] formats.

==3D Programs==

#[[Blender]] - Open-source 3D modeling program that comes with built-in support for [http://collada.org Collada].
#[[Autodesk_Maya|Autodesk Maya]] - Professional 3D modeling program with [https://collada.org/mediawiki/index.php/OpenCOLLADA OpenCOLLADA] plugin support.

==2D programs==

#[[GIMP]] - Open-source 2D '''G'''NU '''I'''mage '''M'''anipulation '''P'''rogram.
#[https://krita.org/ Krita] - a free and open source image editing program with focus on painting. It is more similar to Photoshop than GIMP.
#[[Adobe_Photoshop|Adobe Photoshop]] - Professional image editing software.
#[[Paint.NET|Paint.net]]

==Audio programs==

#[[Audacity]]

==Text/Script coding programs==

#[[Notepad%2B%2B|Notepad++]]: Advanced text editor, crucial for script writing.
#[[Geany|Geany]]: An alternative for Notepad++.

'<nowiki/>''Mac OS X alternatives'<nowiki/>''''':'''

#[[:hpl2:third_party_tools:text:textwrangler|TextWrangler]]: A good alternative to Notepad++ on Windows.
#[[TextMate|TextMate]]: A nice and smooth code editor with many customization options.

==Script examples/source code==

#[[HPL2/HPL2_Helper_Scripts|HPL2 Helper Scripts]] is a package of .hps files containing script classes and functions that may be useful to HPL2 modders and custom story creators, for ATDD version 1.5 and later.

==Asset pack / Dependencies (Steam Workshop)==

#[[https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage| AMFP Asset pack installation and usage]] - A complete package of assets unique to the machine for pigs, exactly as they work in aforementioned game, with minimal overhauls and quality of life improvements. Now fully integrated into the 1.5 update steam workshop functionality.
#Amadeus asset pack details
#In Lucy's Eyes asset pack details

HPL2/Third party tools

2024-01-01T18:11:51Z

KiraImmortal: /* Asset pack / Dependencies (Steam Workshop) */

=Third Party Tools=

Information on some of the third-party tools that can be used to create models, graphics and art for the game and what specific things you will need to setup to make it all work.

==COLLADA==

All 3D models regardless of program used must be able to export to the [http://collada.org Collada] format.

Note: The 1.3 patch for Amnesia allows support for [http://en.wikipedia.org/wiki/FBX FBX] formats.

==3D Programs==

#[[Blender]] - Open-source 3D modeling program that comes with built-in support for [http://collada.org Collada].
#[[Autodesk_Maya|Autodesk Maya]] - Professional 3D modeling program with [https://collada.org/mediawiki/index.php/OpenCOLLADA OpenCOLLADA] plugin support.

==2D programs==

#[[GIMP]] - Open-source 2D '''G'''NU '''I'''mage '''M'''anipulation '''P'''rogram.
#[https://krita.org/ Krita] - a free and open source image editing program with focus on painting. It is more similar to Photoshop than GIMP.
#[[Adobe_Photoshop|Adobe Photoshop]] - Professional image editing software.
#[[Paint.NET|Paint.net]]

==Audio programs==

#[[Audacity]]

==Text/Script coding programs==

#[[Notepad%2B%2B|Notepad++]]: Advanced text editor, crucial for script writing.
#[[Geany|Geany]]: An alternative for Notepad++.

'<nowiki/>''Mac OS X alternatives'<nowiki/>''''':'''

#[[:hpl2:third_party_tools:text:textwrangler|TextWrangler]]: A good alternative to Notepad++ on Windows.
#[[TextMate|TextMate]]: A nice and smooth code editor with many customization options.

==Script examples/source code==

#[[HPL2/HPL2_Helper_Scripts|HPL2 Helper Scripts]] is a package of .hps files containing script classes and functions that may be useful to HPL2 modders and custom story creators, for ATDD version 1.5 and later.

==Asset pack / Dependencies (Steam Workshop)==

#[[https://wiki.frictionalgames.com/page/AMFP_Asset_pack_installation_and_usage|AMFP Asset pack installation and usage]] - A complete package of assets unique to the machine for pigs, exactly as they work in aforementioned game, with minimal overhauls and quality of life improvements. Now fully integrated into the 1.5 update steam workshop functionality.
#Amadeus asset pack details
#In Lucy's Eyes asset pack details

AMFP Asset pack installation and usage

2023-12-27T17:36:59Z

KiraImmortal: /* If you want to release on Steam Workshop: */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents (Non Omnis Moriar demo):===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but had to be manually copied into each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Third and final step, on the Workshop release add the Asset pack (easiest from your Subscribed Items) in the "Add/Remove Required Items" section, so the player is aware of its necessity!

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:34:53Z

KiraImmortal: /* Showcase mod contents (Non Omnis Moriar demo): */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents (Non Omnis Moriar demo):===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but had to be manually copied into each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:34:17Z

KiraImmortal: /* Showcase mod contents: */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents (Non Omnis Moriar demo):===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:16:27Z

KiraImmortal: /* Releasing a Mod: */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:14:01Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work well.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:13:40Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae / .fbx - the static model file. Animated models usually have an "animations" folder with more files inside that you might wanna grab for it to work as intended.
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:12:48Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae - the static model file
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material/materials to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:12:02Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae - the static model file
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called
"<init_from>" to see which material to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:11:50Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae - the static model file
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called "<init_from>" to see which material to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:11:37Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae - the static model file
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

Note that some models use multiple materials (and assigned textures). You can try opening the .dae file with notepad/notepad++ and search for a section called "<init_from>" to see which material to look for. For FBX files, I recommend using a Hex editor (search for "material") or a modelling program such as Blender or Maya to find this reference.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:08:57Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae - the static model file
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:08:30Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae - the static model file
- .msh - is a generated file by the engine, you can grab it but not necessary
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included for in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:07:59Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae - the static model file
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture "layers" usually included for in a model's material, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more or some are not needed.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:06:49Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore most of the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae - the static model file
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture layers usually included for a model, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:06:33Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore all the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom asset usually needs these files to work, so be sure to check if you have all for every singular asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae - the static model file
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture layers usually included for a model, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:06:13Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore all the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom assets usually needs these files to work, so be sure to check if you have all for the asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae - the static model file
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture layers usually included for a model, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:06:01Z

KiraImmortal: /* If you only want to create a simple custom story, this pack might still help you! */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore all the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

A custom assets usually needs these files to work, so be sure to check if you have all for the asset you copy:
- .ent - the entity itself if the asset has any, this includes any in game interaction
- .dae - the static model file
- .mat - the material file (you can open with notepad to check for all the texture files needed)
- "example.dds", "example_nrm.dds", "example_spec.dds" are the texture layers usually included for a model, each have unique filenames, but this is usually the format baseline. You might want to check the .mat if there is more.

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T17:03:14Z

KiraImmortal: /* NOTE: The asset pack dependency setup ONLY works for: */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no regular custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore all the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T02:24:29Z

KiraImmortal: /* If you want to release on Steam Workshop: */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always resets your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore all the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T02:24:07Z

KiraImmortal: /* If you want to release on Steam Workshop: */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. IMPORTANT, that the Workshop always reset your mod's description on each update, make sure to BACK IT UP before you reupload!

There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore all the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!

AMFP Asset pack installation and usage

2023-12-27T01:28:16Z

KiraImmortal: /* If you want to release on Steam Workshop: */

=='''Welcome to my page and modding instructions for my asset pack.'''==

'''Thank you for taking interest, and I will format and update this as we go based on feedback.'''

I will be taking into account that you have modded TDD before, so you know how to work with custom assets and how to put a basic Full Conversion mod together.
If that is not the case I suggest you delve into some youtube tutorials first, before attempting to use this pack.

By using this pack, you seemlessly integrate it as an existing outside source/dependency into your own project.

===='''NOTE''': The asset pack dependency setup ONLY works for:====
- Total Conversion / Full Conversion mods being able to browse outside resources (no custom stories sadly, but check the bottom of the page)
- You need to own a Steam version of the game that is automatically updated to 1.5 patch, and you download the assets from the Workshop. This is advised, but not the only one supported!
- For 1.4 version and earlier means you create mods for retail / other online stores. Download and use the MODDB version instead!

=='''Asset Pack contents:'''==
Let's break down what the asset pack itself entails:
"Billboards, Entities, Graphics, Lights, Misc, Music, Particles, Sounds, Statics and Textures" are all included from the source game.
- They contain no duplicates with the base game of Dark Descent. Unloading these folders straight into your modding installation will produce no overwrites!
- Mostly they work identical to their AMFP counterparts, with some more interactions and expansions added.

"Scripts" folder contains some customly recreated script functions of AMFP. It's currently very makeshift and brief, but you can either:
- Copy these into your level scripts to ease creating AMFP-esque gameplay.
- Include the whole hps (only works with 1.5 update) by adding the #include "amfp_common_functions.hps" somewhere in your level hps, and call any of its functions as they were part of the same script file
- In the moddb version it also contains an example bat file on how to make the pack required for your mod to launch. Simply replace "your_mod" with the name of your mod's folder

===Showcase mod contents:===

'''There is a Showcase mod that contains more files for a FC/TC mod that would want to be even more authentic to AMFP gameplay.'''
- Ported, playable levels from my older AMFP project, that make use of the 1.5 update functions, compiled script libraries (such as: "amfp_common_functions" from the base asset pack's "scripts" folder) and the provided assets in general.
- For the moddb version, these same scripts exist, but you need to manually copy them in each level hps. The one specific 1.5 update function used is recreated with custom logic

====Files that overwrite base game variants when used in a TC environment:====
- Config folder has unique entries, see "baselang_amfp/base_english.lang", "game_amfp.cfg", "menu_amfp.cfg" files for exact changes. They contain authentic language entries, mechanics altered to AMFP such as no sanity vision, lantern consuming no oil and so on
- Fonts and Gui contain the AMFP variants so the same authentic menu can be created.
- Graphics folder contain UI elements for Hud, Inventory, Journal and so on to replace the base game's look (and some custom ones)
- Lang folder lets you find the AMFP menu logo, ready to be used
- Misc folder contains a custom sanity event to recreate the ShowScreenImage function from AMFP and the TDD 1.5 update, see the moddb version for its usage in the first level hps.
- Models contain the Mandus hand and lantern models to be used instead of Daniel's
- Particles feature the "blood smoke" effect to be used when enemy hallucinations disappear (and a few custom ones)
- Shaders are from AMFP as well, for a more authentic look on entity highlights and such
- Sounds contain the overwritten footsteps, joints and player sounds (alonside custom ones)
- The rest of the folders only contain custom content for the showcase mod itself

===Version differences:===
- Steam Version of the mod contains new functionalities such as built in dependency for the asset pack itself that the workshop can then auto-download for the player. It uses unique new functionalities from 1.5 patch, such as custom story config browsing, script outsourcing (ex: "amfp_common_functions.hps") and ShowScreenImage function.
- The Moddb version of the downloads are based on 1.3 or 1.4 patch. Which means if you want your mod to be available outside of the Steam Workshop you should set it up with this version as well. 1.5 script functions are removed, and outside scripts are integrated into each level's script file.
IT DOESN'T MATTER which version of the assets you put into your modding installation and make your levels with. What matters is which version do you release your mod for, and how you set it up. See below!

==Releasing a Mod:==
Let's say you got the assets working, and you have a working mod, ready to be released or tested. So how do you release it?

==='''If you want to release on Moddb for retail/other online store versions:'''===
Once again, if you haven't been actively creating FC mods before, this tutorial helps setting up a full conversion mod: https://www.youtube.com/watch?v=t1d6NyWruTY&t=1190s&ab_channel=Mudbill

- You need to have these 2 lines on top of your resources.cfg:

<code><Directory Path="/NonOmnisMoriar_TDD" AddSubDirs="true" />
<Directory Path="/amfp_assets" AddSubDirs="true" /></code>

- Additionally, you should use the example bat file to launch your "main_init.cfg" that contains a reference to this resource file.
If the player have both the asset pack and your mod downloaded, the bat file will let them play instantly, otherwise warning them to download the assets as well

- Check the "resources_amfp.cfg" in the Moddb version of Non Omnis Moriar for reference.

==='''If you want to release on Steam Workshop:'''===
I recommend browsing through this page to understand the update and how to set up a TC mod with it beforehand: https://wiki.frictionalgames.com/page/HPL2/1.5_Update

This gets a bit tricky here, bear with me.

- First, your resources must contain this line on top:

<code><Directory Path="../3123410893" AddSubDirs="true" /></code>

This is the relative path to the workshop downloads folder, and the online ID of the AMFP asset pack itself. This is ALWAYS THE SAME.

- Second, you need to add a dependency to your own mod's assets:

Before you can do this my way, you need to upload your mod through the WorkshopUploader exe. This nets you an online ID for your mod itself. It should look something like this: https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472
That id part "?id=3123452472" is what you need. The mod's ID in this case is: "3123452472".

Put this ID with a relative path the same way you did with the asset pack's, on the very top above it.
So with our example it looks like this:
<Directory Path="../3123452472" AddSubDirs="true" />

So if you have both of these relative paths on top of resources, and you upload this small update to your mod, the assets and the mod should now work perfectly, and ready to be set to Public. There might be easier ways to this, but this is a foolproof method I found that worked perfectly for my own release.

- Check the "resources_amfp.cfg" in the Steam Workshop version of Non Omnis Moriar once again for reference.

=='''If you only want to create a simple custom story, this pack might still help you!'''==
- You should ignore all the jargon above, and just take what you need from the pack, and include them in your own mod's files like you would do originally. I still recommend using this pack over grabbing the assets yourself from AMFP, as it's more organized here. But be sure TO COPY EVERY NEEDED FILE MANUALLY in this case!

==Links:==

No matter where you came from to this page, I will link you all the downloads down here:

- AMFP Asset pack (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123410893

- Showcase mod with FC overwrites (Steam Workshop release): https://steamcommunity.com/sharedfiles/filedetails/?id=3123452472

- AMFP Asset pack and Showcase level (Moddb version): https://www.moddb.com/mods/machine-for-pigs-asset-pack-for-tdd

PS: Holidays were busy. Please give me a bit of time to improve these instructions. Thanks, cheers!