[A19] khzmusik's modlets

[ate0ate]

I am using a Kinggen generated world using your initial provided settings as I generated the world before you tweaked the values for kinggen in your most recent update. To be clear, I did update everything but the world itself was generated using the older kinggen values. It is the correct poi that you have written above and I definitely have two of those POIs, at least. One is in the forest biome by my base and the other in the desert biome 4km away. In both instances the marker leads me to the corner of the trailer park camp where there is some barbed wire and a concrete pillar. The marker seems to lead to the pillar if i follow the "distance to" that is displayed. I initially thought it may have spawned the rally point in the ground a bit or even in the pillar itself but that is not the case. Thanks for getting back to me btw.

EDIT: You replied right when I did lol. Thanks for the fix and the info. I don't mind resetting the chunks. Gives me a great excuse to move the base anyways I'll grab the update from gitlab and get to it. Thanks again. Amazing work. It really makes a single player world feel so much more alive having some sort of dynamic life besides zeds roaming about. Thanks for balancing the creature pack too, those demon dogs were absolutely lethal.

 

[khzmusik]

I am using a Kinggen generated world using your initial provided settings as I generated the world before you tweaked the values for kinggen in your most recent update. To be clear, I did update everything but the world itself was generated using the older kinggen values. It is the correct poi that you have written above and I definitely have two of those POIs, at least. One is in the forest biome by my base and the other in the desert biome 4km away. In both instances the marker leads me to the corner of the trailer park camp where there is some barbed wire and a concrete pillar. The marker seems to lead to the pillar if i follow the "distance to" that is displayed. I initially thought it may have spawned the rally point in the ground a bit or even in the pillar itself but that is not the case. Thanks for getting back to me btw.

EDIT: You replied right when I did lol. Thanks for the fix and the info. I don't mind resetting the chunks. Gives me a great excuse to move the base anyways I'll grab the update from gitlab and get to it. Thanks again. Amazing work. It really makes a single player world feel so much more alive having some sort of dynamic life besides zeds roaming about. Thanks for balancing the creature pack too, those demon dogs were absolutely lethal.

Let me know how it goes, and again, sorry for the stupid mistake.

I'm glad that you're enjoying the NPC modlets. Please let me know if you spot anything else. Thanks!

 

[ate0ate]

Things are going well since the fix but I do have a quick question. There is probably little that can be done about it and I am unsure if it is an issue with NPCs themselves or the factions in general or if it is even an "issue" at all. When I place a robotic sledge it will strike at NPCs that roam by regardless of my faction status with them. I built my base unknowingly close to a Whiteriver camp, which has been interesting, and the NPCs tend to roam around the area frequently often being drawn to roaming zombies near my base. If they stray too close to the sledge they get hit and then aggro as if I hit them so I am forced to kill them as they attack unless the sledge does it first. Really puts a strain on faction relations to say the least I assume an auto turret would behave much the same but I have not placed one so I I can't be certain. I can certainly live with this but I thought I'd ask. Great job on the new zombies by the way.

 

[khzmusik]

Things are going well since the fix but I do have a quick question. There is probably little that can be done about it and I am unsure if it is an issue with NPCs themselves or the factions in general or if it is even an "issue" at all. When I place a robotic sledge it will strike at NPCs that roam by regardless of my faction status with them. I built my base unknowingly close to a Whiteriver camp, which has been interesting, and the NPCs tend to roam around the area frequently often being drawn to roaming zombies near my base. If they stray too close to the sledge they get hit and then aggro as if I hit them so I am forced to kill them as they attack unless the sledge does it first. Really puts a strain on faction relations to say the least I assume an auto turret would behave much the same but I have not placed one so I I can't be certain. I can certainly live with this but I thought I'd ask. Great job on the new zombies by the way.

That was a known issue with NPCs in general, but I thought it was fixed in SphereII Core.

If you look in the 0-SphereIICore modlet, go to the Configs directory, and open the blocks.xml file. There is a block with the name "ConfigFeatureBlock". In it, there is a property node named "AdvancedNPCFeatures", and within that, there is another property named "HumanTags". Its "value" attribute is a comma-separated list of entity tags.

In theory, any entity with these tags should use faction-based targeting. At the end of that list is a "deployed" tag, and that tag is on all the deployed junk robotics (junk sledge, junk turret, eventually the junk drone).

