forked from HellFirePvP/AstralSorcery
-
Notifications
You must be signed in to change notification settings - Fork 0
/
AS-Example.zs
256 lines (228 loc) · 12.9 KB
/
AS-Example.zs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
// Disables the modifiers and/or converters of a single perk on the perk tree
// Enable the F3-debug screen (press f3...) and then open the perks-tab to see the registry names of the perks on their tooltip.
// Parameters:
// String (RegistryName)
// Example:
// mods.astralsorcery.PerkTree.disablePerk("astralsorcery:base_inc_perkeffect_t1");
// Removes a perk and its connections from the perk tree.
// It is highly advised to do any kind of removals from the perk tree BEFORE releasing the pack/allowing users to pick those perks.
// Enable the F3-debug screen (press f3...) and then open the perks-tab to see the registry names of the perks on their tooltip.
// Parameters:
// String (RegistryName)
// Example:
// mods.astralsorcery.PerkTree.removePerk("astralsorcery:base_inc_perkeffect_t1_1");
// Modifies the multipliers of all modifiers on a perk.
// The default values will be multiplied with the passed multiplier.
// Enable the F3-debug screen (press f3...) and then open the perks-tab to see the registry names of the perks on their tooltip.
// Parameters:
// String (RegistryName)
// Float (The multiplier)
// Example:
// mods.astralsorcery.PerkTree.modifyPerk("astralsorcery:base_inc_perkeffect_t1", 0);
// Adds a new Infusion recipe to the starlight infusion
// Parameters:
// InputStack, OutputStack, consumeMultiple (true/false), consumptionChance, craftTickTime
// Example:
// mods.astralsorcery.StarlightInfusion.addInfusion(<astralsorcery:itemjournal>, <minecraft:bow>, false, 0.7, 200);
// Removes the first Infusion that matches the described ItemStack.
// Removes only the first it finds. Add multiple removeInfusion-calls to remove multiples, if present.
// Parameters:
// OutputStack
// Example:
// mods.astralsorcery.StarlightInfusion.removeInfusion(<minecraft:ice>);
// Adds a light transmutation recipe
// Each input & output item specified *has to have* a block representation or the recipe will be skipped.
// Metadata of the itemstacks is used to determine the blockstate.
// Parameters:
// InputBlock (as itemstack), OutputBlock (as itemstack), chargeUsed (until transmutation is complete)
// Example:
// mods.astralsorcery.LightTransmutation.addTransmutation(<minecraft:grass>, <minecraft:gold_ore>, 10);
// Adds a light transmutation recipe requiring a specific constellation
// Each input & output item specified *has to have* a block representation or the recipe will be skipped.
// Metadata of the itemstacks is used to determine the blockstate.
// Parameters:
// InputBlock (as itemstack), OutputBlock (as itemstack), chargeUsed (until transmutation is complete), string name of the required constellation
// Example:
// mods.astralsorcery.LightTransmutation.addTransmutation(<minecraft:grass>, <minecraft:gold_ore>, 10, "astralsorcery.constellation.fornax");
// Removes a light transmutation recipe
// The inputstack can be an item or block, depending on that it'll try and find a recipe that matches.
// Removes only the first it finds. Add multiple removeTransmutation-calls to remove multiples, if present.
// Parameters:
// matchStack (itemstack that is matched against the output of the transmutation), true/false (respect metadata in the check, false ignores metadata and only looks for a block match)
// Example:
// mods.astralsorcery.LightTransmutation.removeTransmutation(<minecraft:end_stone>, false);
// Removes a lightwell recipe
// Tries to find the recipe to remove via the given ItemStack and optionally the fluid together with it.
// The fluid-parameter can be 'null' only search for the recipe to remove via the given itemstack.
// Removes only the first it finds. Add multiple removeLiquefaction-calls to remove multiples, if present.
// Parameters:
// matchStack (itemstack that is matched against the input of the liquefaction), liquidStack (as additional search parameter *or null* to only search via itemstack-input)
// Example:
// mods.astralsorcery.Lightwell.removeLiquefaction(<astralsorcery:itemcraftingcomponent:0>, null);
// Adds a lightwell recipe
// Only the fluid from the output-liquidstack counts, the amount will (like the default lightwell depend on day/night and stuff too..)
// outputMulitplier: Multiplier that is applied together with the collected starlight to calculate the output fluid amount. Usually 0.3 - 1.2 (aka: don't write like 200 here, if you want to stay reasonable :P)
// shatterMultiplier: The higher this multiplier, the lower the chance per-tick that the catalyst item will shatter.
// colorHEX: The colorcode used for the particles around the hovering item.
// Parameters:
// Input-ItemStack, Output-LiqudStack, (float) outputMulitplier, (float) shatterMultiplier, (int) colorHEX (use a hex-color picker or something if you don't know how to specify that manually)
// Example:
// mods.astralsorcery.Lightwell.addLiquefaction(<minecraft:dirt>, <liquid:water>, 1, 0.2, 0);
// Adds a liquid interaction to the chalice-interactions
// FluidStack amounts count as the amount of liquid that will be consumed if an interaction occurs.
// chance1 and chance2 define the chances the input fluids input1 and input2 are consumed respectively.
// weight determines how likely this is to be selected in comparison to the other liquid interactions registered for a given pair of fluid-inputs
// Parameters:
// Input-LiquidStack-1, (float) chance-consumption-1, Input-LiquidStack-2, (float) chance-consumption-2, (int) weight, Output-ItemStack
// Example:
// mods.astralsorcery.LiquidInteraction.addInteraction(<liquid:lava> * 10, 0.1, <liquid:water> * 90, 0.2, 400, <minecraft:diamond>);
// Removes a liquid interaction from the chalice-interactions
// FluidStack parameters match against the 2 components that would interact to produce some output
// If a FluidStack combination can have multiple outputs, only the first matching one is removed!
// The itemstack output-parameter is optional. It may be used to select a specific fluid-interaction to remove if multiple are present..
// Parameters:
// Input-LiquidStack, Input-LiquidStack [, (Optional) Output-ItemStack]
// Example:
// mods.astralsorcery.LiquidInteraction.removeInteraction(<liquid:lava>, <liquid:water>, <minecraft:obsidian>);
// Adds a grindstone recipe
// The 'Input' can be both an itemstack or a oredict name!
// Parameters:
// Input, Output-ItemStack
// Example:
// mods.astralsorcery.Grindstone.addRecipe(<minecraft:stone>, <minecraft:gravel>);
// Removes a single grindstone recipes
// Only 1 recipe will be removed, the first one matching the output-stack specified.
// Parameters:
// Output-ItemStack
// Example:
// mods.astralsorcery.Grindstone.removeRecipe(<minecraft:redstone>);
// Removes a recipe from the altar recipe registry.
// Removes only the first it finds. Add multiple removeAltarRecipe-calls to remove multiples, if present.
// You can see the altar-recipe-registryname of existing recipes by hovering over the output of it in the tome or JEI while the F3-Debug screen is active!
// Parameters:
// - recipeRegistryName (The altar recipe's recipe registry name)
// Example:
// mods.astralsorcery.Altar.removeAltarRecipe("astralsorcery:shaped/internal/altar/lightwell");
// Adds a recipe to the discovery/tier1 altar recipes
// You can see the altar-recipe-registryname of existing recipes by hovering over the output of it in the tome or JEI while the F3-Debug screen is active!
// This cannot be shapeless.
// Can accept an ItemStack, OreDicitionary, LiquidStack or null in any slot.
// Formats (just as reminder): (ItemStack should be known), OreDicitionary: <ore:OreDictName>, Liquid: <liquid:LiquidName>
// Output has to be an ItemStack.
// Inputs have to have at least 1 non-null input.
// Arrays are indexed as follows:
//
// [ 0] [ 1] [ 2]
// [ 3] [ 4] [ 5]
// [ 6] [ 7] [ 7]
//
// Parameters:
// - recipeRegistryName (If a recipe with the same name already exists, the existing recipe will be removed!)
// - OutputStack,
// - (int) starlightRequired,
// - (int) craftTickTime,
// - Inputs-Array (*has* to be 9 elements)
// Example:
// mods.astralsorcery.Altar.addDiscoveryAltarRecipe("mypackname:shaped/internal/altar/dirtfromstuff", <minecraft:dirt>, 200, 200, [
// <minecraft:grass>, null, <ore:treeLeaves>,
// null, <minecraft:grass>, null,
// <liquid:astralsorcery.liquidstarlight>, null, <ore:treeLeaves>
// ]);
// Adds a recipe to the attunement/tier2 altar recipes
// You can see the altar-recipe-registryname of existing recipes by hovering over the output of it in the tome or JEI while the F3-Debug screen is active!
// This cannot be shapeless.
// Can accept an ItemStack, OreDicitionary, LiquidStack or null in any slot.
// Formats (just as reminder): (ItemStack should be known), OreDicitionary: <ore:OreDictName>, Liquid: <liquid:LiquidName>
// Output has to be an ItemStack.
// Inputs have to have at least 1 non-null input.
// Arrays are indexed as follows:
//
// [ 9] [10]
// [ 0] [ 1] [ 2]
// [ 3] [ 4] [ 5]
// [ 6] [ 7] [ 8]
// [11] [12]
//
// Parameters:
// - recipeRegistryName (If a recipe with the same name already exists, the existing recipe will be removed!)
// - OutputStack,
// - (int) starlightRequired,
// - (int) craftTickTime,
// - Inputs-Array (*has* to be 13 elements)
// Example:
// mods.astralsorcery.Altar.addAttunmentAltarRecipe("mypackname:shaped/internal/altar/iguessmarble", <minecraft:dirt>, 500, 300, [
// null, null, null,
// <ore:treeLeaves>, <astralsorcery:blockmarble:2>, <ore:treeLeaves>,
// null, <liquid:astralsorcery.liquidstarlight>, null,
// <ore:blockMarble>, <ore:blockMarble>, <ore:blockMarble>, <ore:blockMarble>
// ]);
// Adds a recipe to the constellation/tier3 altar recipes
// You can see the altar-recipe-registryname of existing recipes by hovering over the output of it in the tome or JEI while the F3-Debug screen is active!
// This cannot be shapeless.
// Can accept an ItemStack, OreDicitionary, LiquidStack or null in any slot.
// Formats (just as reminder): (ItemStack should be known), OreDicitionary: <ore:OreDictName>, Liquid: <liquid:LiquidName>
// Output has to be an ItemStack.
// Inputs have to have at least 1 non-null input.
// Arrays are indexed as follows:
//
// [ 9] [13] [14] [10]
// [15] [ 0] [ 1] [ 2] [16]
// [ 3] [ 4] [ 5]
// [17] [ 6] [ 7] [ 8] [18]
// [11] [19] [20] [12]
//
// Parameters:
// - recipeRegistryName (If a recipe with the same name already exists, the existing recipe will be removed!)
// - OutputStack,
// - (int) starlightRequired,
// - (int) craftTickTime,
// - Inputs-Array (*has* to be 21 elements)
// Example:
// mods.astralsorcery.Altar.addConstellationAltarRecipe("mypackname:shaped/internal/altar/thisisveryexpensive", <astralsorcery:itemcraftingcomponent:2>, 2000, 10, [
// <ore:blockMarble>, <astralsorcery:blocklens>, <ore:blockMarble>,
// <ore:blockMarble>, <astralsorcery:itemcraftingcomponent:2>, <ore:blockMarble>,
// <ore:blockMarble>, <minecraft:nether_star>, <ore:blockMarble>,
// null, null, <liquid:astralsorcery.liquidstarlight>, <liquid:astralsorcery.liquidstarlight>,
// <ore:blockMarble>, <ore:blockMarble>,
// <minecraft:nether_star>, <minecraft:nether_star>,
// <minecraft:nether_star>, <minecraft:nether_star>,
// <ore:blockMarble>, <ore:blockMarble>
// ]);
// Adds a recipe to the trait/tier4 altar recipes
// You can see the altar-recipe-registryname of existing recipes by hovering over the output of it in the tome or JEI while the F3-Debug screen is active!
// This cannot be shapeless.
// Can accept an ItemStack, OreDicitionary, LiquidStack or null in any slot.
// Formats (just as reminder): (ItemStack should be known), OreDicitionary: <ore:OreDictName>, Liquid: <liquid:LiquidName>
// Output has to be an ItemStack.
// Inputs have to have at least 1 non-null input.
// Inputs at index 25 or higher are considered the "outer items" the player has to put onto relays around the tier4+ altar
// Arrays are indexed as follows:
//
// [ 9] [13] [21] [14] [10]
// [15] [ 0] [ 1] [ 2] [16]
// [22] [ 3] [ 4] [ 5] [23]
// [17] [ 6] [ 7] [ 8] [18]
// [11] [19] [24] [20] [12]
//
// Parameters:
// - recipeRegistryName (If a recipe with the same name already exists, the existing recipe will be removed!)
// - OutputStack,
// - (int) starlightRequired,
// - (int) craftTickTime,
// - Inputs-Array (*has* to be 13 elements)
// - (optional, string) required-unlocalized-constellation-name
// Example:
// mods.astralsorcery.Altar.addTraitAltarRecipe("mypackname:shaped/internal/altar/seemsalotforjusttnt", <minecraft:tnt>, 4500, 100, [
// <liquid:lava>, <liquid:lava>, <liquid:lava>,
// <liquid:lava>, <minecraft:gunpowder>, <liquid:lava>,
// <liquid:lava>, <liquid:lava>, <liquid:lava>,
// null, null, null, null,
// <ore:blockMarble>, <ore:blockMarble>,
// <astralsorcery:itemusabledust>, <astralsorcery:itemusabledust>,
// <astralsorcery:itemusabledust>, <astralsorcery:itemusabledust>,
// <ore:blockMarble>, <ore:blockMarble>,
// <minecraft:redstone>, <minecraft:redstone>,
// <minecraft:redstone>, <minecraft:redstone>,
// <minecraft:sand>, <minecraft:sand>, <minecraft:sand>, <minecraft:sand>, <minecraft:sand>
// ],
// "astralsorcery.constellation.evorsio");