Brady_The

I think the house looks pretty great. The first floor is a bit oppressive in size, overpowering the ground floor with its volume. Make the ground floor a bit taller and see how it changes the view.

Unfortunately you cannot at this time.

Alright, now we are getting somewhere. Where is the patch file located? It should be in "craftsmanship\assets\craftsmanship\patches". Sub-folders in the patches folder are okay. Also, test it without any extra mods to make sure that it is not some other mod messing with the drifter file.

Make sure that you are using the correct asset type and code, and that the asset is available.

What's most likely missing in your case is the correct command. "/giveitem" is for items. Blocks require the command "/giveblock". The next hurdle would be the correct asset code. The easiest way to obtain those would be via Creative Inventory. However, if you don't have any admin powers, the next best way would be to execute the command ".edi" in chat. This adds among other things, the page code of assets to their handbook pages. This gives you two information. Is it a block or an item. What is the asset code. With those you can now spawn the aged wooden bed (or any other asset). /giveblock bed-woodaged-head-north, followed by the quantity if you need more than one and the target, if you are not giving the bed to yourself. "/help" giveblock" in the ingame chat will help you with any optional parameters.

That looks correct. How did you ascertain that the drop is not working?

Drops are a bit different for entities. Those are handled on the server side. So you would have to address "/server/behaviors/9/dropsByType/*-normal/-" if, for example you would want to add drops to the normal drifter. Because you are patching a game file you don't need to add the game domain in front of asset codes.

You could do it in such a manner, however, it would have a huge downside. If you place the drifter file in "yourmod/assets/game/entities/lore" you would overwrite the Vanilla drifter. If the developers should ever decide to change the drifter, players using your mod would never experience those changes because the original file is overwritten. This could also cause problems with other mods modifying the drifter file. You want to patch the original file instead: https://wiki.vintagestory.at/index.php/Modding:JSON_Patching This way the original file is not replaced, but modified only in the areas you chose to address. You could utilise the ModMaker, which you can find in the installation directory, to create patches for you based on edited Vanilla files.

According to the comments this mod doesn't work any more. I wouldn't count on an update any time soon: https://mods.vintagestory.at/reignited#cmt-22612

The scrambled eggs recipe works for me. Start a completely mod-free test world, switch to creative and test again. "/giveblock firepit-cold" lets you skip the firepit building part. If it works there, you have conformation that a non-cooking mod is apparently messing with cooking.

That's Compatibility Lib's moment to shine. I am currently rewriting the article, because it is a bit archaic. Here's a sneak preview: https://wiki.vintagestory.at/BradyThe/Sandbox (It's still a work in progress, but hopefully explains the inner workings of the Comp Lib already a bit better.) How I would go about it depends a bit on the structure of the other mod and your goals. Remove recipes from the other mod: Easy. I would probably use Mod-dependent json-patches (JSON Patches in my rewrite) to disable them. Combine/replace item: Easy - medium: There are one or two solutions to this. Overwrite the 3rd-party item with the Comp Lib. Put all properties of both items (the 3rd-party and yours - combine) into this file. Disable your item via patch. Add recipes into the compatibility folder using the item code of the overwrite. Disable the 3rd-party item with a patch, add any properties of the 3rd-party item you want in yours (combine) to your item by patch. Example setup (I quickly frankensteined an existing test setup, pay no regard to any domain or other inconsistencies): I hope all of this isn't too theoretical only making sense in my mind. If you have any questions, shoot them.

You select the backDropShape that has been used in the shape and potentially look into the clothing itemtypes to see what the dev did to the clothing in the background. Edit: I assume the shape you looked at step parented parts of the shapes to the backdrop shape so that the clothing item shows up properly on the player/npcs. Without backdrop present those parts might reset to a default position at 0,0.

As I expected there's nothing obvious popping up in the logs. Besides the usual lot of warnings and errors due to outdated or broken mods. I would reinstall the game. I see a lot of audio errors. It is very possible that this will fix not the recipe issues, though. If that's the case, employ the binary search meethod I mentioned above to find the culprit.

