Rabbits Love Cactus
Scavenger
Probably that new Demolition questView attachment 38198
Post automatically merged:
This is a first: I clicked on the rally point for the Knowbly Cabin POI, and it self-destructed!
Probably that new Demolition questView attachment 38198
Post automatically merged:
This is a first: I clicked on the rally point for the Knowbly Cabin POI, and it self-destructed!
Ah if you're including fixes like these, maybe this one too:
"questRewardLegendaryMeleeWeaponCraftingBundleDesc,items,item,,,A bundle of parts used to craft a legendary version of the title weapon or tool.\n\nIncudes some related magazines."
(There are 4 "incudes" in the Localization.txt)
I have only played once since the hotfix, and I am on PC, but mine worked fine. Are you sure you have flowers in them? You need at least a single stack of 10+ for them to work. It won't split across multiple stacks of flowers, so 3+3+4 won't produce.
Try this if you haven't already...My 2nd and 3rd Apiaries are no longer producing after the hotfix, I'm on ps5
If you could please post a proper bug report at https://community.thefunpimps.com/forums/bugs-7dtd/View attachment 38198
Post automatically merged:
This is a first: I clicked on the rally point for the Knowbly Cabin POI, and it self-destructed!
so we go from one error due to skins to new vertices error spamming?
I'm not sure if you're aware of this... but the trap Turrets are setting off the Demo zombies button causing them to explode.Unfortunate, but is being looked at rightI'm not sure if you're aware of this but.
I would happily include both the Game Name and the World Generation Seed... but the Seed is a random number that I didn't save. (Never do.) Does the game save it somewhere?If you could please post a proper bug report at https://community.thefunpimps.com/forums/bugs-7dtd/
It would be very much appreciated. I have tested cabin_10 Knowbly Cabin in playtest and Nevazgane and am not seeing any issues. If you could include the RWG Game Name and World Generation Seed we may have better luck reproducing the issue you encountered.
Ever since the hotfix, I can no longer connect to my server. I click spawn, and a few seconds later I'm DC'd
The logs for my game folder show this
2026-01-18T23:46:39 423.824 ERR NCSimple_Deserializer (ch=1) Message: Index was outside the bounds of the array.
2026-01-18T23:46:39 423.831 EXC Index was outside the bounds of the array.
at TileEntityCollector.read (PooledBinaryReader _br, TileEntity+StreamModeRead _eStreamMode) [0x001e7] in <3a063f32b5664748afde897a9f002d8e>:0
at Chunk.read (PooledBinaryReader _br, System.UInt32 _version, System.Boolean _bNetworkRead) [0x005ba] in <3a063f32b5664748afde897a9f002d8e>:0
at Chunk.read (PooledBinaryReader stream, System.UInt32 _version) [0x00000] in <3a063f32b5664748afde897a9f002d8e>:0
at NetPackageChunk.read (PooledBinaryReader _reader) [0x0009b] in <3a063f32b5664748afde897a9f002d8e>:0
at NetPackageManager.ParsePackage (PooledBinaryReader _reader, ClientInfo _sender) [0x00017] in <3a063f32b5664748afde897a9f002d8e>:0
at NetConnectionSimple.taskDeserialize (ThreadManager+ThreadInfo _threadInfo) [0x00289] in <3a063f32b5664748afde897a9f002d8e>:0
UnityEngine.StackTraceUtility:ExtractStringFromException(Object)
Log:Exception(Exception)
NetConnectionSimple:taskDeserialize(ThreadInfo)
ThreadManager:myThreadInvoke(Object)
System.Threading.ThreadHelper:ThreadStart_Context(Object)
System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean)
System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object, Boolean)
System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object)
System.Threading.ThreadHelper:ThreadStart(Object)
2026-01-18T23:46:39 423.835 INF Exited thread NCS_Reader_1
2026-01-18T23:46:40 424.423 INF Disconnect
One other thing I don't see noted elsewhere, the apiary smoker no longer works after this update. Apparently it only stops the bee swarms from spawning in response to the Open event, not when they spawn in response to the Close event.
For what ever reason, I had the server set to update on start, and on the latest experimental branch and it refused to update off of b23. Once I changed the branch to stable, it updated finally to b27 and fixed the problem.Are you 100% sure you've updated both your sever AND your local client to V2.5 B27?
You may have done just that, but I always have to double check.
In our testing of the original issue with TileEntityCollector, it would usually cause the chunk that contained the bad data to reset.
A chunk of a player's base would be gone that contained the Apiary, but it wouldn't kick anyone out of the game once the server was rebooted.
I would need to see your client and server output logs to know for sure what's going on here.
Please see our bug reporting forum on how to share your logs via PasteBin and then DM me a link.
Post automatically merged:
You may have to pick up the Apiary and place it back down again.
Seems to be working as intended on my end in V2.5 B27.
It has happened to me a couple of times too, but not at the Knowbly Cabin. Were you on Navezgane or a RWG map?View attachment 38198
Post automatically merged:
This is a first: I clicked on the rally point for the Knowbly Cabin POI, and it self-destructed!
RWG map. I have just finished posting a bug report. What platform were you using (PC, Mac, console...)It has happened to me a couple of times too, but not at the Knowbly Cabin. Were you on Navezgane or a RWG map?
That's an even better question.What platform were you using (PC, Mac, console...)
I'm on a Mac.That's an even better question.
I'm on PC and I have also made a bug report about it.
Are you on console?
I have a feeling that this is a RWG issue. I just started a Navezgane run but it's early so I haven't done too many quests, especially outside of the pine forest.
Obviously something is causing stability issues once quest activation resets the POI.
Sorry, that's what I meant. I hadn't tried the same flower in multiple slots since there isn't any reason to do that.It will NOT work with 5 golden, 4 cotton, and 1 chrysanthemum...at least not yet.