There is an extra boolean in the render method that flips entities. That extra boolean involves the enabling/disabling of capes. If the condition isn't met, then they will not be flipped. This applies to Dinnerbone as well.
-
- MitchellbrineTheCreator
- Registered Member
-
Member for 11 years, 9 months, and 12 days
Last active Wed, Dec, 28 2016 13:31:53
- 3 Followers
- 261 Total Posts
- 28 Thanks
0
Which version are you using? (Also, since recent versions, it will use the native file inside the .jar file in the mods folder)
If your medication json question involves the medication json files:
- Medication JSON files act similarly to Disease JSON files in that you can add as many different medications as you possibly can)
- OR you can have multiple medications that treat the same disease (and balance the recipes as needed).
0
That means a mod isn't obviously causing an error. If there are "E"s at the end of mod names, that means that mod is DEFINITELY the culprit. It is a nice addition Forge added to hopefully lessen the modder's use of the "Not My Issue" card.
0
The .json files can be named whatever you want (so long as the medication json files are in the /DiseaseCraft/Medication/ folder in your Minecraft folder and the disease json files are in the /DiseaseCraft/ folder).
Disease JSON files can contain as many diseases as you can fit inside the document. It's basically limitless until you run out of storage (or cause the game to become super slow in calculations).
Can you post the parameters for your custom disease? I feel it's a incompatibility with the version (2.2.0.2a includes the new system for disease parameters in mob and mobAttack variations. This means that if you are using the old version of the parameters, it won't work and will throw a NPE.
Like what I said in #94, those config options are there to lower the amount of calculations the mod performs and can even disable them if needed. That greatly improves performance (and has no impact on the gameplay of the mod as is). If you are using 2.1 or 2.0, try upgrading or posting any debug messages that might appear in the game log (because I might have left some in there).
0
The wiki is missing diseased crops (due to it being in the new alphas), but in short, they're random plants in the world that are "infected" and act as a condition for custom disease contraction. Currently the plants are unused, but are in the code. I need to get onto that.
The contraction table doesn't exist yet (because it will be very large), but you can check the medical journal and the native JSON files to see how the changes work on disease contraction. There is a consumption contraction type as well (as seen in Pneumonic Plague):
{ "name":"pneumonicPlague", "level":2, "minVersion":2.0, "effects":[ 2, 4, 18, -4 ], "contracting":[ { "type":"eaten", "parameters":[ "minecraft:porkchop", 0, 950000 ] } ], "deathRate":50, "lore":"Yersinia Pestis,\nViolent than the fleas\nFor animal bacteria\neverywhere it seems." },The parameters for the "eaten" type are as follows:
1. Item (Item ID or name)
2. Item Metadata
3. Chance (out of 1,000,000,000) <<< 1,000,000,000 is a number I chose a long time ago for all diseases and thus, I haven't changed it much. It is greater than or equal to that number (so that's 50,000 out of 1,000,000,000 or 0.005% chance of it happening)
There are other types of disease contractions that can be found here.
And the answer to what ID coughing is -5 (the rest of them can be found here).
0
Okay, so in the configs, there are 3 values that you can change to decrease the amount of time that the server will take to calculate diseased crops (I'm assuming you're using the versions after 2.1 (the recommended, or else, I really don't know what could be causing it).
These 3 values are:
diseasedCropsRadius
doDiseasedCrops
diseasedPlantsChance
The first two lower (or nullify) the calculations every x seconds that the game will check for crops that can become diseased. diseasedPlantsChance is the amount of seconds between each calculation. If you disable doDiseasedCrops (and get rid of the diseaseCrops file in your world), it should not be doing the server-side calculations and raise your TPS. No diseases at the moment use diseased crops, so gameplay shouldn't be affected.
If you are using 2.1 or 2.0, then I recommend trying to upgrade and seeing if the problem persists (especially with the configs).
In regards to the crash, I have no idea what's causing that. Try removing Optifine first and then, if it still occurs, report it at this location with more information.
0
1. Are you sure it was because of DiseaseCraft and not another mod?
2. Have you tried using the built-in config options to enhance performance?
3. Are you sure you don't mean tps? DiseaseCraft rarely touches rendering, but sometimes can do a handful of calculations that might tax a system (hence my adding performance-enhancing configs).
0
Oh, this is actually a fairly simple fix. Is there a DiseaseCraft.json in the DiseaeCraft/ folder?
If so, delete it, so it uses the native file within the alpha.
Or you can replace the file with this one.
(The two crashes in #86 are because of a change in format in the recent version of DiseaseCraft. I'll be sure to add in a way for the mod to check if an old format is being used in the next version. Thank you for the report).
0
The two problems aren't related, but I think I think the pastebin crash is due to an incompatibility with that LycaniteMobs mod.
It seems that an incompatibility might be the cause of the crash (since I cannot reproduce the crash in my dev environment). I really don't know if the problem is on my end (since vanilla mobs seem to work fine in the testing environment). It might be due to sloppiness on the modder adding the mob (I use the classToStringMapping and some mods might bypass that, which could mess everything up (even though I made sure to double check these things beforehand)).
The empty string error points to line 32 in the MedicationRecipes class points to
which does not involve an NBTString at all. Can I get a version number (and if it is outdated, could you try it in the most recent alpha version)?
I seem to be a step closer to solving that first problem (well, solving as much as I can, since it might just be sloppy modding technique). The second problem is probably an easy fix if I can get an updated crash log on it.
0
Okay, so Optifine isn't causing it. Now, to confirm:
If not, then I need to know:
From both of your crash reports (which include the same error and stacktrace), not of my mod classes are visible in the crash or stacktrace and, according to FML, it has not errored. If you can provide me with that information, I could get a better sense of this issue and quickly resolve it.
0
Please try without Optifine. That mod messes with a lot of stuff it shouldn't. If it still occurs, then re-report with some background to how/when this happened (e.g. startup, loading world, etc.)
0
Head to the CurseForge page and download the version under the red "A". That would be the alpha. 2.1 is the latest recommended version, but it still has the bug. The alpha is pretty much stable (bar a few performance issues that I'm addressing at the moment).
0
Try with the new alpha (I'm pretty sure it was fixed in the last alpha version). If not, then please report it on the GitHub issue tracker here.
0
Chemical Extractor + Hold Right Click + View tooltip
That should work (unless I forgot to include that in the migrated changes in 2.2). That should work in the latest alpha.
1
Ah, an easy fix. I'll get right on it. Thank you so much for reporting the bug! (Now, it is a bug with Lycanite's mobs, but it can be prevented on my end)
0
Okay, I've seen this problem and I believe I fixed it in the newest version of the mod. I'm going to be releasing an alpha in the next couple of days that should fix it.