Topics

[Extended Woodworking]

Extended Woodworking

Description

This mod extends trees so that they drop different types of wood based on the tree they are. This mod also allows you to paint wood into 6 different colours (Red, Green, Blue, Yellow, White, Black) which you can use to build various things.

A woodworking table has been added to allow you to convert the different wood types into normal wood so you can still build the various buildings that require normal wood to be built. You can also paint wood at that table.

Mod Team

    TeflonJim - Updates from A13 to current
    ItchyFlea - Code (A13)
    Silvermane - Fence & FenceGate Textures

Download

https://github.com/indented-automation/ExtendedWoodworking/releases

Changelog

v5.0.3

• Redesigned to use XML patching
• Integrated VGP add-on as a patch using ModCheck
• Added support for a number of other mods
• Added ModSync.Ninja support

Perhaps the wrong place, but I wrote this to find some conflicts I bumped into so I thought I'd share it in case it's of use to anyone.

Indented.RimWorld is a PowerShell module which reads module information from the RimWorld game directory. The following functions / CmdLets are exposed:

Set-RimWorldDirectory - Set the working directory for functions in this module.
Get-RimWorldMod - Get information about RimWorld mods from the game directory.
Get-RimWorldModDef - Get Defs from the mod.
Compare-RimWorldModDef - Compares Defs across mods.

If you haven't worked with PowerShell before this requires:

.NET Framework 4.5 (required for PowerShell 4)
Windows Management Framework 4 (http://www.microsoft.com/en-gb/download/details.aspx?id=40855)

These steps are required because it's the version I run and I'm too lazy to find something earlier. It should work under PowerShell 3, but the PS version requirement in the manifest (.psd1 file) would need changing.

To install:

1. If it doesn't exist, create "My documents"\WindowsPowerShell\Modules
2. Extract the content of the attachment to the new folder
3. Start PowerShell
4. Run "Import-Module Indented.RimWorld"

The module is signed so your code signing policies should not matter.

Help on specific functions is available using:

Get-Help Get-RimWorldMod
Get-Help Get-RimWorldMod -Full
Get-Help Get-RimWorldMod -Examples
Get-Help Get-RimWorldMod -Parameter ModName
etc

I intend to see if I can add in the ability to merge mod definitions (depending on free time). At the moment I use it to debug mod conflicts.

I imagine I can make it look for conflicting class / namespace use in the assemblies too, but I haven't noticed a problem with anything like that so far.

Cheers!

[attachment deleted by admin: too old]