订阅以下载
StatAPI

Note: OUTDATED! If possible, use Stats API 2.0 instead on the workshop.

Modder tool.

First release, likely has some bugs - leave anything you find strange in the comments below and for now, I left all the debugging strings on so you can check what it thinks yours stats are.

Known bugs:
- Purity Aura Boost (FireDelay) Isn't properly treated as a flat modifier, and may cause modded base-tears up items to have reduced effect while active.
- Kidney Stone scales differently than the base game a bit - its effectively the same item, but with a high firerate (like 30 or so) it may jump every other frame instead of going +1 every time.
- Some effects of multiplier babies may not apply right. Haven't tested it yet.
- Speed is an odd stat to work with and doesn't perfectly mesh with the base game.
- It currently ♥♥♥♥♥ up how bloody lust works - its a bug i know about i just dont have the time to fix it rn.

This is setup to work with the True Coop Mod - as far as I can tell. Haven't been able to test it myself as I don't have a controller really.

Have you ever had that annoying feeling of wanting to make a simple stats item, such as Tears +0.7 like sad onion, only to realize that Nicalis in their infinite wisdom could only give us the FireDelay stat?

This tool fixes that.

In addition, it fixes other problems based on mods stats such as:
1. More options for modifying the speed stat.
2. Automatic implementation of D8 to your stat changing items.
3. Apply modifiers or flat numbers or changes to the base stats, that works with other mods using the same system - incorporating them all in the proper order.

If any of that sounds any bit interesting to you, awesome! Ill explain how to use it below shortly.

If it doesn't - use it anyway. Because really, if we all use it together then all our items will apply correctly in the right order.

So - how to use it. There are four functions.

The first is statAPI.RegisterPlayer(playerType,damageMultiplier). Effectively, if you want a custom character of yours to start with a custom damage modifier, you can apply it here. I may expand this to also include custom tearrate starts and the like in the future, but hold tight on that for now.

The second is statAPI.CacheItem(itemID, FlagTable, stackable). If stackable is true, then the stats it applies will stack with multiple of the same item. If one with the same id already exists, it will be overwritten. Flagtable is a bit special, see below.

The third is statAPI.CacheTrinket(trinketID, FlagTable, momsBox). If momsBox is true, then the effects will be doubled if you hold Mom's Box (excluding negative multipliers. Im not sure how the game handles these on trinkets - so i left it out for now). If one with the same id already exists, it will be overwritten. Flagtable is a bit special, see below.

The fourth is statAPI.CacheNull(Name, FlagTable). Effectively the same as CacheItem, but doesn't require a specific item id - the minute you give it anything, it applies those stats. If one with the same name already exists, it will be overwritten.

The final is statAPI.RemoveNull(Name), because when any null effects you add are always active, you want a way to be able to remove them.

Basically, you set up a table, and then fill it with tables relating to its various properties. These properties are CacheFlag, StatChange, ChangeType, NormBreak, and MultiTag.

CacheFlag is what stat this is adjusting (Damage,TearDelay,Range,Luck,ShotSpeed, or MoveSpeed), StatChange is how much you want that stat to change by (Range is negative because its really "TearHeight"), and ChangeType is how you want to change it - either "Normal", "Multi", or "Flat" [Defaults to Normal]. The last two are just for multipliers (right now) - NormBreak determining if the multiplier is unusually and comes out of order [Defaults to false]. If you include a MultiTag, then any other items with the same MultiTag won't also be used - so you can make certain items not synergize together like Magic Mush and Cricket's Head if you choose. These MultiTags are per-stat only. Below are the built-in stat multipliers for you to perhaps choose to conflict with. If you choose to use one of these multipliers, your multiplier code will run first - so you could perhaps negate the effect of these by setting the multiplier to a value of 1, or increase their effect by setting a higher multiplier than the base one (though you will have to check when to apply the higher multiplier yourself).

Damage - Polyphemus, OddMushroomRate, SoyMilk, OnePointFive (Magic Mush, Cricket's Head, Belial + Martyr), EvesMascara, Proptosis, SacredHeart, Technology2, CrownOfLight, BloodyLust, DeadEye, Haemolacria

Firedelay - PolyShot (Polyphemus, Inner Eye, Mutant Spider), SoyMilk, Brimstone, Azazel, Ipecac, MonstrosLung, DrFetus, EvesMascara

The order that stats are changed goes like this:

1. Normal changes
1.5. Converts normal stat to the displayed stat version
2. NormBreak multipliers
3. Flat modifiers
4. Multipliers

Once you have made a table that fits, simply call the function with that table and it will insert it into the callback checks. This can be called anytime, but if you dont need to dynamically update the stats an item is affecting, you should be good just to check for statAPI and call it in POST_GAME_STARTED.

Example:
Recreating soymilk

SoyFlag =
{
{CacheFlag = CacheFlag.CACHE_FIREDELAY, StatChange = 0.25, ChangeType = "Multi"},
{CacheFlag = CacheFlag.CACHE_FIREDELAY, StatChange = -8, ChangeType = "Flat"},
{CacheFlag = CacheFlag.CACHE_DAMAGE, StatChange = 0.2, ChangeType = "Multi"}
}

statAPI.CacheItem(CollectibleType.COLLECTIBLE_SOY_MILK,SoyFlag,false)

If you have any questions feel free to leave comments below!