Curses
This mod is currently in an alpha release. It shouldn't crash your game, but it might not work 100% of the time. I'm still testing. Catch me on the discord @divisionbyzorro
This mod adds difficulty modifiers (curses) to your runs. Some are simple, like reducing the items you get from events on the map. Others are complex, such as randomly adding deathcards to encounters (like the bounty hunters from Act 3).
Requirements
As with most mods, you need BepInEx installed. There are no other requirements.
Installation
The zip file should be structured in the same way as your Inscryption root directory. Just drop the 'BepInEx' folder into your Inscryption directory and you're golden.
Changelog
Changelog
0.3.1
- Fixed defect where unpaused audio would sometimes come back too loud.
0.3.0
- Added 'Curse of Loose Teeth' and 'Curse of Chaos'
- Fixed defect where audio would sometimes not properly resume after deathcards appear in battle
- Improved how 'Curse of the Lone Candle' interacts with boss sequences.
- Curse selection now happens after drafting/starter deck selection and after side deck selection
0.2.1
- Fixed occasional crash when adding deathcards to battle plan
- Fixed random icons appearing on procedurally generated cards.
0.2.0
- Added the 'Curse of Haunted Pasts'
- Significantly improved the curse selection event
- Fixed a bug in the curse selection event where card backs were not displaying correctly.
0.1.1
- Updated asset loader to (hopefully) fix issues with Thunderstore mod manager.
0.1.0
- Initial version. Includes 'Curse of the Empty Backpack,' 'Curse of the Lone Candle', ' and 'Curse of the Empty Backpack'
What is a Curse?
A 'Curse' is a difficulty modification that changes the way the game plays. Each curse you take on increases the overall difficulty of your run. They are completely optional, but they clearly make you more of a badass for accepting them.
Curse of Haunted Pasts
Remember the bounty hunters from Act 3? Well, they're back, but flavorfully appropriate.
The game will track a 'haunt level' as you progress and win more battles. The higher the haunt level, the higher the chance that a random deathcard from the deathcard pool will be selected and inserted into battles that you fight.
Curse of Loose Teeth
You will take one damage at the start of every game.
Curse of the Empty Backpack
Backpack encounters now only gain you a single consumable, even if you have none.
Curse of the Lone Candle
This forces the player to only have a single candle flame available for the run.
You can't gain more from winning boss battles, and you also won't get smoke at boss battles.
Curse of the Strong Survivors
Campfire events are harder. If you've successfully upgraded a card previously, there's even a chance of failure on the first try. And failure costs you more than just a card.
Curse of Chaos
Opposing creatures will gain random abilities. This will not apply to every creature - only to those
However, you can also leave a campfire event without doing anything if you wish.
What if I want to program my own Curse?
Technical Stuff
I'll do my best to summarize it here:
- You need to create a new curse class that inherits from CurseBase.
- There are a number of abstract fields you have to implement:
- Title: This will display in the rulebook, prefixed with 'Curse Of'. So if you title your curse 'Flatulence,' the rulebook will refer to it as 'Curse Of Flatulence.'
- Description: This describes what the curse does and will appear in the rulebook.
- IconTexture: This is the icon that will appear in the middle of the curse card. It should be a 56x56 PNG. You can use AssetHelper to load it if you want, but AssetHelper will assume the PNG is in the 'Infiniscryption/assets' folder.
- Reset: This is incredibly important. This logic will run at the beginning of every run and whenever you leave the Curse selection node. If you need to do something at the start of the run, do it here (look at OneCandleMax to see how this is used).
- Do whatever patching you need to do to make your curse work.
- There is an instance variable called 'Active' which will tell you if your curse is active. If you're in a static method (like a patch), you can get the value of this flag using CurseManager.IsActive<T>, where T is the class name of the mod.
- I can't stress this enough. The framework does not check whether or not your curse is activated by the player - you have to do that! So if your curse makes the Mycologists put three copies of a card named 'Wet Fart' into your deck, you better make sure it only happens when that active flag is set.
- Register the curse using CurseManager.Register. This will also take care of any patches defined in your curse.
That should be enough. Once a curse is registered, the Curse node will automatically pick it up and display it as an option for the player. If they leave it turned up, the Active flag will be set to true.
