[A21.1 b6] Dew Collector surpasses the 3-bottle stack limit when waiting several days after it's filled.

I don't know if this note is important, but the water bottles were taken by using the R key, not by clicking.

Checking

On 7/31/2023 at 4:10 PM, 3ternalDamned said:

Checking

This issue might prove hard to find, as while the reproduce steps help, they are not 100% effective if you try to force the command to make it happen. You cannot reproduce it artificially by getting the time to pass by with a command, so that means the issue is in the code, specifically in the way the Dew Collector retrieves the state of "filling" that it is in.

 

Sometimes, when you have a few collectors, and you leave one without checking, and you are either in a long play session (doesn't matter which mode, but single player is rarer) the game either fails to stop water from producing in the background or clones the previous state (unlikely). Might also point at a memory issue (probably a combination of some of the above). I'm inclined to believe this can be completely fixed and/or ensured to be fixed by making the retrieving of the "state" of the Dew Collector more fail proof, so when you open it, its independent slots show the state they are in without that "background overflowing" if time is excessive.

 

As I said, rare issue, but worth looking at.

Edit: Correction : Either in a long play session or in a Memory-filled multiplayer session*

On 8/2/2023 at 10:12 AM, Blake_ said:

This issue might prove hard to find, as while the reproduce steps help, they are not 100% effective if you try to force the command to make it happen. You cannot reproduce it artificially by getting the time to pass by with a command, so that means the issue is in the code, specifically in the way the Dew Collector retrieves the state of "filling" that it is in.

 

Sometimes, when you have a few collectors, and you leave one without checking, and you are either in a long play session (doesn't matter which mode, but single player is rarer) the game either fails to stop water from producing in the background or clones the previous state (unlikely). Might also point at a memory issue (probably a combination of some of the above). I'm inclined to believe this can be completely fixed and/or ensured to be fixed by making the retrieving of the "state" of the Dew Collector more fail proof, so when you open it, its independent slots show the state they are in without that "background overflowing" if time is excessive.

 

As I said, rare issue, but worth looking at.

Edit: Correction : Either in a long play session or in a Memory-filled multiplayer session*

 

Before I look into this, you have game mode: all, you've seen this on a server and in an MP session too? 

12 hours ago, Jugginator said:

 

Before I look into this, you have game mode: all, you've seen this on a server and in an MP session too? 

It was seen in a MP session P2P. Given that I have not been able to reproduce the exact cause, you might want to bury this issue for now (as in "cannot reproduce"). It might very well be due to faulty memory hardware, because if and when I try to force the issue it doesn't happen. It's a rare issue anyways. Thank you for your time !

6 hours ago, Blake_ said:

It was seen in a MP session P2P. Given that I have not been able to reproduce the exact cause, you might want to bury this issue for now (as in "cannot reproduce"). It might very well be due to faulty memory hardware, because if and when I try to force the issue it doesn't happen. It's a rare issue anyways. Thank you for your time !

 

Ah nah I still want to give it a go. Initially, I ran the game for 7 days after putting collectors down and it hasn't reproduced, but I've seen weird oddities like this so it's plausible enough to warrant further checking.

Well, I've run a few different tests on servers, mp and sp and haven't reproduced this yet. I did run across a weird thing with forges, figured I'd look at them too while I was repeating 8 or so day long tests so that's nice. I believe there is a reproduction trigger for this, so not calling it a closed-case yet though. It's likely some magic combination of something to cause it, which certainly eludes me for the time being.

 

If anyone has any info that could help that would be great. Something like, for example:

 

• I took all the water out of the collectors
• I went 1.8km away to a city
• Spent a lot of time there and did other stuff away from the collectors
• X amount of days later I returned
• I took water out of the dew collector (Shift-click, click and drag, loot all) 
• Went back into the collector and there was more water (or it refilled in front of me)

Were no players near the collectors? Were they occasionally loaded in (i.e. one or more players pass by the chunk)

Edited October 27, 2023 by Jugginator (see edit history)

On 10/27/2023 at 7:00 PM, Jugginator said:

Well, I've run a few different tests on servers, mp and sp and haven't reproduced this yet. I did run across a weird thing with forges, figured I'd look at them too while I was repeating 8 or so day long tests so that's nice. I believe there is a reproduction trigger for this, so not calling it a closed-case yet though. It's likely some magic combination of something to cause it, which certainly eludes me for the time being.

 

If anyone has any info that could help that would be great. Something like, for example:

 

• I took all the water out of the collectors
• I went 1.8km away to a city
• Spent a lot of time there and did other stuff away from the collectors
• X amount of days later I returned
• I took water out of the dew collector (Shift-click, click and drag, loot all) 
• Went back into the collector and there was more water (or it refilled in front of me)

Were no players near the collectors? Were they occasionally loaded in (i.e. one or more players pass by the chunk)

They were near the collectors indeed. We were 5 dudes (and gals). 

 

You are doing it right though, and it should happen. If everything fails, then there might be some variables (test cases) that are missing. Can it be that our savegame was dragged from a previous 21.X patch and it might be causing issues for the p2p host and therefore it also causes those Dew Collector issues for the rest of the clients?

 

While that would invalidate the bug, it could be a great test to discard it once a for all if confirmed .

Even if it gets confirmed by this, the fact that it happens with this specific "fillable" container  is an interesting case of analysis for future references.

Only you can do that test though, as all of the people involved in this bug has long since wiped out their savegame, their PC, their house, their neightbors and their respective countries.

 

Forges do have some edge cases, I'm glad you spotted them.

 

Have a great day!