Can you double-check to see if your version of SphereII Core has that? If it does, then maybe something got screwed up in a later update.

You could also try adding the "turret" tag to the end of that list, to see if that helps. That tag isn't used by the junk drone, but it is used by the sledge and turret.

If that doesn't work, then something else must be going on.

That only affects the junk robotics though. It wouldn't affect the auto turret or shotgun turret (the ones that require power). I have not even tested with those yet.

EDIT: This assumes you're using the NPCPack versions of the NPCs, which require Core for the custom C# code. If you're using the CreaturePack humans, then there's not much that can be done.

 

[ate0ate]

Sorry for the delay in getting back to you. I am using the NPCpack version of NPCs along with your suite of mods. I checked to see if my version of Spherell Core contained both of the properties you mentioned and indeed it does. I did try adding the "turret" tag to the "HumanTags" property but still am having the issue of the sledge targeting NPCs. I suppose a conflict  is possible though I am not using any other modlets that touch NPCs or the turrets/robotics, at least not that I am aware of, but I will try stripping out everything other than just the NPC modlets and related dependencies to see if the issue remains as soon as I get the time. Thank you very much for looking into this.

 

[khzmusik]

Sorry for the delay in getting back to you. I am using the NPCpack version of NPCs along with your suite of mods. I checked to see if my version of Spherell Core contained both of the properties you mentioned and indeed it does. I did try adding the "turret" tag to the "HumanTags" property but still am having the issue of the sledge targeting NPCs. I suppose a conflict  is possible though I am not using any other modlets that touch NPCs or the turrets/robotics, at least not that I am aware of, but I will try stripping out everything other than just the NPC modlets and related dependencies to see if the issue remains as soon as I get the time. Thank you very much for looking into this.

I just tried this myself. If it ever worked before, it's sure not working now.

I was thinking maybe I was confusing it with another issue where the turrets would target hired NPCs. But that's not it. Hired NPCs won't take any damage from the turrets, but the turrets still fire at them (basically just wasting ammo).

The behavior is exactly the same even without including any of the tags that are on the turret entity classes. It doesn't seem to make any difference whatsoever.

I could swear that it used to work, but it was a long time ago. I'm thinking it used to work in A18 but something changed in either the vanilla game or Core (vanilla is more likely). Or I was just wrong that it ever worked, and added that tag for nothing.

I did look in the Core code, and it might be possible to get turrets to use faction targeting, but that would require code changes and those usually break game saves. Plus, with A20 coming up soon, this will all have to be reworked anyway.

So, unfortunately, I don't think this problem is going to be solved in A19.

I will bring it up in the discord channel for the creature packs. Maybe there's a solution that someone else knows about.

 

[ate0ate]

I'm no coder but I can only imagine how much of a headache integrating a faction recognition system into the turrets/traps would be. I completely understand that with alpha 20 coming up it makes no sense to break things now with code changes. I've been mitigating the damage by simply using the creative menu to give myself faction point books totaling the damage done to relations by the sledge. Not perfect, but it works well enough for me. Thank you for your time here regardless, its much appreciated.

 

[ate0ate]

Alrighty, I have one more possible issue for you that I just stumbled upon. Much like the missing waypoint I had before in the tier 3 Whiteriver camp, this time I have a missing waypoint in the tier 5 bandit camp. I went to the trader and chose a Tier 5 Murder for the Whisperers mission which was located at the Tier 5 bandit camp. Much like before as I approached the POI the waypoint to actually start the mission appears to be missing. Now the odd thing is that I had a mission at this POI before that worked just fine. I do not remember which faction the mission was for before but I do know that it was a steal mission, not a murder.

 

[khzmusik]

Alrighty, I have one more possible issue for you that I just stumbled upon. Much like the missing waypoint I had before in the tier 3 Whiteriver camp, this time I have a missing waypoint in the tier 5 bandit camp. I went to the trader and chose a Tier 5 Murder for the Whisperers mission which was located at the Tier 5 bandit camp. Much like before as I approached the POI the waypoint to actually start the mission appears to be missing. Now the odd thing is that I had a mission at this POI before that worked just fine. I do not remember which faction the mission was for before but I do know that it was a steal mission, not a murder.

I think I found the bug. It looks like a bug with the quest itself. The short version, I mistakenly made it a fetch quest rather than a murder quest.

