Tutorial Basic Patching Now With Path Guide [v1.9]

I love how you guys are so open with explaining the innards of your game. It really helps us understand how it works and improves our ability to report bug as well as create mods.

 

True, but if I use includes, doesn't that mean that the mod is loaded immediately after the "included" mod, so that a given item is guaranteed to be in a certain position in an array?

 

No, because if two mods load the same include then it will be loaded immediately before whichever mod tries to load first. Also if a mod loads both includes and requires then the requires are loaded after the includes.

For clarity, here is the mod sorting code in use in the current revision. I don't expect it to change (though it might).

http://pastebin.com/a3m6hHp2 (the forums eats the indentation)

 

This all sounds very complicated...I think I'll just stick with writing independent mods.

 

does anyone know the new way to do nocollision with the physics.config? this is what I've got but it's incorrect
[
"nocollision" : {
"gravityMultiplier" : 0.0,
"bounceFactor" : 1.0,
"maxMovementPerStep" : 0.4,
"groundSlideMovementEnabled" : false,
"collisionPoly" : [],
"ignorePlatformCollision" : true,
"groundFriction" : 0,
"airFriction" : 0,
"liquidFriction" : 0,
"speedLimit" : null
}
]

 

thx for taking time to reply but i actually already figured out the issue with the patch tester link

 

I was having a similar issue.

The base file I was trying to patch was cobblestone.matitem:

Code:

{
  "itemName" : "cobblestonematerial",
  "rarity" : "Common",
  "inventoryIcon" : "cobblestone.png",
  "dropCollision" : [-2.5, -2.0, 2.5, 2.0],
  "shortdescription" : "Cobblestone",
  "description" : "Hard stones, smooth to the touch.",
  "glitchdescription" : "Statement. Cobblestones.",
  "florandescription" : "Cobblessstone.",

  "materialId" : 3
}

Originally my code was:

Code:

[
  {
  "op":"add",
  "path":"/learnBlueprintsOnPickup/-",
  "value":"masonrytable"
  }
]

Which would not get parsed correctly using the tester. However, based on what you'd posted, I changed the code to:

Code:

[


  {
  "op":"add",
  "path":"/learnBlueprintsOnPickup",
  "value":[]
  },

  {
  "op":"add",
  "path":"/learnBlueprintsOnPickup/-",
  "value":"masonrytable"
  }


]

And this worked. It was a bit of a nuisance, as I have trouble as it is understanding the patching system, as I've not used it before really, even when it was added.[DOUBLEPOST=1433247163][/DOUBLEPOST]Also, couldn't this thread be stickied?*

 

Sorry, I did look in that thread but must have missed it, I'll have a look again in a minute.

Thanks, I tried something similar but I think hadn't used the brackets properly at some point, so that must be where I got confused.

 

I think he said NOT stickied? Dunno why you'd want to do that though

 

So we can't simply replace a whole JSON if we are making bulk changes anymore???

 

That's a good point! I didn't think about compatibility. Thank you moderator!

 

I'm having an issue with one of my mods. I'm trying to add a custom ore to the moon yet it's not spawning at all. I tested the ore spawns on normal worlds and it does spawn just fine. I'm thinking I'm getting the path wrong for the moon layers.
"path" : "/moonores/0/1/-",
and
"path" : "/moondeepores/0/1/-",
is what I'm using. Is this right or?
Or is there anything extra I need to do to get it to spawn on the moon? I also tried to ass a small amount of coal to the moons as well with no luck

 

..........why don't people read? I swear it is not that hard to read. Bad when it's a moderator. >.< I'll say right now I get really REALLY sick and tierd of having to repeat myself because people don't freaking READ. Please stop skimming and assuming and read what people freaking say! Sorry if this sounds rude or such but I see this happen all the freaking time to myself and other people!

So round 2. I'm not talking about rather or not my json is correct or not. I already said I tested it first on
"path" : "/surfaceOres/0/1/-",
and it worked FINE. Spawning the ore on the worlds surfaces.

it's adding it to the MOON where I want it that its not spawning.
Like I said I think the PATH /moonores/0/1/- might not be the right path to make it spawn.

So, I never asked is the json right or not. I'm asking is the PATH FOR THE MOON if it is right or not. A check to see if json is valid or not isn't going to tell me that.


So sense it's going to come up, yes I used that site, it gives the exact same error each time rather the ore works or not.
"message" : "failed to apply patch",
"exceptionClass" : "com.github.fge.jsonpatch.JsonPatchException",
"exceptionMessage" : "parent of node to add does not exist",
"info" : "other messages follow (if any)"
Even when it worked fine. Shoot it throws the exact same error when I plop in custom ores from other mods. Shows the exact error no matter what path you toss in valid or not.

So yes, this don't help me, and isn't at all what I asked for.

So to make 100% clear for the people who don't want to read:



[
{
"op":"add",
"path":"/surfaceOres/0/1/-",
"value": ["erechusshard", 1.20]
}
]

THAT WORKS 100% FINE.


[
{
"op":"add",
"path":"/moonores/0/1/-",
"value": ["erechusshard", 1.20]
}
]


DOES NOT WORK. I think the PATH IS WRONG. That or there is something extra to make ores spawn on the moon as I cant even get coal to spawn when I use a simple replace in my ore rebalance mod thats already out.

 

.. the path is moonores and moondeepores, I know the path is moonores and moondeepores as it's the path listed in the oredistributions.configfunctions file. I don't know if the /0/1/- is right or not. even with out it nothing spawns.
I see nothing in the biome codes that would effect or limit what ores can spawn.

I've even done
{
"op" : "replace",
"path" : "/moonores",
"value" : [[0.5, [ [ "coal", 2.20], [ "plutonium", 0.70], [ "solarium", 0.3] ] ]]
},
{
"op" : "replace",
"path" : "/moondeepores",
"value" : [[0.5, [ [ "coal", 2.20], [ "plutonium", 0.70], [ "solarium", 0.3] ] ]]
},
that is in my current mod, and the only thing that is effected is the plutonium, no matter how high I crank the other two up they don't spawn.