[A14] Community Core Library v0.14.3.1

[Slowtapus]

I've noticed an odd bug and am not 100% sure what causes it. However at times the CCL Vanilla hoppers get replaced by the vanilla ones.

It seems like it might be any time you load a game with different mods than you have previously. As in if you start a game with CCL Vanilla and then later add a mod that doesn't do anything to hoppers. I'm not 100% that this is the cause but it certainly seems like it.

I should clarify. It seems like all the CCL vanilla features vanish. Since the power draw part vanishes as well.

[1000101]

@Slowtapus

Would need to see your modsConfig.xml and output_log.txt before any determination could be made as to the problem.

Replacing CCLs hoppers with vanilla would be a good magic trick as they are completely different objects with completely different properties.  The only similarity is the human readable strings (ie, "hopper") and that they are storage buildings.


@pestilenz

First part of my response is the same as above regarding modsConfig.xml and output_log.txt.

Second part is dependant on what I find in said files.


@everyone

Please do due diligence when reporting potential issues as to not clutter up the forum.  Due diligence involves:

a) Confirm there actually is a bug which includes:

• Making sure mods are installed correctly as per the mods instructions
• Make a new world and new colony and test the mod combination you are using (don't just load up your existing game an expect everything to work)
• Adjust your mod load order to resolve "simple" conflicts, repeating the above step as necessary

b) After you have confirmed that there is a bug and not just a mod conflict, attach your modsConfig.xml and output_log.txt to the report you file in our issues tracker, NOT HERE, as we have repeatedly asked.

Sorry if a sound like a jerk, but we want to separate real bugs from junk bugs and keep the forum some what clear of bug reports anyway.  We have an issue tracker for bugs and feature requests, it is important to use it so they can be easily tracked without getting lost.  Further, they can be directly linked to the commit which fixes/implements them and will show up on our commit log when we do releases.

[1000101]

READ THIS BEFORE REPORTING ERRORS

CCL has been updated for Alpha 13, but any mod which has an assembly (DLL) needs to be recompiled against the new alpha version and CCL version.

There are many issues with DLLs and alpha updates including but not limited to:

• Changes in the API the assembly uses
• Assembly version signing

Do not use any mod with an assembly (DLL) from previous alpha versions until the mod has been updated for the new alpha.  It will not work and will only lead to bogus reports.  I've already had to deal with this, I don't wish to deal with more.

If you see an error like this in your output_log.txt (Player.log on MacOS), then it because you are trying to use a mod from an earlier alpha which is not compatible.

Code Select Expand

=> System.TypeLoadException: Could not load type 'CommunityCoreLibrary.SpecialInjector' from assembly 'Community Core Library, Version=0.12.2.0, Culture=neutral, PublicKeyToken=null'.
Although the above error is specific to CCL, if you see a simalarily formatted message, that's the issue - It's not compatible with the current alpha.

[hwfanatic]

What exactly is the purpose of hydroponics basin power cycling?

[jacob814]

I am failing to see the error in my mod using the advance research from this mod. In the past I haven't had an issue but alpha 13 update CCL won't work correctly, or it isn't showing an error when it should?

My colored ceiling lights should only be unlocked after the vanilla colored research and my mod's research. I haven't changed any of my code, does advance research for CCL work differently? I wouldn't have come here without spending a few hours trying to figure it out myself.

If this is the DDL error you have 2 posts above then I am blind. With my mod loaded with CCL, I get no error you're describing. There should be an error...

[Simulacrum0]

Can you make it so smelted products is usable by Automated Factory, a automated smelter and recycler would so helpful.

[1000101]

@jacob814

There shouldn't be an issue, based on what I see in your mod.  I'll give it a try though.  That being said, as of A13 ThingDefs can have multiple researchPrerequisites which makes CCL redundant for your usage.

@Simulacrum0

All you need to do is create a recipe which mimics the smelting process.  That is basically what the automated stonecutter example does - instead of a single recipe which has a variable output, there are recipes for each stone type.  While this isn't the best solution for weapons, for slag chunks it will work fine.  Adding variable output recipes is on the to do list but isn't at the top of. 