EDIT: I may be mistaken. I found this bug with the Murder for Whiteriver quest, not the one for Whisperers. I'll keep digging. It might be an issue with the POI after all, though if you successfully did a "steal" quest, it's probably not (or at least it's not an issue with the rally marker).

I'm going to go through all of them and see if I can find any others. I will also double-check that the POIs all have quest markers, though I believe I checked them all with the last update.

If there are any changes needed to the POIs, then I will probably issue another update to them. I intended to add the XML tags such that they only spawn in certain biomes, but didn't add them.

I'll make sure any POI changes are in a different update. POI changes have a higher risk of messing up existing worlds. The quest changes should take effect the next time you start the game - though it may mess up quests in progress, those quests would have been messed up anyway, so no big deal.

 

[khzmusik]

I found the issue. Unfortunately, it was the worst case scenario. The T5 Bandits POI did not have a rally marker.

I'm not sure how that keeps happening. This time I made absolutely certain that all the human POIs have rally markers. I caught another T5 POI that also did not, the Military POI. Both are updated in the POIs modlet.

I also pushed a fix for the bug with the Tier 5 Whiteriver "murder" quest. That is in the Quests modlet.

Both modlets should now be working, and I bumped the version numbers of each. Since the quest bug is in a different modlet, you should be able to update that without any risk of breaking the world.

For the others, unfortunately, you will have to delete the chunks again, or live with the fact that those POIs can't be targeted for "murder" quests. I'm also not sure how they worked when they were targeted for "rob" quests, so you might have to steer clear of those as well.

I guess that's what happens when you rush to get things out while A19 is still around.  Hopefully I've learned my lesson for A20.

 

[Doomblade3890]

Hey I have an issue when trying to load a saved world. I had to change the boot folder for 7DTD on STEAM (to an SSD from an HDD) and now I'm getting these error messages when trying to load up the world. I'm running the NPC mods and their respective POI mods too.

 

[khzmusik]

Hey I have an issue when trying to load a saved world. I had to change the boot folder for 7DTD on STEAM (to an SSD from an HDD) and now I'm getting these error messages when trying to load up the world. I'm running the NPC mods and their respective POI mods too.

It looks like something major messed up when you moved the boot folder. I don't know what process you used to do this. If you did it through Steam then I'm guessing that's the root cause of the problems - it probably removed (or failed to move) a bunch of stuff that the modlets require to function.

The yellow warning messages mean that it can't find the required modlet dependencies. The red error means that something was trying to be added with the same name/ID as something that already exists.  (It could be anything, since that's a standard C# error.)

Since the console warnings refer to NPCPack, not CreaturePack, I'm assuming you're using the modlets that require custom C# code. If you're doing that, I strongly recommend you use the Mod Launcher for this. You should be able to set the directory where it copies the game files, so you should be able to use your SSD.

If you're not doing that, then you used some other method to compile the modlets, and I'm not sure what it was. I always use the Mod Launcher myself so I'm not sure how much I can help you.

If you haven't done so already, make a backup of your saved game world. Then, use the Mod Launcher to create an entirely new game copy, with whichever modlets you already were using. Then try loading up the save game again. If that doesn't work, you might be out of luck.

EDIT: Also, in situations like these, it's a good idea to provide the entire log output. It's usually in [game folder]/7DaysToDie_Data/output_log.txt, but there may also be a log with a specific date. You can upload it to something like pastebin and add a link, since I think the forum software doesn't allow text file attachments. (If you're using the Mod Launcher it can do this for you.)

 

[nickuk01]

Hi Khzmusik, I use your edit modlet for the creature pack and also your new zombie pack. Like both very much.

One thing noticed ingame which is probably related to the creature pack (not your edits) is that the zombies do not catch fire. When hit vanilla Z with lit torch for example, it will catch fire usually within 4 hits. For the zombies from creature pack they do not. 

I appreciate probably their issue to fix not yours but as you know what to do with edits and your own zombie models, would you be able to fix this in any future update?

 

[khzmusik]

Hi Khzmusik, I use your edit modlet for the creature pack and also your new zombie pack. Like both very much.

One thing noticed ingame which is probably related to the creature pack (not your edits) is that the zombies do not catch fire. When hit vanilla Z with lit torch for example, it will catch fire usually within 4 hits. For the zombies from creature pack they do not. 

I appreciate probably their issue to fix not yours but as you know what to do with edits and your own zombie models, would you be able to fix this in any future update?