I don't think that it will cause any real damage, but I would still look through my mods and find out which one is causing it, to notify the author about this error.

Oh. To be fair, I haven't done any handbook texts yet, so I only orientated myself on other mod. I should have taken a look at the wiki page... Anyway, you can do it both ways. I don't think that there are any advantages or disadvantages to either of them. You just have to settle for one. { "pageCode": "brady-test", "title": "brady-test-title", "text": "bradya:brady-test-text" } { "game:brady-test-title": "Test title", "brady-test-text": "Test text" }

It's possibly a mod with a broken recipe file. Some errors can break seemingly random recipes. The link to your mod list doesn't work. Something else could be going on, though. If you want you can share your client-main and server-main log files here. However, those do not necessarily point towards the source of the error. I would suggest to perform a binary search to find the culprit.

The domains shouldn't be needed here. game:mechanici...

Are you sure you are looking at an up variation of your scrap slab and not a down variation? Hit Ctrl+F3 and look at the block in question. The block info alone is not too precise. For some reason the game will only display one iteration of the block as the asset code, which is not necessarily the correct one. up-snow variations are not created because their top is at the height of a full block. Snow will cumulate on top naturally. The down and cardinal direction versions are special cases, because they are lower or smaller than normal blocks, which would result in strange results, floating snow and the like. Anyway, if you added a scrap texture for the plankslab correctly (/texture/block/wood/planks/scrap.png) you shouldn't get any errors. What do the logs tell you? Texture issues should pop up in client-main, but it's always good to keep an eye on server-main as well.

Hey Eranderil, welcome to the forum! The game is utilising command blocks for the eidolon fight. https://cdn.imgchest.com/files/e0714a145670.jpg I'd load into a testing world, go into Creative mode, head to the Resonance Archive and have a look for myself. Shift+Right Click should open the Edit interface. Here are some more information: https://wiki.vintagestory.at/Command_block I haven't used those before, so I cannot tell you if that is all you need. It's still a decent place to start, I'd say.

clientsettings.json in %AppData%\VintagestoryData

The VTML code could be counting towards the character limit per site. I'd do some testing with and without the code and see if there's a difference. There most likely will be. Then I would report my findings on https://github.com/anegostudios/VintageStory-Issues/issues. The devs most likely didn't think that VTML would be that heavily used. That should be an easy enough fix on their end, though.

Don't forget to report the crash on the mod page so that the author knows about and can fix it.

You are most likely running into the problem of escaping certain characters. Quotes in particular. This will break the language string: Because quotes are used in starting and ending a key, but are also used in certain VTML values, which when improperly used will confused the game because it assumes something is ending or starting when it really isn't. "lore-miller-piece1": "<font color="#b5e61d">The</font> <font size="25" weight="bold" color="#c36">Pond</font>[...] This will not: With a backslash you will tell the game to ignore or interpret any following character differently. "lore-miller-piece1": "<font color=\"#b5e61d\">The</font> <font size=\"25\" weight=\"bold\" color=\"#c36\">Pond</font>[...] You might find this mod interesting: https://mods.vintagestory.at/vtmleditor (Edit: The mod works with any language string loaded in the game, so mods should theoretically supported.)

That's not the correct code. See skipVariants. You want to look at mushroom-side.json.

That depends what you mean with grouping. You can consolidate blocks/items in the ingredients section in the handbook. "attributes": { "handbook": { "groupBy": ["seashell-{type}-*"] } } You cannot condense the handbook entries too many ways. You can filter out variants of assets, showing for example only north-orientated assets "creativeinventory": { "general": [ "*-north" ] } Technically you can "excludeByType" assets, but that'll remove the handbook entries completely (which doesn't make them uncraftable btw). "attributes": { "handbook": { "excludeByType": { "*-eidolon": true, "*-erel": true, "*-seamonster": true, "*-thunderlord": true } } } But that's about it.