They'll probably fine so no stress. I'll fix whatever breaks, if anything does break but thanks for the heads up :D

Hey man! I'm updating the HYE version now and bringing some new weapons and stuff and I'll just put the core folders of the mod inside a new 1.6 folder which might break your patch's paths.

Didn't change defnames or anything, just put everything inside a 1.6 folder.

Not this time. Mods that overwrite the def with their own def would need to be loaded after the main mod. Since mine is handled as an operation, it doesn't matter where it goes
So I get where you're coming from. There's no need to worry with this one (thumbsup.jpg)

If it works fine for you then it should work fine for me, but I have always seen patches loaded AFTER the things they patch so I thought it would be best to be on the safe side.

Does it break something if it's loaded before the main mod? It shouldn't really matter where it goes since it uses patching methods instead of loading defs directly like other mods do.
I mean, I have it loaded before both on my side and it works fine

Rimsort also insists on putting this patch BEFORE Citizen's version like Rimpy, so you have to make a rule to have it come AFTER citizen's version.

Everything seems fine on my side. Try unsubbing from this mod and subbing again. It might fix the issue

I'll look into it

The [HYE] nanobots have a texture material error, should this be corrected by patchse or should we contact HYE or someone else?

Rimpy is an idiot. Just ignore it
Alternatively, use RimSort

Rimpy mod manager still says I need Lyn's version when I just want to use Citizen's version.

No problem :D

Thank you for your work o7

Support added

Ok, tested it myself and looks like I'll need to add a patch for some compatibility.. because texture names are different

Test it. If it doesn't, let me know and I'll figure it out and add compatibility (ok.jpg)

Does/will this have compatibility with the Nanotech fork by Citizen706, Lyn says it's better so I had switched to that one.

I made several attempts to stop the generation of the nanotiles and nanofluid which all failed. Research indicates this problem has been an issue for 6+ years for modders and requires C# help. I have zero C# knowledge so it's beyond my skill level to fix this problem.

I've noticed that too and I don't really touch the nanotiles apart from adding a tag and cleaning properties.
I'll look into it tomorrow. I'm pretty fried today

Not sure if this is an issue with this mod or the main mod, but nanotile and nanowater have been spawning in ruins with increased frequency.

It's just odd since I already have it set so I don't know why it's not updating for you

Yep, no change. I'll just change the thing manually. Its not a major issue but figured I'd mention it.

Have you tried unsubbing and resubbing?

1.6

Already did. Which RW version are you using?

You need to change defs apparently for NT_nanobots to LWNT_Nanobots cause there's a texture issue.

Good stuff :D

1.5 Def Name Problem is fixed. Thanks alot!

From what I see in the Oddysey XML, only the gravship hull is meant to be airtight if you're trying to build structures on asteroids or mechanoid platforms. Since the wall stuffed with nanobots is just vanilla wall, it won't gain the airtight property that the gravship hull has
Just build gravship hull with nanobots and it'll keep the air in

I'll see what I can do

the wall built by nano has no impermeability ，air will escape ，no matter vanilla wall or mod wall，could you please make a patch to fix it?

Thanks, let me know if it's fixed :D

The missing Texture bug with the changed Def Name seemingly still persists for 1.5. Would be great if you could Patch that too. Thanks in advance!

No problem :D

Thank you

Fixed. The problem was in the error log as well
MayRequireAnyOf should've been MayRequire so thanks for pointing that out.

Ah, no. I'll push a patch so players that don't have Anomaly won't see it

Hi does this error mean i have to buy that anomaly DLC to remove this error it seems to be looking for it. I can simply ignore it but thought maybe you wanted to know this seems to come up: XML error: Could not find parent node named "SerumBase" for node "ThingDef". Full node: <ThingDef MayRequireAnyOf="Ludeon.RimWorld.Anomaly" ParentName="SerumBase"><defName>NanoAuraSerum</defName><label>Nanoaura Serum</label><description>A one-use super-dose of nanobots which attune to the user, giving them an invisible, intangible cloud of nanobots. It will protect the user against everything, and greatly increase their stats.

Update pushed, thanks for letting me know

Alrighty, I'll sort it out

the original author (Lyn the Cookie) has made an update, and seems this patch mod has something with that update, causes some resources of the original mod (eg. nanobot) cannot find the correct file relation. that means, the big red cross. any patch for this issue is appreciated.

@coldzero. Lyn has updated the base mod and changed some of the defs. you need to change your's to match the new defs, as the nanobots were having a texture issue.

Pasted the fix in the base mod comments:

"Right, so the issue with the nanobots texture is being caused by the Nanotech overpowered patches mod. "Could not load Texture2D at 'Things/Item/Resource/NT_Nanobots' for def" is what is defined it the patch mod. Export the mod from workshop folder, unsubscribe form steam, paste it in the manual/on disk mod folder, edit the bots.xml in the on-disk patch DEF patch folder and change things/item/resource/NT_nanobots to LWNT_Nanobots and the new textures appear where they should. need to tell the patch owner to fix the defs to match LYN's new defs."

No idea what caused it but I've pushed a fix. If any errors occur, let me know

Ok, ignore what I said. I'll try find out what's going on and push a fix

@Sumatris Anytime :)

All I can suggest is unsub and resub. I can't see any reason why the mechlink would disappear.
Are there any error logs that come up?

I'll look into it

hmm for what ever reason the mech link is gone

Yeah, that did it. Steam Workshop strikes again ^^. And thanks again for your continued support :-).

Tried pushing the update again but Steam already recognises the changes. Try unsubbing and resubbing to see if it fixes it