You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: raw/meteor-reagents/README
+23-12Lines changed: 23 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,9 @@
4
4
5
5
The butter for your bread.
6
6
7
-
This file and the other default meteor reagent configs (crystallos.json, incendium.json, orbisTerrae.json, tenebrae.json, and terrae.json) are generated when the folder config/BloodMagic/meteors/reagents/ is not present.
7
+
This file and the other default meteor reagent configs (crystallos.json, incendium.json, orbisTerrae.json, tenebrae.json, and terrae.json) are generated when the folder config/BloodMagic/meteors/reagents/ is not present. Delete that folder if you want to regen these files with default values.
8
8
9
-
Remember that you need to use the Alchemic Calcinator to turn the reagent items into AR to be able to put into the Master Ritual Stone for them to have any effect. Also remember that only up to three different reagents may be in a Master Ritual Stone. Try the Alchemic Segmenter to make dealing with multiple reagents easier.
9
+
Remember that you need to use the Alchemic Calcinator to turn the reagent items into AR to put them into the Master Ritual Stone for them to have any effect. Also remember that only up to three different reagents may be in a Master Ritual Stone at a time. Try the Alchemic Segmenter to make dealing with multiple reagents easier.
10
10
11
11
If you are a player, feel free to delete this file. Nothing should fail to load for any of these configs like might happen with the default meteor ones.
12
12
@@ -15,27 +15,30 @@ If you are a pack creator, the instructions on how to create your own custom met
15
15
##############################################
16
16
### Custom Meteor Reagent File Specification ###
17
17
##############################################
18
+
------------------------------------------------
19
+
reagentName.json: These config files have more strict naming than the ones for meteors. You MUST name your file reagentName.json (using the reagent's internal name, case sensitive) to define how that reagent acts when summoning a meteor.
18
20
19
-
reagentName.json: These config files have more strict naming than the ones for meteors. You MUST name your file reagentName.json (using the reagent's internal name) to define how that reagent acts when summoning a meteor.
21
+
The easiest way to find a reagent's internal name is to look up crystal belljars in NEI and check their tooltips.
22
+
This config system *should* be able to account for custom reagents that you make if you register them in ReagentRegistry, but that is well beyond the scope of this guide.
20
23
21
-
The easiest way to find the internal reagent names is to look up crystal belljars in NEI and check their tooltips.
22
-
This config system *should* be able to account for custom reagents that you make if you can figure out how to register them, but that is well beyond the scope of this guide.
24
+
Your file must contain a valid JSON object, and the properties within will define that reagent's characteristics when used to summon a meteor.
25
+
If you don't know how to read/write JSON, look at the default files as a reference or check out https://www.w3schools.com/js/js_json_intro.asp or any other online tutorial.
23
26
24
-
Your file must contain a valid JSON object, and the properties within will define that reagent's characteristics when used to summon a meteor. If you don't know how to read/write JSON, look at the default files as a guide or check out https://www.w3schools.com/js/js_json_intro.asp or any other online tutorial.
27
+
Reagents that you intend to only use for unlocking blocks in Meteor Component arrays do not need to have a file in config/BloodMagic/meteors/reagents/. Putting an empty one here anyway will not change any behavior.
25
28
26
-
Reagents that you intend to only use for unlocking blocks in Meteor Component arrays do not need to have a file in config/BloodMagic/meteors/reagents/, but putting an empty one here anyways will not hurt anything.
29
+
Note that all reagents supplied to the Master Ritual Stone are still consumed whether they change anything or not.
27
30
------------------------------------------------
28
31
"filler": Array of Meteor Component Strings
29
32
30
-
Reagents with "filler" properties will *entirely replace* the filler of meteors they are used to summon.
33
+
Reagents with "filler" properties will *entirely replace* the filler of any meteor they are used to summon.
31
34
32
-
Only has an effect on meteors that have a fillerChance above zero, but they are still consumed.
35
+
Only has an effect on meteors that have a fillerChance above zero (set directly or derived from maxWeight).
33
36
34
37
The same format as the "ores" and "filler" properties of meteors must be used:
For best results when combining reagents, try to ensure that all reagent filler arrays you define have the same total weight. Default configs use a total of 180 because it is highly composite, but any number may be used.
41
+
For best results when players combine reagents, try to ensure that every reagent filler array you define (across every reagent) has the same total weight. Default configs use a total of 180 because it is highly composite, but any number may be used.
39
42
40
43
Meteor Components in a reagent's "filler" property CAN depend on other reagents being present!
41
44
If all reagents used to summon a meteor have "filler" properties that *only* contain Meteor Components with reagents that are not present (so they all end up becoming empty), then the meteor's original filler list will be unchanged.
@@ -53,7 +56,7 @@ Default value if not included in a config is 0.
53
56
54
57
Modify the filler chance of the summoned meteor. This is similar to how (Orbis) Terrae increased the max weight, except the numbers are smaller by a multiple of 10 (Orbis Terrae has a fillerChanceChange of 20 instead of adding 200 weight).
55
58
The full formula is newFillerChance = 100 * (fillerChance + change) / (100 + change).
56
-
For example, a meteor with a fillerChance of 50 and supplied with Orbis Terrae will have a new fillerChance of ~58%.
59
+
For example, a meteor with a fillerChance of 50 which is summoned with Orbis Terrae will have a new fillerChance of ~58%.
57
60
58
61
Will not add filler to meteors with a fillerChance of 0.
59
62
Setting a value of -100 will completely remove filler (to avoid division by zero).
@@ -66,23 +69,31 @@ Default value if not included in a config is 0.
66
69
"rawFillerChanceChange": Float (+/-)
67
70
68
71
Directly add or subtract from the summoned meteor's fillerChance.
69
-
For example, a meteor with a fillerChance of 50 supplied with a custom reagent with rawFillerChanceChange set to -12.5 will have a new fillerChance of 37.5.
72
+
For example, a meteor with a fillerChance of 50 summoned with a custom reagent with rawFillerChanceChange set to -12.5 will have a new fillerChance of 37.5.
70
73
71
74
Only the single largest increase and single largest decrease will impact the summoned meteor.
72
75
This is inspired by how Orbis Terrae completely overshadowed the effects of Terrae in the old system.
73
76
74
77
Default value if not included in a config is 0.
78
+
79
+
Unused in any default reagent configs.
75
80
------------------------------------------------
76
81
"disableExplosions": true/false
77
82
78
83
Entirely disables explosions caused by a meteor summoned with any reagent that has this property set to true.
79
84
85
+
Default value if not included in a config is false.
86
+
80
87
Unused in any default reagent configs.
81
88
------------------------------------------------
82
89
"invertExplosionBlockDamage": true/false
83
90
84
91
Inverts the setting B:doMeteorsDestroyBlocks in config/AWWayofTime.cfg for meteors summoned with a reagent that has this property set to true.
85
92
May be used to make normally dangerous meteors safe, or can be used as a tradeoff to unlock a powerful effect when meteors are normally safe.
86
93
94
+
Overshadowed by disableExplosions if any reagent used to summon the meteor has it set, since there will be no explosion for blocks to break/not break.
95
+
96
+
Default value if not included in a config is false.
Copy file name to clipboardExpand all lines: raw/meteors/README
+37-31Lines changed: 37 additions & 31 deletions
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,9 @@
4
4
5
5
"Meteor happens" - xQc
6
6
7
-
This file and the other default meteor configs (StoneBlockMeteor.json, IronBlockMeteor.json, DiamondMeteor.json, and NetherStarMeteor.json) are generated when the folder config/BloodMagic/meteors/ is not present.
7
+
This file and the other default meteor configs (StoneBlockMeteor.json, IronBlockMeteor.json, DiamondMeteor.json, and NetherStarMeteor.json) are generated when the folder config/BloodMagic/meteors/ is not present. Delete that folder if you want to regen these files with default values.
8
8
9
-
If you are a player and the pack does not include certain ores in the default meteors (like cinnabar and amber from Thaumcraft in DiamondMeteor.json), feel free to remove those entries in the "ores" property for that meteor so that they don't send warnings that they can't be found to the log. Also feel free to delete this file.
9
+
If you are a player and your pack does not include certain ores in the default meteors (like cinnabar and amber from Thaumcraft in DiamondMeteor.json), feel free to remove those entries in the "ores" property for that meteor so that they don't send warnings that they can't be found to the log. Also feel free to delete this file.
10
10
11
11
If you are a pack creator, the instructions on how to create your own custom meteors are below.
12
12
@@ -15,50 +15,52 @@ If you are a pack creator, the instructions on how to create your own custom met
15
15
######################################
16
16
----------------------------------------
17
17
FileName.json: Name your file anything you like with the extension ".json" and place it in config/BloodMagic/meteors/.
18
-
Choose something descriptive for the file name; the Focus Item is often a good choice, but it can be anything.
18
+
Choose something descriptive for the file name; the Focus Item is often a good choice, but it can be anything. IronIngot.json, RAINBOWS.json, and NewMeteor2026.json are all valid names, but meteor.txt is not, as it does not end in .json.
19
19
20
-
Your file must contain a valid JSON object, and the properties within will alter the meteor's characteristics.
21
-
If you don't know how to read/write JSON, look at the default files as a guide or check out https://www.w3schools.com/js/js_json_intro.asp or any other online tutorial.
20
+
Your file must contain a valid JSON object, and the properties explained below will alter the meteor's characteristics.
21
+
If you don't know how to read/write JSON, look at the default files as a reference or check out https://www.w3schools.com/js/js_json_intro.asp or any other online tutorial.
22
22
----------------------------------------
23
23
"ores": Array of Meteor Component Strings
24
24
25
25
The most complicated and most important thing to define for your meteor: the main blocks it places.
26
26
27
27
These two formats (which can be mixed and matched in the same "ores" property) may be used to specify a Meteor Component (a block, its associated weight, and any required reagents):
modId:itemName:meta:weight(:reagent1, reagent2, ... optional) - Note: specifying meta is REQUIRED, even if 0
29
+
OREDICT:oreDictName:weight(:reagent1, reagent2, ... optional) - Note: OREDICT: at the front stays the same, only replace oreDictName
30
30
31
-
For example, the following "ores" property will place iron and gold ore in a 2:1 ratio and will add end stone when either sanctus OR magicales is provided (resulting in a ratio of 2 iron : 1 gold : 1 end stone):
31
+
For example, the following "ores" property will place iron and gold ore in a 2:1 ratio. It will also add end stone when either sanctus OR magicales is provided (resulting in a ratio of 2 iron : 1 gold : 1 end stone):
32
32
"ores": [
33
33
"OREDICT:oreIron:200",
34
34
"OREDICT:oreGold:100",
35
-
"minecraft:end_stone:100:sanctus, magicales"
35
+
"minecraft:end_stone:0:100:sanctus, magicales"
36
36
]
37
37
38
-
Reagents that you intend to only use for unlocking blocks in Meteor Component arrays do not need to have a file in config/BloodMagic/meteors/reagents/, but putting an empty one there anyways will not hurt anything.
38
+
Reagents that you intend to only use for unlocking blocks in Meteor Component arrays do not need to have a file in config/BloodMagic/meteors/reagents/. Putting an empty one there anyway will not change any behavior.
39
39
40
-
If the "ores" property is not present, is set to be empty, or if it contains only blocks with reagents that are not provided (so it would be empty), the block specified with S:defaultMeteorBlock in config/AWWayofTime.cfg will be used as a default (minecraft:stone is used as a fallback if the config is unset or if the specified block can't be found).
40
+
If the "ores" property is not present, is empty, or if it contains only blocks with reagents that are not provided (so the meteor would have no blocks to place), the block specified with S:defaultMeteorBlock in config/AWWayofTime.cfg will be used as a default. minecraft:stone is used as a fallback if the config is unset or if the specified block can't be found, such as minceraft:breadrock.
41
+
42
+
Try using the command "/iih" ("item in hand") from GTNHLib or "/mt hand" from MineTweaker while holding an item to get its modId, itemName, and meta automatically put in your clipboard.
41
43
----------------------------------------
42
44
"filler": Array of Meteor Component Strings
43
45
44
-
Just like the "ores" property, you can define custom blocks to be used as filler. Uses the same format to define Meteor Components, so you can set different blocks in the filler list to have different relative weights or require specific reagents.
46
+
Just like the "ores" property, you can define custom blocks to be used as filler. Uses the same format to define Meteor Components, so you can set blocks in the filler list to have different relative weights or require specific reagents.
45
47
46
-
All filler blocks will be replaced if a meteor is summoned with a reagent that is configured to have its own filler list (incendium, tenebrae, and crystallos with the default configs).
48
+
ALL filler blocks in a meteor will be replaced if it is summoned with a reagent that is configured to replace filler (incendium, tenebrae, and crystallos with the default configs).
47
49
48
-
Uses S:defaultMeteorBlock in config/AWWayofTime.cfg as the default filler block just like the ores property.
50
+
Uses S:defaultMeteorBlock in config/AWWayofTime.cfg as the default filler block, just like the ores property.
49
51
----------------------------------------
50
52
"fillerChance": Floating Point Number from 0.0-100.0 inclusive
51
53
52
-
Definez the chance (out of 100) that any block placed will pick a block from the "filler" property instead of the "ores" one.
53
-
A value of 50 means the meteor will be 50% filler, 75 means the meteor will be 75% filler, etc.
54
+
Defines the chance (out of 100%) that any block placed will pick a block from the "filler" property instead of the "ores" one.
55
+
A value of 50.0 means the meteor will be 50% filler and 50% ores, 75.5 means the meteor will be 75.5% filler and 24.5% ores, etc.
54
56
Default value if not specified is 0.
55
57
56
58
fillerChance of 100 means that the whole meteor will be filler. The "ores" list will not show up in NEI.
57
59
fillerChance of 0 means that the whole meteor will be ore. The "filler" list will not show up in NEI.
58
60
----------------------------------------
59
61
"maxWeight": Positive Integer
60
62
61
-
IGNORED when fillerChance is defined in the same meteor.
63
+
IGNORED when fillerChance is defined in the same meteor. It's recommended to use that property for new meteors instead of this one.
62
64
63
65
An alternate way to specify the fillerChance which is similar (but NOT identical) to the old weight system.
64
66
The formula used to turn maxWeight into fillerChance is 100 * (1 - (total ore list weight / maxWeight)).
@@ -71,41 +73,45 @@ For example, this example "ores" property has a total list weight of 400:
71
73
"minecraft:log:2:100",
72
74
"minecraft:log:3:100:virtus"
73
75
]
74
-
With a maxWeight of 1000, the resulting fillerChance would be 60%.
75
-
With a maxWeight of 600, the resulting fillerChance would be about 33.3%.
76
+
Setting maxWeight to 1000 for that meteor would result in a fillerChance of 60%.
77
+
Setting maxWeight to 600 for that meteor would result in a fillerChance of 33.33%.
76
78
77
-
This does NOT account for blocks over the max weight requiring (Orbis) Terrae like the old system. Specify that the blocks require them in the Meteor Component string if you want that functionality.
79
+
This does NOT account for blocks over the max weight requiring (Orbis) Terrae like the old system. Specify that the blocks require the reagent in the Meteor Component string if you want that functionality.
78
80
This does NOT account for blocks that are not present because they are missing reagents. The above example with a maxWeight of 1000 will have 60% filler whether or not you supply virtus.
79
81
80
-
This DOES account for blocks that can't be found when reading the configs and is used in the default configs for that purpose. I recommend only using this if you expect something similar to happen with your meteors.
82
+
This DOES account for blocks that can't be found when reading the configs. It is used in the default meteor configs for that purpose. It is recommended to only use this if you expect something similar to happen with your meteors.
81
83
----------------------------------------
82
84
"radius": Positive Integer
83
85
84
86
Sets the radius (in full blocks out from the center block) of your meteor.
87
+
A meteor of radius 5 will have a full diameter of 11, including the center block.
88
+
A meteor's radius is also used to calculate the strength of the explosion when it lands if that feature is enabled. The explosion strength is 4 * radius.
85
89
86
90
Default value is 1 if the property is not set, which will create a very wimpy meteor.
87
91
----------------------------------------
88
92
"cost": Non-Negative Integer
89
93
90
94
Sets the LP cost to summon this meteor.
91
95
92
-
Value if not defined in a meteor's config may be set by I:defaultMeteorCost in config/AWWayofTime.cfg.
93
-
Default value for that config is 1000000 LP.
96
+
Uses I:defaultMeteorCost in config/AWWayofTime.cfg if this property is not set.
97
+
The default value for that config is 1,000,000 LP.
94
98
95
-
Remember that Mark of the Falling Tower takes 100k LP to activate by default. A player can activate it and leave the sacrifice of the Focus Item until after more LP has been added to the soul network.
99
+
Remember that Mark of the Falling Tower takes 100k LP to activate by default. Keep in mind that players can activate the ritual and leave the sacrifice of the Focus Item until after more LP has been added to their Soul Networks.
96
100
----------------------------------------
97
101
"focusItem": String in format "modId:name(:meta optional)"
98
102
99
103
The Focus Item is the block/item sacrificed to summon the meteor. Avoid configuring multiple meteors to use the same item, because only one will actually be able to be summoned in-game.
100
-
Different metadata of the same item works fine, such as having multiple meteors summoned with different colors of wool.
104
+
Having different focus items with the same ID but different metadata works fine, such as having multiple meteors summoned with different colors of wool.
105
+
Specifying Focus Items based on NBT is not currently possible.
106
+
Specifying Focus Items based on oredicts is not currently possible.
101
107
102
108
As an example, a meteor with this value for "focusItem" will require a birch log:
103
-
"minecraft:log:2"
104
-
105
-
The default value for meta is 0 if not provided. A meteor with this value for "focusItem" will require coal and charcoal (which is the same item ID with a metadata of 1) will not work:
106
-
"minecraft:coal"
109
+
"focusItem": "minecraft:log:2"
107
110
108
-
Setting meta to 32767 will act as a wildcard for the item's metadata. If meta is set to 32767 in the above example, oak, birch, spruce, or jungle logs will all be valid items to summon this meteor (because they all have the same block ID).
111
+
The default value for meta is 0 if not provided. A meteor with this value for "focusItem" will require coal:
112
+
"focusItem": "minecraft:coal"
113
+
Charcoal (which is the same item ID with a metadata of 1) will NOT work.
109
114
110
-
There is currently not support for using oredicts for Focus Items.
115
+
Setting meta to 32767 will allow any item with the same ID. For the following example, oak, birch, spruce, and jungle logs will all be valid items to summon this meteor (because they all have the same block ID):
0 commit comments