Jump to content

xXx_Ape_xXx

Very supportive Vintarian
  • Posts

    304
  • Joined

  • Last visited

  • Days Won

    11

xXx_Ape_xXx last won the day on February 20 2025

xXx_Ape_xXx had the most liked content!

3 Followers

About xXx_Ape_xXx

  • Birthday October 24

Recent Profile Visitors

2752 profile views

xXx_Ape_xXx's Achievements

Steel Worker

Steel Worker (8/9)

469

Reputation

23

Community Answers

  1. Just wanted to let you know I'm still working on this, and have made some promising progress this week. Might see a release closer to the weekend, if things go as I hope.
  2. The link to your mods at the bottom of your posts is not working.

    1. xXx_Ape_xXx

      xXx_Ape_xXx

      Oh, thank you, I didn't know. Much appreciated!

  3. Made some more progress. More planned, but it's functional in current state, and looks quite good if I may say so myself https://imgur.com/60R4lQR https://imgur.com/X1GXWZK https://imgur.com/M5gfU8t Plans: Decorative stone and wooden lining along the edges Lantern stand Garden gnomes? Signs? Other things?
  4. The second recipe using clear quartz, is missing "game:" in it's declaration of ingredients. Basically, what is happening in the first example, is the game engine looks for an item in your mod called "clearquartz", and can't find it because it simply does not exist. And since the recipe sit inside your mods domain, "olivinefraud", the recipe defaults to search for items without a domain declared, inside the mod that calls it. In this case, it thinks your recipe is pointing to "olivinefraud:clearquartz" , instead of the correct "game:clearquartz" In the second example, the game engine looks for the same clearquartz, but this time inside the domain of the game itself, hence the "game:" in front of all the item names. And the recipe works. Think of domains as folders where everything inside them, belongs to that folder name. I know it can be hard to wrap ones head around this at the start, but once you get to experiment a bit, it becomes clearer. Good luck with your modding endeavour.
  5. Quick concept, auto-tiling and trowel tool to produce flowerbeds. https://imgur.com/N0REQz9 https://imgur.com/IyKSqzp https://imgur.com/g790k4s https://imgur.com/VFinkFA Early stages yet, got plans...
  6. What domain is your file containing these entries in? Try adding "game:" to all the textures and shape. Like this --> There are some inconsistencies to some parts of the rendering pipeline, where the base path is added to textures in some cases, and some not. This reminds me of one such case, as I've had similar problems.
  7. It looks like the whole shape for the bow is missing. Try adding "game:" prefix to all the shape references:
  8. Yeah it's the class "ItemKnife" that controls the harvesting of entities, so you might have to create a custom class to achieve what you want.
  9. Grass uses "dropsByType" because there are several types of grass registered by the tallgrass.json { code: "tallgrass", class: "BlockTallGrass", entityClassByType: { "tallgrass-eaten-*": "Transient" }, variantgroups: [ { loadFromProperties: "block/tallgrass" }, { code: "cover", states: ["free", "snow", "snow2", "snow3"] }, ], This results in tallgrass-veryshort-free, tallgrass-veryshort-snow etc etc The "dropsByType" matches the key to find what it drops when harvested/cut. What you want to achieve does not require "dropsByType", unless you want to have different drops for male/female types of raccoons. I've had a closer look at your files above, and there's several things that needs fixing. I'll attach them under, so you can test to see if they work now.
  10. The tool needs to be the same as in your skinningknife json: If you want to prevent a regular knife from being used, you'll need to assign a different tool type from the list I posted earlier here: In this list, there are several that are not used in the game. Try using "sickle", as that is not used by any currently available tools in the game. So change "tool: knife" to "tool: sickle" in your skinningknife.json, and same in the raccoon harvesting properties.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.