There were two testing updates with own version number before: Compactness and Reclaim.
Uh. I hadn’t noticed. So when a big feature is added to an already-in-testing update, it bumps the version number. Neat.
Anyway, I’ll go back to bed waiting to see what 245 will bring us. ^^
Admittedly, this is more about some QoL changes, and I’m hoping for some big and juicy rework action.
Thanks y’all, so excited about Gleambow! 
No, the release number is always one higher than the Testing number. Well, except when we had 2 testing releases in a row without an actual update…
The odd numbers used to be release versions, the even numbers were testing versions, due to that one time with compactness and reclaim being 2 separately testing releases it changed around now…
1 Like
Uh. So, in truth, there’s been roughly half the number of updates released than the number suggests.
Kinda seems like an weird way of doing things, but ok. ^^
i can no longer shift click items in shopstands
hope its a bug and no feature of the smartstack behavior 
1 Like
Is that as an owner or as a buyer? Can you go into more detail so that I can look into it?
On ps4, trying to move a 900 smart stack of refined igneous rock into a shop stand only allows a stack of 200. The remaining rocks end up back in my inventory. Edit: pressing R2 is the issue, moving them manually works as intended.
1 Like
iam the owner and want to add more items to the stand for sale as example gleambow totems but i have the same with most uneven number of items they just “plop” back in my inventory
What format are you on?
platform? pc or what you mean ?
Yes, platform. Is it only shift-clicking that’s the issue, or does it also affect items being dragged across?
only moving in the stand dont work out has no problem
edit: and when nothing is in the stand or only full ss it only move 2/200 items in everything else “plops” back
It is, but as a dev I actually get it. It always feels weird to save and upload my testing version work with the new version’s number when it’s technically not finished yet.
Thanks @Alucard2150 and @econodog, I can see that in some situations it doesn’t occur, but your examples definitely occur (independent of platform) so it will be added to the bug database.
1 Like
Oh, sure, that I get.
When I do projects, I save with numbers like “1.0.0” and as long as it’s testing, each version will up the last digits (1.0.1, 1.0.2, etc). Once it’s a proper release, it’s the middle digit that gets a up and I reset the last one (1.1.0). If it’s a major big meaty change, I’ll up the first number.
Anyway, to each their own method.
World of Warcraft does it like “8.3.0.build-number” where 8 is the expansion number + 1 (because the vanilla version counts), followed by the expansion’s current major content patch, and then decent content updates to that content patch ups the last digit. But it doesn’t account for hotfixes and small QoL changes, that’s why they have a build number that counts every single update they internally do. So they’re currently at 8.3.0.34220.
Well that looks almost as annoying as the R2 bug on PS4 while using the reclaim menu.
2 Likes
I can’t/shouldn’t say what 245 will bring, but you will like it, I can almost guarantee that.
How’s that for a tease?
246 though is rumored to be a hunting update (FINALLY) and I am sooooooooo excited
1 Like
Yup! And is that one already solved? Haven’t checked yet…