[Simulacrum0]

@1000101
this is the recipe i have for armor
<RecipeDef>
    <defName>AutomatedArmourRecycling</defName>
    <label>Recycle Armour.</label>
    <description>Dismantle armor for materiel.</description>
    <jobString>Recycle Armour.</jobString>
    <workAmount>1800</workAmount>
    <ingredients>
      <li>
        <filter>
          <categories>
            <li>Armour</li>
          </categories>
        </filter>
        <count>1</count>
      </li>
    </ingredients>
    <specialProducts>
      <li>Smelted</li>
    </specialProducts>
  </RecipeDef>
in game it give a errors saying it has no products.
and you cant mimic smelting with a products <____>2</____> recipe since the game does not count stuff items as a thingdeff, a cloth parka is just a parka and even if it did i would then have to make 1 recipe for every item for every stuff it can be made from that's 40 for parkas alone.

[1000101]

@Simulacrum0

Yes, as I outlined above, for smelting weapons/armour/apparel the system isn't ideal as it would require a recipe for each.  Also, currently Building_AutomatedFactory only allows a small subset of recipe tags, <specialProducts> is not in that list.  Please refer to the documentation as to what is allowed and what the restrictions are.  Specifically:

The only recipe tags which are relevant are as follows:
        defName
        label
        description**
        jobString***
        allowMixingIngredients
        ingredients
        fixedIngredientFilter
        defaultIngredientFilter
        products
        workAmount

All other tags will be ignored and if certain tags are missing, an error will be thrown.

Adding variable output recipes is on the to do list but isn't at the top of.

[jacob814]

Hm... Did not see that in the change notes.. will take a look, thankyou.

[hwfanatic]

Quick search found nothing. I'll continue tommorrow, but for now I'll leave this here and maybe somebody will recognize it.

CCL tweaks stopped working. Something about DetourInjector. Persists without all the other mods as well.

Code Select Expand

Community Core Library :: Injection Controller :: Initialization :: Errors during injection
Error injecting 'CommunityCoreLibrary.DetourInjector' :: System.NullReferenceException: Object reference not set to an instance of an object

Log: http://pastebin.com/raw/jeqbZ6mj
Save: http://www66.zippyshare.com/v/5oimmjrJ/file.html

[Rock5]

I was trying out a mod which overwrote the default Wall def. All I did was add an extra DamageMultiplier.

Without CCL in the mod list, this works as usual. But with CCL, walls become like art - they can be uninstalled and reinstalled.

Something like this happened to me. I'm assuming you didn't include the base def. Try including it. That fixed it for me.

[hwfanatic]

I'm really sorry for reporting on the forums. I was tired and didn't read the instructions. :-(

It turns out it is an incompatible mod called "M&Co. MiningHelmet". Once removed and the game client restarted, it works fine.

[LustrousWolf]

I keep getting this repeating error. Any fixes?

https://gyazo.com/0fc45ea4640737d6b1b7c94e4a5c381b

[1000101]

@LustrousWolf

That tells me nothing.  As REPEATEDLY said, no screen shots.  They are useless.  Please send or caption the relevant section of your output_log.txt/Player.log.


@Everybody

Before jumping into any given mod thread, look through your log file for the first mod which has an error, be in a missing assembly class, xml error - anything.  Always work down from the top, not the bottom up.  The first mod which has an error can cascade down into other mods as the game state will already be corrupt when those mods load.

Eg, mod 'Snibbits Plus' references "BaseBuilding" but never defines it.  The mod author of 'Snibbits Plus' is incorrectly referencing an abstract definition which they don't have access to.  This may cause errors in mods loaded after it in the load order as the game state is now corrupt.

The core game should actually be more stringent when validating the xml, but it only throws some silent warnings when it should be throwing fatal errors.  CCL is especially sensitive to bad xml and errors in mods.

Always scan your log file starting at the top, not the bottom.  Resolve issues starting at the top and only report an issue to the next mod author in the list AFTER the issues with the current mod is resolved.