That's a new one for me. I recently played a horde night with my own zombies, which were made following Xyth's instructions, and they at least looked like they were set on fire (by molotovs). I did not try with a torch however.

I am asking in the Discord forums. If there is a solution that involves XML, I will make it. If it needs Unity to fix, I can't, since I don't have access to the raw assets.

EDIT: Just to make sure I understand, and that you checked... These are zombies from the Creature Pack, correct? Not the zombies that are versions of the game's UMA archetypes, nor the new zombies I made in Unity.

 

[khzmusik]

So, I had a conversation about this in the CreaturePack Discord channel.

Short version: it's not something I can get to work with TFP flames, but you can use the 2-CharacterEffectsPack and it will add its own flames.

Long version:

Somewhere in an A19 patch update, flames on entities requires the model to be read/write. Unfortunately, in Unity, I can't find any way to set this except when first importing an FBX. In the "usual" zombie creation workflow, this is very early in the process - before you add ragdoll colliders, gore objects, tags, textures, and so forth.

This step is not in any of the tutorials, so I didn't even know I had to do it. So, in order to fix this, I would have to start all over with each zombie. That's a pretty time-consuming process, and to be frank, I'm not willing to do it at this point. I'll probably have to mostly start over anyway once A20 drops, so if it still needs to be done, I'll do it then.

But, this did affect nearly all of the existing entities in the creature packs, so Xyth made a workaround and put it into the Character Effects Pack. Basically he uses a new flame particle, and attaches that to any entity with a "cp" tag, which includes my zombies.

It's not as good as TFP though, IMHO. There's a flame centered around the hips, and some smoke that floats maybe a foot above the entities' heads. Also, the effects pack has some other stuff, like a revamped sound system and an infection/cure system for NPCs, which I don't use, and you might or might not want. So, I'll leave it to you to see if you want to use it.

That's about the best I can do.

 

[khzmusik]

But, this did affect nearly all of the existing entities in the creature packs, so Xyth made a workaround and put it into the Character Effects Pack. Basically he uses a new flame particle, and attaches that to any entity with a "cp" tag, which includes my zombies.

With the kind help of @bdubyah in the Discord channel, I found a way to do the same thing with the vanilla "burning barrel" particle. So, no new Unity assets are needed; it doesn't interfere with the flame effect on vanilla zombies; and it actually looks pretty decent IMHO.

I'm going to add the code to my own Unity zombies modlet, but it should also put flame effects on the CP entities as well. (EDIT- or maybe my zombie "adjustments modlet, it might make more sense there.)

I'll make the changes and push to the repo, but it will have to wait until tomorrow. It's late where I am and I need sleep.

 

[khzmusik]

This fix is now live. I put the "new" flame effect into the 0-CreaturePackZombies_khzmusik_Adjustments modlet. It should apply flames to any CreaturePack entities, and my own zombies created in Unity.

The new version is 1.0.1 and is on the master branch now. If you're using the Mod Launcher, the new version should show up soon.

 

[nickuk01]

OMG Khzmusik thank you so much for such fast work and trouble you went to. Amazing.

I have installed update. FYI in the mod launcher the modlet screen is out of sync as it says for both your new zombies modlet and adjustments to creature pack modlet that updates are available. However,  it says I have v1.0.1 installed for both and 1.0.0 is available which is, of course, the older version. May need to make SphereII aware.

 

[khzmusik]

OMG Khzmusik thank you so much for such fast work and trouble you went to. Amazing.

I have installed update. FYI in the mod launcher the modlet screen is out of sync as it says for both your new zombies modlet and adjustments to creature pack modlet that updates are available. However,  it says I have v1.0.1 installed for both and 1.0.0 is available which is, of course, the older version. May need to make SphereII aware.

I noticed that too, but didn't know if it was due to my dev environment. I'll let him know. There is a new version written in Unity, and he's probably spending all his time on that.

 

[ErrorNull]

below are two things i discovered while creating UMA zombies for my enZombies mod. it's listed in my "known issues" section of my enZombies mod page, and I believe this would apply to your UMA archetype zombies:

- UMA zombies don't catch fire from torch attacks. However, they do burn and suffer damage from molotov cocktails, flaming arrows/bolts. The flame effects just don't visually show on their bodies.

- UMA zombies don't get shocked when walking into electric fence traps. However, they occasionally get shocked while knocked down on the fence. Stun batons shock the zombies just fine though.