Checks

The anatomy of the "checks" field:
	Whenever any data structure allows for a "checks" field it essentially allows for a huge amount of different effects to be coded in through the data itself. The "checks" field should contain an array [] of different dictionaries {}, each one representing a different effect that can be raised up to be handled by the game when its conditions are met. Let's take a look at a skill from the example mod:

	"checks": [{"trigger": "FLOOR_START", "ranks": [1], "requirements": {}, "check": "ALLY_GAIN_STATUS", "character": "self", "info": {"status": "ExampleMod1_SE_TeeOff", "duration": 1, "visible": true, "overwrite": "IGNORE"}}]

	This may look intimidating, but we can break it down.
	The whole thing is an array, or put more simply, a list of items contained in square brackets and separated by commas. There's only one entry in this array, so only one check. We can just ignore the outer [] in this case.
	That leaves us with a dictionary, which is a set of keys and values that is contained in braces and separated by commas. Removing the outer {} and separating out the pairs, we have:

	"trigger": "FLOOR_START",
	"ranks": [1],
	"requirements": {},
	"check": "ALLY_GAIN_STATUS",
	"character": "self",
	"info": {"status": "ExampleMod1_SE_TeeOff", "duration": 1, "visible": true, "overwrite": "IGNORE"}

	Here we can see that the "info" field also contains a dictionary which can also be further separated out. We'll get to that, but for now, we'll cover the more basic parts that can be in a check dictionary:

	"trigger": What type of event being raised could potentially cause this effect to activate?
	"ranks": What skill ranks can have this effect happen? (exclusive to skills)
	"requirements": What conditions need to be satisfied for this effect to activate beyond just matching the trigger type?
	"check": What type of check does this effect generate to raise and potentially activate other effects?
	"character": Who does this newly generated check target when it is raised?
	"info": What information needs to be passed on along with this check so that the game logic can handle it?

	And answering those questions from what we see in the data:

	What type of event being raised could potentially cause this effect to activate? The FLOOR_START event.
	What skill ranks can have this effect happen? Rank 1 only.
	What conditions need to be satisfied for this effect to activate beyond just matching the trigger type? The dictionary here is empty, so there are no conditions. (This isn't technically true, but we'll talk about that later)
	What type of event does this effect generate to raise and potentially activate other effects? It raises an ALLY_GAIN_STATUS check to be handled.
	Who does this effect target if it does activate? Self, or rather, the character who had this skill activate in the first place.
	What information needs to be passed on so that this specific effect can be handled by the game logic? The status effect, duration, visibility, and overwrite type.

	So there is a split there. The first three fields are saying WHEN the check should be raised, and the latter three are saying WHAT should be raised. While the order of fields doesn't matter, I tend to try and separate it like this.

	Whenever an event happens in game, a relevant check is generated and raised up. When the check is going to be handled by the game logic, the game first reaches out to every relevant entity and essentially says "a check of this type is happening, do you have anything that could be triggered as a result?" and evaluates all of those things first.

	So you start the game. The game gets a FLOOR_START check raised internally because you enter the dungeon. It takes that FLOOR_START check and looks at each ally (and other relevant entity) to see if they have anything that could trigger when FLOOR_START happens. An ally with this skill would indeed have something that could potentially trigger, because the skill has FLOOR_START as its trigger field. Seeing that, the game then evaluates a bit more. Does the ally have the right skill rank? Are the requirements met? There's only one rank of this skill and there are no requirements, so in this case, yes to both. Everything is correct, so the check should be generated and raised up now.

	A check with the type of ALLY_GAIN_STATUS is created. This check's character "self" is evaluated as the character who has the skill in the first place. The information in the info field is packaged into the check, and the whole thing is raised up just like the FLOOR_START check was earlier.

	The game then looks at each ally (and other relevant entity) to see if they have anything that could trigger when ALLY_GAIN_STATUS is happening. For the sake of example, we'll say that there are no further checks generated and raised here.

	So with that covered, the game can then use the info field to evaluate what it needs to when an ALLY_GAIN_STATUS type event is happening. Not to shock anyone, but it turns out this applies a status effect to the target ally. Which status effect? The one specified in the info field. For how long? The amount in the duration field. And so on.

	Once that ALLY_GAIN_STATUS check is all finished up and evaluated and the game has done everything it needs to with it, the check can be cleared away, and the game can continue on with anything it had left to do with the FLOOR_START check that triggered this whole thing. It finishes up looking at any remaining allies/entities, and then clears away the FLOOR_START check... And goes right into an ALLY_TURN_START check as game logic continues!

	Some of the more programming oriented people reading this probably looked at that above bit, recognized the last in first out nature and thought "stack", and you would be correct in doing so because that's literally what's happening. It's entirely possible that I could have saved a lot of time by just saying that but I wrote it the long way and you read it the long way and neither of us are getting our time back and I'm not even a little sorry.

	But anyway, knowing all of this now, I hope you can see how much power it gives to anything that has a "checks" field. Ninety-something percent of all status effects, skills, curses, spells, monster/trap status effects, and results of dungeon and camp event scenes use this format (there are some effects that are hard coded due to needing to touch the UI or do weird stuff which isn't the best but it is what it is). By that logic, being able to insert your own versions of those things and have them use the same system, you have ninety-something percent of the same power that I have to make an effect do the thing you want it to do! You just have to know what check types are available, when they are triggered, what information they need, and what they do. Easy, right?

	... Maybe not, but it should be possible to get a decent understanding.

	The following is a complete list of all the different check types that can be raised in the game along with what they do. There are also general guidelines for when you would want to trigger off of that type, or when you would want to raise a check of that type yourself, and a list of what fields are expected in the check information.

	TODO: Continue filling out the expected check info for all checks. It is only partially done.

	DUMMY
		Does nothing on its own. This is often used internally for effects that could trigger in multiple ways at once as a way to make sure that the associated text/icon/particle effect only plays once regardless of how many parts of it are triggered at the same time.
		Raise a check of this type if: You want access to some of the base UI functions of a check to happen without further logic.
		Trigger off of this check type if: Do not trigger off of DUMMY.
		Info:
			None
	CHANGE_TRIGGERING_CHECK_CHARACTER,
		Looks at the check that triggers this one and changes the character it is pointing at to the character that has this effect.
		Raise a check of this type if: You want an effect that changes the target of a parent check.
		Trigger off of this check type if: Do not trigger off of CHANGE_TRIGGERING_CHECK_CHARACTER.
		Example: I'll Cover You skill changes the target of a ALLY_COMBAT_ATTACKED check when triggered.
		Info:
			None (because at least currently, this check can only set the triggering check's target to the character who raises this check)
	CHANGE_TRIGGERING_CHECK_INFO_ADD,
		Looks at the check that triggers this one and changes the specified information to a new value by adding the evaluated amount.
		Raise a check of this type if: You want an effect to add to a field in the parent effect.
		Trigger off of this check type if: Do not trigger off of CHANGE_TRIGGERING_CHECK_INFO_ADD
		Info:
			info: String. The name of the field in the triggering check that is to be changed.
			amount: Amount*. The new value that the field in the triggering check should be set to.
	CHANGE_TRIGGERING_CHECK_INFO_VALUE,
		Looks at the check that triggers this one and changes the specified information to a new value.
		Raise a check of this type if: You want an effect to set the information in a parent effect to a static value.
		Trigger off of this check type if: Do not trigger off of CHANGE_TRIGGERING_CHECK_INFO_VALUE
		Info:
			info: String. The name of the field in the triggering check that is to be changed.
			value: Any type. The new value that the field in the triggering check should be set to.
	CANCEL_TRIGGERING_CHECK,
		Sets the check that triggers this one to be canceled after all checks that it triggers are finished evaluating.
		Raise a check of this type if: You want an effect to cancel another effect happening.
		Trigger off of this check type if: Do not trigger off of CANCEL_TRIGGERING_CHECK

	CHANGE_TRACKER_VALUE,
		Changes the value of the given status, skill, or curse information tracker to the given amount/value.
		This happens BEFORE further checks are triggered, meaning it cannot be canceled once raised.
		Raise a check of this type if: You want an effect to change the value of a tracker variable on this or any other status/skill/curse
		Trigger off of this check type if: You want an effect that does something when a status/skill/curse's tracking variable values have changed
		Example: Grace has an internal value for the number of Grace stacks which can be changed by triggering this check.
		Info:
			type: String, one of "status", "skill", or "curse". The type of entity that has the tracker to be changed.
			tracker: String. The name of the tracker field.
			amount: Amount*. The new value that the tracker should be set to.
	FLOOR_START,
		Triggers once per ally at the start of each dungeon floor. Does nothing on its own.
		Raise a check of this type if: Do not raise FLOOR_START manually.
		Trigger off of this check type if: You want an effect that happens exactly once to the ally at the start of a dungeon floor.
		Info:
			None
	ALLY_TURN_START,
		Triggers once at the start of a given ally's turn. Does nothing on its own.
		Raise a check of this type if: Do not raise ALLY_TURN_START manually.
		Trigger off of this check type if: You want an effect that happens at the start of each of the ally's turns.
		Info:
			None
	ALLY_HEAL_DAMAGE,
		Triggers when some effect indicates that an ally should heal a negative stat. If not cancelled, heals the ally in the given stat for the given amount, then raises an ALLY_DAMAGE_WAS_HEALED check.
		Raise a check of this type if: You want an effect to heal an ally.
		Trigger off of this check type if: You want an effect to happen immediately before an ally is going to heal.
		Info:
			stat: String, one of "Injury", "Exhaustion", "Lust", "Corruption_T", "Corruption_P". Which stat is taking damage.
			amount: Amount*. How much damage is being dealt.
	ALLY_DAMAGE_WAS_HEALED,
		Triggers after an ally has been made to heal a negative stat. Triggers any post-heal effects, then outputs the information about how much was healed to the event list UI.
		Raise a check of this type if: Do not raise ALLY_DAMAGE_WAS_HEALED manually.
		Trigger off of this check type if: You want an effect to happen only when an ally has been successfully healed.
		Info:
			None
	ALLY_TAKE_DAMAGE,
		Triggers when some effect indicates that an ally should take damage to a negative stat. If not cancelled, the ally gains the given amount in the given stat, then raises an ALLY_DAMAGE_WAS_TAKEN check.
		Raise a check of this type if: You want an effect to do damage to an ally.
		Trigger off of this check type if: You want an effect to happen immediately before an ally is going to take damage.
		Info:
			stat: String, one of "Injury", "Exhaustion", "Lust", "Corruption_T", "Corruption_P". Which stat is healing damage.
			amount: Amount*. How much damage is being healed.
	ALLY_DAMAGE_WAS_TAKEN,
		Triggers after an ally has been made to take damage in a negative stat. Triggers any post-damage effects, then outputs the information about how much damage was taken to the event list UI.
		Raise a check of this type if: Do not raise ALLY_DAMAGE_WAS_TAKEN manually.
		Trigger off of this check type if: You want an effect to happen only when an ally has successfully taken damage.
		Info:
			None
	ALLY_NEGATIVE_STAT_BREAK,
		Triggers automatically when an ally reaches 100 in a (non-corruption) negative stat. If not cancelled, sets temporary corruption to 0, adds break_amount to permanent corruption, heals the ally for 30 in all negative stats, and removes Well Rested. After that it raises an ALLY_NEGATIVE_STAT_BROKEN check.
		Raise a check of this type if: Do not raise ALLY_NEGATIVE_STAT_BREAK manually.
		Trigger off of this check type if: You want an effect to happen immediately before an ally is going to suffer a corruption break.
		Info:
			break_amount: Int. The amount of temporary corruption that is to be converted into permanent corruption.
	ALLY_NEGATIVE_STAT_BROKEN,
		Triggers after an ally has had a negative stat break. Triggers any post-break effects, then outputs information about the corruption break having happened to the event list UI.
		Raise a check of this type if: Do not raise ALLY_NEGATIVE_STAT_BROKEN manually.
		Trigger off of this check type if: You want an effect to happen only when an ally has suffered a corruption break.
		Info:
			None
	ALLY_GAIN_STATUS,
		Triggers when some effect indicates that an ally should be gaining a status effect. If not cancelled, applies the given status effect for the given duration with the given visibility using the given overwrite behavior, then raises an ALLY_GAINED_STATUS check.
		Raise a check of this type if: You want an effect to give an ally a status effect.
		Trigger off of this check type if: You want an effect that happens immediately before a status effect is granted to an ally.
		Info:
			status:
			duration:
			visible:
			overwrite:
	ALLY_GAINED_STATUS,
		Triggers after an ally has gained a new status effect. Triggers any post-status gain effects, then outputs information about the status being gained to the event list UI.
		Raise a check of this type if: Do not raise ALLY_GAINED_STATUS manually.
		Trigger off of this check type if: You want an effect to happen only when an ally has successfully gained a status effect.
		Info:
			None
	ALLY_STATUS_TICK,
		Triggers when a status effect is being made to decrease its duration. This can happen naturally at the start of an ally's turn or when an ally performs an action, depending on what kind of status effect it is. If not cancelled, decreases the duration of the given status effect by 1
		Raise a check of this type if: You want an effect to tick down the duration of an ally's status effect(s)
		Trigger off of this check type if: You want an effect to happen whenever an ally's status effect duration is decreasing.
		Info:
			status:
	ALLY_LOSE_STATUS,
		Triggers when some effect indicates that an ally should be losing a status effect. If not cancelled, it will look for the given status effect on the character. If it is found, its trackers will be removed, it and any of its associated particles will be made invisible, then it will be removed. After that it will create an ALLY_LOST_STATUS check.
		Raise a check of this type if: You want an effect to remove a status effect from an ally.
		Trigger off of this check type if: You want an effect to happen immediately before a status effect is going to be lost.
		Info:
			status
			OR
			statuseswithtag
	ALLY_LOST_STATUS,
		Triggers after an ally has had a status effect removed. Triggers any post-status loss effects, then outputs information about the status loss to the event list UI and resets ally pathfinding to its current natural state.
		Raise a check of this type if: Do not raise ALLY_LOST_STATUS manually.
		Trigger off of this check type if: You want an effect to happen only when a status effect has successfully been lost.
		Info:
			None
	ALLY_COMBAT_ENCOUNTER,
		Triggers the first time that a monster room is entered with a monster inside. If not cancelled, plays a given encounter sound, then looks for a relevant dungeon event for the monster, triggering any of its checks and sending it out to the event list UI if one is found.
		Raise a check of this type if: Do not raise ALLY_COMBAT_ENCOUNTER manually.
		Trigger off of this check type if: You want an effect to happen when an ally first encounters a new monster.
		Info:

	ALLY_COMBAT_ATTACK,
		Triggers immediately before an ally is about to perform the Attack Action.
			If cancelled, checks if the monster can counterattack. If so, raises an ALLY_COMBAT_ATTACKED check.
			If not cancelled, performs combat calculations with the character and monster information, outputs a message to the event list UI, raises a MONSTER_TAKE_DAMAGE check, spawns given particles/sounds, then triggering an ALLY_COMBAT_POST_ATTACK check.
		Raise a check of this type if: You want an effect to force an ally to attack a monster.
		Trigger off of this check type if: You want an effect to happen immediately before an attack against a monster occurs.
	ALLY_COMBAT_POST_ATTACK,
		Triggers after an ally has completed an Attack Action successfully. Triggers any post-attack checks, then raises an ALLY_COMBAT_ATTACKED check if the monster is willing and able to counter attack.
		After all checks are resolved, sets the ally as having performed an action and adds exhaustion from combat if appropriate.
		Raise a check of this type if: Do not raise ALLY_COMBAT_POST_ATTACK manually.
		Trigger off of this check type if: You want an effect to happen immediately after an ally attacks, but before the monster can counterattack.
	ALLY_COMBAT_ATTACKED,
		Triggers immediately before an ally is about to be attacked by a monster. If not cancelled and the monster still has health, does combat calculations with the character and monster information.
			This looks for a relevant dungeon event for the monster and event type, but there are currently no ALLY_COMBAT_ATTACKED events in the game. If it doesn't find a dungeon event, it simply outputs generic text to the event list UI.
		After that it spawns relevant particles/sounds for combat, then checks if the damage calculation indicates that the ally has been hit. If so, raises an ALLY_COMBAT_ALLY_DAMAGED check.
		Raise a check of this type if: You want an effect to force a monster to attack an ally. (TODO: I've never had an effect raise this. Would it even be okay to do manually?)
		Trigger off of this check type if: You want an effect to happen immediately before an ally is going to be attacked.
	TODO: ALLY_COMBAT_POST_ATTACKED post check?
	ALLY_COMBAT_ALLY_DAMAGED,
		Triggers when a monster has dealt enough damage to an ally to score a hit. If not cancelled, looks for a relevant dungeon event for the monster, triggering any of its checks and sending it out to the event list UI if one is found.
		Raise a check of this type if: Do not manually raise ALLY_COMBAT_ALLY_DAMAGED
		Trigger off of this check type if: You want an effect to happen when a monster successfully scores a hit on an ally.
	TODO: ALLY_COMBAT_ALLY_WAS_DAMAGED post check?
	ALLY_COMBAT_ENEMY_DEFEATED,
		Triggers when a monster has taken enough damage to be reduced to 0 or less health, and the final blow was a direct attack that can be linked to a character. If not cancelled, looks for a relevant dungeon event for the monster, triggering any of its checks and sending it out to the event list UI if one is found.
		After that it spawns relevant particles/sounds for the monster's defeat, updates the ally's count of defeated monsters, and raises a MONSTER_DEFEATED_FROM_ROOM check
		Raise a check of this type if: Do not raise ALLY_COMBAT_ENEMY_DEFEATED manually.
		Trigger off of this check type if: You want an effect to happen when an ally reduces a monster's health to 0.
	ALLY_TRAP_TRIGGERED,
		Triggers when a trap is about to go off, regardless of why or if it is going to hit or not. If not cancelled, spawns relevant particles/sounds for the trap being triggered, then checks if avoiding is allowed.
		If avoid is allowed, it compares the trap's accuracy against the character's relevant stat. If the accuracy is higher, raises an ALLY_TRAP_TRIGGERED_HIT check. If not, raises an ALLY_TRAP_TRIGGERED_MISS check.
		If avoid is not allowed, raises an ALLY_TRAP_TRIGGERED_HIT check.
		After all checks are resolved, sets the trap to no longer be armed. If the trap is not rearmable, it is removed from the room. Otherwise, the trap's rearm timer is set to its rearm time.
		Raise a check of this type if: You want an effect to force a trap to go off.
		Trigger off of this check type if: You want an effect to happen immediately before a trap is going to go off.
	ALLY_TRAP_TRIGGERED_HIT,
		Triggers when a trap has gone off and it has been determined that it is going to hit an ally. Spawns relevant trigger hit sound, then looks for a relevant dungeon event, triggering any of its checks and sending it out to the event list UI if one is found.
		Raise a check of this type if: Do not raise ALLY_TRAP_TRIGGERED_HIT manually.
		Trigger off of this check type if: You want an effect to happen when a trap successfully scores a hit on an ally.
	ALLY_TRAP_TRIGGERED_MISS,
		Triggers when a trap has gone off and it has been determined that it is going to miss an ally. Spawns relevant trigger miss sound, then looks for a relevant dungeon event, triggering any of its checks and sending it out to the event list UI if one is found.
		Raise a check of this type if: Do not raise ALLY_TRAP_TRIGGERED_MISS manually.
		Trigger off of this check type if: You want an effect to happen when an ally successfully avoids a trap that has gone off.
	ALLY_TRAP_ATTEMPT_DISARM,
		Triggers immediately before an ally is about to perform the Disarm Action. If not cancelled, performs disarm calculations with the ally and trap information, outputs a message to the event list UI, raises a TRAP_TAKE_DAMAGE check, spawns given particles/sounds, then if the trap
		Raise a check of this type if: You want an effect to force an ally to use the disarm action on a trap.
		Trigger off of this check type if: You want an effect to happen immediately before an ally uses the disarm action on a trap.
	TODO: ALLY_TRAP_ATTEMPTED_DISARM post check?
	ALLY_TRAP_COMPLETED_DISARM,
		Triggers when a trap has taken enough damage to be reduced to 0 or less health, and the final damage was a direct disarming that can be linked to an ally. If not cancelled, looks for a relevant dungeon event for the trap, triggering any of its checks and sending it out to the event list UI if one is found.
		After that it spawns relevant particles/sounds for the trap's disarming, updates the ally's count of disarmed traps, and raises a TRAP_DISARMED_FROM_ROOM check.
		Raise a check of this type if: Do not raise ALLY_TRAP_COMPLETED_DISARM manually.
		Trigger off of this check type if: You want an effect to happen when an ally reduces a trap's health to 0.
	ALLY_TRAP_FAILED_DISARM,
		TODO: Is this used for anything? It triggers when a trap's complexity counter passes an ally's defend stat, but just raises an ALLY_TRAP_TRIGGERED_HIT check anyway.
	ALLY_OPEN_CHEST,
		Triggers immediately before an ally is about to perform the Open Chest Action. If not cancelled, removes the chest from the room, spawns the relevant particles/sounds, and looks for a relevant dungeon event, triggering any of its checks and sending it out to the event list UI if one is found.
		After all checks are resolved, sets the ally as having performed an action and updates the ally's count of opened chests.
		Raise a check of this type if: You want an effect to force an ally to use the open chest action.
		Trigger off of this check type if: You want an effect to happen immediately before an ally opens a chest.
	TODO: ALLY_OPENED_CHEST post check?
	ALLY_ENTERING_ROOM,
		Triggers immediately before an ally moves to enter a room. Appends the ally to the list of room occupants.
		TODO: Should this be cancellable? EXITING ROOM is, but I would need to double check that an ally can't get stuck in some between rooms limbo.
		Raise a check of this type if: Do not raise ALLY_ENTERING_ROOM manually.
		Trigger off of this check type if: You want an effect to happen when an ally enters a room.
	ALLY_EXPLORING_ROOM,
		Triggers when an ally has entered a room which has not had its contents revealed previously.
		After all checks are resolved, updates the ally's count of rooms explored
		Raise a check of this type if: Do not raise ALLY_EXPLORING_ROOM manually (TODO: Actually, would this be okay? It may actually be?)
		Trigger off of this check type if: You want an effect to happen when a room is explored.
	ALLY_EXITING_ROOM,
		Triggers immediately before an ally moves to exit a room. Removes the ally from the list of room occupants.
		Raise a check of this type if: Do not raise ALLY_EXITING_ROOM manually.
		Trigger off of this check type if: You want an effect to happen when an ally exits a room.
	ALLY_RESTED_IN_SAFE_ROOM,
		Triggers immediately before an ally is about to perform the Rest Action. If not cancelled, sets the ally as having performed an action, outputs a message to the event list UI, and heals the appropriate negative stats from resting.
		Raise a check of this type if: You want an effect to force an ally to use the Rest Action.
		Trigger off of this check type if: You want an effect to happen when an ally uses the Rest Action.
	ALLY_FORCE_MOVE_TO_ROOM,
		Triggers when some effect indicates that an ally should be moved from their current location to a given room. If not cancelled, raises an ALLY_EXITING_ROOM check for their current room, then an ALLY_ENTERING_ROOM check for the new room, then an ALLY_WAS_FORCE_MOVED_TO_ROOM check.
		Raise a check of this type if: You want an effect that forcibly moves an ally from their current room to a new one.
		Trigger off of this check type if: You want an effect to happen immediately before an ally is going to be forcibly moved.
	ALLY_WAS_FORCE_MOVED_TO_ROOM,
		Triggers after an effect has forcibly moved an ally to a new room. Does nothing on its own, but triggers any post-move checks.
		Raise a check of this type if: Do not raise ALLY_WAS_FORCE_MOVED_TO_ROOM manually.
		Trigger off of this check type if: You want an effect to happen only when an ally has finished being forcibly moved.
	ALLY_TELEPORTING_TO_ROOM,
		A positive variant of ALLY_FORCE_MOVE_TO_ROOM. Does the same thing but with a different connotation.
		TODO: This should also probably be split into a pre and post check
		Raise a check of this type if: You want an effect that moves an ally from their current room to a new one, but does not trigger effects of ALLY_FORCE_MOVE_TO_ROOM
		Trigger off of this check type if: You want an effect to happen immediately before an ally is going to be moved.
		Example: The Recall spell moves allies to the safe room when they suffer a corruption break, but is considered a good thing compared to other force move effects.
	ALLY_CHANGE_CURRENT_DESIRE,
		Triggers when some effect indicates that an ally's current value for a desire is to be changed. If not cancelled, modifies the given desire by the given amount field and outputs a message to the event list UI. If allow_drive_change is true and the current desire value goes above 10 or below 0, triggers an ALLY_CHANGE_DESIRE_DRIVE check.
		TODO: There's a weird bit of code in here I need to look at later
		Raise a check of this type if: You want an effect to change the current value of one of an ally's desires.
		Trigger off of this check type if: You want an effect to happen immediately before one of an ally's desires is going to be changed.
	ALLY_CHANGE_DESIRE_DRIVE,
		Triggers when some effect indicates that an ally's drive for a desire should change. If not cancelled, modifies the given desire drive by the given amount field and outputs a message to the event list UI.
		Raise a check of this type if: You want an effect to directly change one of an ally's desire drives.
		Trigger off of this check type if: You want an effect to happen immediately before one of an ally's desire drives is going to be changed.
	ALLY_CHANGE_FAVORABILITY,
		Triggers when some effect indicates that an ally's favorability value should change. If not cancelled, sets the ally's favorability to the given amount.
		Raise a check of this type if: You want an effect to change an ally's favorability toward the inquisitor.
		Trigger off of this check type if: You want an effect to happen immediately before an ally's favorability toward the inquisitor is giong to be changed.
	ALLY_CHANGE_CONTROL,
		exactly the same as the previous, but for player control over the ally instead of favorability
	ALLY_TO_ALLY_INTERACTION,
		TODO: Complex and messy. Need to think about refactoring to make these less hardcoded
	ALLY_TURN_END,
		Triggers once at the end of an ally's turn. Does nothing on its own.
		Raise a check of this type if: Do not raise ALLY_TURN_END manually.
		Trigger off of this check type if: You want an effect that happens at the end of an ally's turn.
	MONSTER_SPAWN_IN_ROOM,
		Triggers when some effect indicates that a monster should be spawned in a given room. If not cancelled, spawns a monster of the given monster_ID with any specified spawn_modifier, then adds it to the given room. After that, raises a MONSTER_WAS_SPAWNED_IN_ROOM check.
		Raise a check of this type if: You want an effect that will spawn a new monster.
		Trigger off of this check type if: You want an effect that will happen immediately before a monster is going to be spawned.
	MONSTER_WAS_SPAWNED_IN_ROOM,
		Triggers after some effect has spawned a monster. Triggers any post-monster spawn checks, but does nothing on its own.
		Raise a check of this type if: Do not raise MONSTER_WAS_SPAWNED_IN_ROOM manually.
		Trigger off of this check type if: You want an effect that will happen when a monster has successfully been spawned.
	MONSTER_TAKE_DAMAGE,
		Triggers when some effect indicates that a monster should take damage. If not cancelled, calculates actual damage done from the amount in against the monster's armor, then raises a MONSTER_DAMAGE_WAS_TAKEN check.
		Raise a check of this type if: You want an effect to deal damage to a monster.
		Trigger off of this check type if: You want an effect that will happen immediately before a monster is about to take damage.
	MONSTER_DAMAGE_WAS_TAKEN,
		Triggers after something caused a monster to take damage. Outputs a message to the event list UI.
			If the monster's health has reached 0 or less and the damage dealt can be directly linked to an ally, triggers an ALLY_COMBAT_ENEMY_DEFEATED check.
			If the monster's health has reached 0 or less and the damage source is not directly linkable to an ally, it skips the ALLY_COMBAT_ENEMY_DEFEATED check and instead raises a MONSTER_DEFEATED_FROM_ROOM check.
		Raise a check of this type if: Do not raise MONSTER_DAMAGE_WAS_TAKEN manually
		Trigger off of this check type if: You want an effect that will happen only when a monster has successfully taken damage.
	MONSTER_HEAL_DAMAGE,
		Triggers when some effect indicates that a monster should regain health. If not cancelled, adds the given amount to the specified monster's current health stat, then raises a MONSTER_DAMAGE_WAS_HEALED check.
		Raise a check of this type if: You want an effect to heal damage from a monster.
		Trigger off of this check type if: You want an effect that will happen immediately before a monster is about to heal.
	MONSTER_DAMAGE_WAS_HEALED,
		Triggers after a monster regained health. Triggers any post-heal checks, then outputs a message to the event list UI.
		Raise a check of this type if: Do not raise MONSTER_DAMAGE_WAS_HEALED manually.
		Trigger off of this check type if: You want an effect that will happen only when a monster has successfully been healed.
	MONSTER_GAIN_STATUS,
		Triggers when some effect indicates that a monster should gain a status effect. If not cancelled, applies the given status effect for the given duration using the given overwrite behavior, then raises a MONSTER_GAINED_STATUS check.
		Raise a check of this type if: You want an effect to give a monster a status effect.
		Trigger off of this check type if: You want an effect that happens immediately before a status effect is granted to a monster.
	MONSTER_GAINED_STATUS,
		Triggers after a monster has gained a new status effect. Triggers any post-status gain effects, then outputs information about the status being gained to the event list UI.
		Raise a check of this type if: Do not raise MONSTER_GAINED_STATUS manually.
		Trigger off of this check type if: You want an effect to happen only when a monster has successfully gained a status effect.
	MONSTER_STATUS_TICK,
		Triggers when a monster's status effect is being made to decrease its duration. This can happen naturally at the start of an ally's turn or when a monster performs an action, depending on what kind of status effect it is. If not cancelled, decreases the duration of the given status effect by 1.
		Raise a check of this type if: You want an effect to tick down the duration of a monster's status effect(s)
		Trigger off of this check type if: You want an effect to happen whenever an monster's status effect duration is decreasing.
	MONSTER_CHANGE_TRACKER_VALUE,
		Changes the value of the given monster status effect information tracker to the given amount/value.
		This happens BEFORE further checks are triggered
		Raise a check of this type if: You want a monster effect to change the value of a tracker variable on this or any other effect
		Trigger off of this check type if: You want a monster effect that does something when an effect's tracking variable values have changed
	MONSTER_LOSE_STATUS,
		Triggers when some effect indicates that a monster should be losing a status effect. If not cancelled, it will look for the given status effect on the monster. If it is found, its trackers will be removed, it and any of its associated particles will be made invisible, then it will be removed. After that it will create a MONSTER_LOST_STATUS check.
		Raise a check of this type if: You want an effect to remove a status effect from a monster.
		Trigger off of this check type if: You want an effect to happen immediately before a status effect is going to be lost by a monster.
	MONSTER_LOST_STATUS,
		Triggers after a monster has had a status effect removed. Triggers any post-status loss effects, then outputs information about the status loss to the event list UI.
		Raise a check of this type if: Do not raise MONSTER_LOST_STATUS manually.
		Trigger off of this check type if: You want an effect to happen only when a status effect has successfully been lost by a monster.
	MONSTER_RETREAT_FROM_ROOM,
		Triggers when some effect indicates that a monster should run away. If not cancelled, clears the monster from the room, leaving it empty. If log_research is true in the check information, the monster is still added to the player's research notes from this happening.
		Raise a check of this type if: You want an effect that causes a monster to run from a room.
		Trigger off of this check type if: You want an effect to happen when a monster is trying to run from a room.
	MONSTER_DEFEATED_FROM_ROOM,
		Triggers when a monster has hit 0 or less health and should be removed from the room. If not cancelled, adds the monster to the player's research notes, spawns the relevant particles/sounds for the monster, and outputs text to the event list UI. If the monster has a reward chest, the room is changed to a chest room and that is also sent to the event list UI. Either way, the monster is then removed from the room.
		Raise a check of this type if: You want an effect that causes a monster to be removed from a room and considered defeated.
		Trigger off of this check type if: You want an effect to happen immediately before a monster is going to be removed from a room.
	TODO: TRAP_SPAWN_IN_ROOM and TRAP_WAS_SPAWNED_IN_ROOM
	TRAP_TAKE_DAMAGE,
		Triggers when some effect indicates that a trap should take damage. If not cancelled, calculates actual damage done from the amount in, then raises a TRAP_DAMAGE_WAS_TAKEN check.
		Raise a check of this type if: You want an effect to deal damage to a trap.
		Trigger off of this check type if: You want an effect that will happen immediately before a trap is about to take damage.
	TRAP_DAMAGE_WAS_TAKEN,
		Triggers after something caused a trap to take damage. Outputs a message to the event list UI.
			If the trap's health has reached 0 or less and the damage dealt can be directly linked to an ally, triggers an ALLY_TRAP_COMPLETED_DISARM check.
			If the trap's health has reached 0 or less and the damage source is not directly linkable to an ally, it skips the ALLY_TRAP_COMPLETED_DISARM check and instead raises a TRAP_DISARMED_FROM_ROOM check.
		Raise a check of this type if: Do not raise TRAP_DAMAGE_WAS_TAKEN manually
		Trigger off of this check type if: You want an effect that will happen only when a trap has successfully taken damage.
	TRAP_HEAL_DAMAGE,
		Triggers when some effect indicates that a trap should regain health. If not cancelled, adds the given amount to the specified trap's current health stat, then raises a TRAP_DAMAGE_WAS_HEALED check.
		Raise a check of this type if: You want an effect to heal damage from a trap.
		Trigger off of this check type if: You want an effect that will happen immediately before a trap is about to heal.
	TRAP_DAMAGE_WAS_HEALED,
		Triggers after a trap regained health. Triggers any post-heal checks, then outputs a message to the event list UI.
		Raise a check of this type if: Do not raise TRAP_DAMAGE_WAS_HEALED manually.
		Trigger off of this check type if: You want an effect that will happen only when a trap has successfully been healed.
	TRAP_GAIN_STATUS,
		Triggers when some effect indicates that a trap should gain a status effect. If not cancelled, applies the given status effect for the given duration using the given overwrite behavior, then raises a TRAP_GAINED_STATUS check.
		Raise a check of this type if: You want an effect to give a trap a status effect.
		Trigger off of this check type if: You want an effect that happens immediately before a status effect is granted to a trap.
	TRAP_GAINED_STATUS,
		Triggers after a trap has gained a new status effect. Triggers any post-status gain effects, then outputs information about the status being gained to the event list UI.
		Raise a check of this type if: Do not raise TRAP_GAINED_STATUS manually.
		Trigger off of this check type if: You want an effect to happen only when a trap has successfully gained a status effect.
	TRAP_STATUS_TICK,
		Triggers when a trap's status effect is being made to decrease its duration. This can happen naturally at the start of an ally's turn or when a trap performs an action, depending on what kind of status effect it is. If not cancelled, decreases the duration of the given status effect by 1.
		Raise a check of this type if: You want an effect to tick down the duration of a trap's status effect(s)
		Trigger off of this check type if: You want an effect to happen whenever a trap's status effect duration is decreasing.
	TRAP_CHANGE_TRACKER_VALUE,
		Changes the value of the given trap status effect information tracker to the given amount/value.
		This happens BEFORE further checks are triggered
		Raise a check of this type if: You want a trap effect to change the value of a tracker variable on this or any other effect
		Trigger off of this check type if: You want a trap effect that does something when an effect's tracking variable values have changed
	TRAP_LOSE_STATUS,
		Triggers when some effect indicates that a trap should be losing a status effect. If not cancelled, it will look for the given status effect on the trap. If it is found, its trackers will be removed, it and any of its associated particles will be made invisible, then it will be removed. After that it will create a TRAP_LOST_STATUS check.
		Raise a check of this type if: You want an effect to remove a status effect from a trap.
		Trigger off of this check type if: You want an effect to happen immediately before a status effect is going to be lost by a trap.
	TRAP_LOST_STATUS,
		Triggers after a trap has had a status effect removed. Triggers any post-status loss effects, then outputs information about the status loss to the event list UI.
		Raise a check of this type if: Do not raise TRAP_LOST_STATUS manually.
		Trigger off of this check type if: You want an effect to happen only when a status effect has successfully been lost by a trap.
	TRAP_CHANGE_REARM_TIMER,
		Triggers when some effect indicates that a trap should have its rearm timer set to a new value. This is NOT generated as a result of a turn passing, only other effects. If not cancelled, sets the trap's rearm timer to the given amount.
		Raise a check of this type if: You want an effect to change the remaining time until rearming of a trap.
		Trigger off of this check type if: You want an effect to happen only when a trap's rearm timer is about to be changed.
	TRAP_REMOVE_FROM_ROOM,
		Triggers when some effect indicates that a trap should be removed from a room for some reason other than being disarmed. If not cancelled, clears the trap from the room, leaving it empty. If log_research is true in the check information, the trap is still added to the player's research notes from this happening.
		This is NOT generated from a non-rearmable trap going off.
		Raise a check of this type if: You want an effect that causes a trap to be removed from a room.
		Trigger off of this check type if: You want an effect to happen when a trap is going to be removed from a room.
	TRAP_DISARMED_FROM_ROOM,
		Triggers when a trap has hit 0 or less health and should be removed from the room. If not cancelled, adds the trap to the player's research notes, raises the relevant particles/sounds for the trap, and outputs text to the event list UI. The trap is then removed from the room.
		Raise a check of this type if: You want an effect that causes a trap to be removed from a room and considered disarmed.
		Trigger off of this check type if: You want an effect to happen immediately before a trap is going to be removed from a room.
	WITCH_DEN_DEAL_MADE,
		Triggers immediately after the player has finished using the Witch's Den room to make a deal, but before the results of the deal are applied. Does nothing on its own. Currently, witch den options are semi-hard coded, so interacting with them via mods will be a bit messy. As a result, the check contains no information about WHAT was exchanged in the deal, just that a deal was made.
		Raise a check of this type if: Do not raise WITCH_DEN_DEAL_MADE manually.
		Trigger off of this check type if: You want an effect to happen immediately after a deal with the Witch is completed, but before the results of the deal are applied.
	SHRINE_OFFERING_MADE,
		Triggers immediately after the player has selected the option to give an offering of corruption at a Shrine room. Looks for a relevant dungeon event, triggering any of its checks and sending it out to the event list UI if one is found. After that, deals the given amount of permanent corruption damage to the ally, updates the corruption wave timer, and adds the time extension to the player's save file (but does NOT save the file)
		Raise a check of this type if: Do not raise SHRINE_OFFERING_MADE manually.
		Trigger off of this check type if: You want an effect to happen immediately when a shrine offering is made.
	SHRINE_BLESSING_GIVEN,
		Triggers immediately after the player has selected the option to have an ally gain the curse that is offered in a shrine. Looks for a relevant dungeon event, triggering any of its checks and sending it out to the event list UI if one is found. After that, applies the given curse to the ally, setting it to be revealed if the player has already reached research level 1 for that curse.
		Raise a check of this type if: Do not raise SHRINE_BLESSING_GIVEN manually.
		Trigger off of this check type if: You want an effect to happen immediately when a shrine blessing is accepted.
	SHRINE_DENOUNCED,
		Triggers immediately after the player has selected the option to denounce at a Shrine room. Looks for a relevant dungeon event, triggering any of its checks and sending it out to the event list UI if one is found. After that, gets a list of rejected curses on the ally and removes all of them.
		Raise a check of this type if: Do not raise SHRINE_DENOUNCED manually.
		Trigger off of this check type if: You want an effect to happen immediately when a shrine is denounced.
	ROOM_BECOME_OBSCURED,
		Triggers when some effect indicates that a given room should be made darkened/obscured. If not cancelled, spawns the lighting effect on the map and sets the room's obscured property to true.
		Raise a check of this type if: You want an effect to darken a room.
		Trigger off of this check type if: You want an effect to happen immediately before a room is going to be made darkened.
	ROOM_SHOW_PARTICLE_EFFECT,
		Triggers when some effect indicates that it should show a particle effect inside of a given room. If not cancelled, looks to see if the room is obscured by darkness. If the room is unobscured or the show_when_obscured flag is set to true in the check information, the given particle is spawned and put on the dungeon map in the given room's location.
		Raise a check of this type if: You want an effect to display a particle effect in a room when it happens.
		Trigger off of this check type if: Do not trigger off of ROOM_SHOW_PARTICLE_EFFECT.
	PLAYER_SCRY_ROOM,
		Triggers when the player has used the scry spell on a given room in the dungeon. If not cancelled, generates PLAYER_SCRY_ALLY, PLAYER_SCRY_MONSTER, and PLAYER_SCRY_TRAP for each such entity in the room. After those checks are resolved, spawns the relevant particles/sounds, sets the room to no longer be obscured, explores it, and adds the scry_cooldown amount to the player's scry cooldown.
		Raise a check of this type if: You want an effect to scry a room.
		Trigger off of this check type if: You want an effect to happen immediately before a room is going to be scried.
	PLAYER_SCRY_ALLY,
		Triggers when a room has been scried that includes an ally. If not cancelled, outputs information about the scry having happened to the event list UI and updates the ally's count of times scried.
		Raise a check of this type if: It would be better to raise a PLAYER_SCRY_ROOM.
		Trigger off of this check type if: You want an effect to happen when an ally is being scried.
	PLAYER_SCRY_MONSTER,
		Triggers when a room has been scried that includes a monster. If not cancelled, outputs information about the scry having happened to the event list UI.
		Raise a check of this type if: It would be better to raise a PLAYER_SCRY_ROOM.
		Trigger off of this check type if: You want an effect to happen when a monster is being scried.
	PLAYER_SCRY_TRAP,
		Triggers when a room has been scried that includes a trap. If not cancelled, outputs information about the scry having happened to the event list UI.
		Raise a check of this type if: It would be better to raise a PLAYER_SCRY_ROOM.
		Trigger off of this check type if: You want an effect to happen when a trap is being scried.
	PLAYER_SCRY_COOLDOWN_CHANGED,
		Triggers when some effect indicates that the player's scry cooldown should be changed to a new value. If not cancelled, sets the player's current scry cooldown to the given amount field.
		TODO: "allowbelowzero" in check info here is uhhh... Hard to explain, but necessary as long as there are no post checks for scry effects. Basically if a scry effect wants to reduce its own cooldown (example: Siphon reducing scry cooldown if scrying a monster room) the cooldown will be 0 at the time PLAYER_SCRY_MONSTER happens, so it has to allow the cooldown to be adjusted to below 0 temporarily before PLAYER_SCRY_ROOM adds the base scry cooldown on after the other checks are resolved. So it will go 0 -> -2 -> 18 instead of 0 -> 0 -> 20.
		Raise a check of this type if: It would be better to raise a PLAYER_SCRY_ROOM.
		Trigger off of this check type if: You want an effect to happen when an ally is being scried.
	MAP_CORRUPTION_WAVE,
		Triggers when the timer for a corruption wave has hit 0, indicating that a wave is happening now. Ranks up a random curse on each ally. If doing so is not possible, damages the ally for the appropriate amount.
		Raise a check of this type if: I... haven't actually tried having an effect raise this? It might actually work.
		Trigger off of this check type if: You want an effect to happen when a corruption wave occurs.
	FLOOR_END,
		Triggers once per ally at the start of each dungeon floor. Does nothing on its own.
		Raise a check of this type if: Do not raise FLOOR_END manually.
		Trigger off of this check type if: You want an effect that happens exactly once to the ally at the end of a dungeon floor.

This is the end of all the currently existing checks FOR THE DUNGEON PORTION OF THE GAME

TODO: Full explanation for Camp checks
	RETURNED_TO_CAMP,
	CAMP_REROLL_ALL_ACTIVITIES,
	CAMP_ALLY_DETERMINING_DESIRED_ACTIVITY,
	CAMP_ALLY_ASKED_TO_CHANGE_ACTIVITY,
	CAMP_TIME_OF_DAY_ADVANCE,
	CAMP_ALLY_DOING_ACTIVITY,
	CAMP_ALLY_CHANGE_CURRENT_DESIRE,
	CAMP_ALLY_SET_CURRENT_DESIRE,
	CAMP_ALLY_CHANGE_DESIRE_DRIVE,
	CAMP_ALLY_CHANGE_FAVORABILITY,
	CAMP_ALLY_CHANGE_CONTROL,
	CAMP_ALLY_TENT_TALK,
	CAMP_ALLY_TENT_ACTION,
	CAMP_ALLY_ADD_TENT_MODIFIERS,
	CAMP_ALLY_REMOVE_TENT_MODIFIERS,
	CAMP_ALLY_TENT_HYPNO,
	CAMP_ALLY_TENT_UNHYPNO,
	CAMP_ALLY_TENT_EMPOWER_CURSE,
	CAMP_ALLY_TENT_WEAKEN_CURSE,
	CAMP_ALLY_TENT_EMBRACE_CURSE,
	CAMP_ALLY_TENT_REJECT_CURSE,
	CAMP_ALLY_HEAL_DAMAGE,
	CAMP_ALLY_TAKE_DAMAGE,
	CAMP_ALLY_GAIN_STATUS,
	CAMP_ALLY_GAINED_STATUS,
	CAMP_ALLY_STATUS_TICK,
	CAMP_ALLY_LOSE_STATUS,
	CAMP_ALLY_LOST_STATUS,
	CAMP_ALLY_REFRESH_SKILLS,
	CAMP_ALLY_IMPRINT_SCROLL,
	CAMP_ALLY_TEACH_SKILL,
	CAMP_PLAYER_SLEEP,
	CAMP_PLAYER_RESEARCH,
	CAMP_PLAYER_PREP_SPELLS,
	CAMP_ADD_SPELL_TO_PASSIVES,
	CAMP_REMOVE_SPELL_FROM_PASSIVES,
	CAMP_PLAYER_MEMORIZE_SKILL,
	CAMP_PLAYER_CAST_SPELL,
	CAMP_PLAYER_CAST_SPELL_ON_ALLY,
	CAMP_PLAYER_CAST_SPELL_ON_LOCATION,
	CAMP_PLAYER_SCRY_LOCATION,
	RETURNED_TO_DUNGEON,