Hello everyone. Someone subscribed to one of my mods told me that my walls weren't working and upon investigating it was because THIS mod changes the wall definition. Looking at the comments it seems like that's a problem for some of you too, so here are two solutions, you only need to do one:

1) Make sure this mod is last in your load order so that other mods that rely on the "Wall" source code get that info before this mod overwrites it.

2) Go into the mod definition and change
<ThingDef ParentName="BuildingBase" Name="Wall">
to
<ThingDef ParentName="BuildingBase" Name="MatchingEmbrasures">
The Name field can be literally anything, this is just an example. Doing this will prevent the mod from overwriting the "Wall" code and will instead create a new *Thing* called "MatchingEmbrasures", this will also fix it and is what @cucumpear should do to fix their mod.

What is breaking your other mods is the following sequence of events in your mod order:

1) vanilla code is loaded in and compiled, giving you a wall structure
2) embrasures mod is loaded in and compiled giving you the embrasures, but it also overwrites (but does not compile since the texpath is different) the vanilla wall definition
3) some other mod (That depends on the Wall definition) is loaded in, copies the wall definition (which is now the Embrasures definition), and compiles.