API "Updated Recently" status for worlds seems to be broken
complete
Kilerbomb
Over the past couple months, I've noticed that the updating a world does not properly tell the API that it was updated. On multiple occasions, I have uploaded an update to my world but it didn't appear in the "Updated Recently" section, and the website had an out of date "Last Updated" date.
Strangely, updating twice within a short timeframe (a few hours) fixes this. I found this when I needed to apply a hotfix shortly after a major update. Both times I ended up doing this the world "updated" status was not changed until the second upload of the day.
It's worth noting that updating the description or title of a world via the website gives it the "Recently Updated" tag immediately, without needing to do so twice.
Log In
StormRel
complete
StormRel
needs more information
Hello! Thanks for reporting this. Is this issue still occurring?
Shiro K
StormRel For me it looks like the issue was solved. At least the past months, the "Last Updated" field was always right.
syncpulse
To add some more info, I noticed this happening on a private test world which has never been published to Labs or made public in any way. So if there's some kind of blacklisting going on, it must be per-user rather than per-world...
llealloo
Yep, same issue here. I thought for a moment that I'd uploaded to the wrong ID because "Last Updated" is unchanged
Shiro K
I remarked this too - but a little bit different: It looks, like the "Last updated" date is only updated, when you are also listed in the "Updated recently" list.
If you do daily updates for example (which is usual, when your world is still in develeopment), then you will be blocked from this list (for a duration of 5 days or so). This makes probably sense, because some creators would use it to stay permanently on that list. But this blocking mechanism seems also to suppress the "Last Update" date, which is bad, in my opinion. Users should be able to see, if the world was updated.
Kilerbomb
Shiro K: Yes there definitely seems to be some blacklisting system behind the scenes, where if you update your world too frequently you are no longer allowed the Updated Recently tag.
For me, it seems to have been permanent. I actually made a support ticket about it once and they manually gave me the Updated Recently tag, but seemingly didn't remove my world from the blacklist. I usually put out one big update every month or so, and maybe a few patches or hotfixes shortly after.
I think the "Updated" date should at least be updated every time. For my world if you just look at the last "updated date" it says Oct 2022, making it appear to have been stagnating for a while despite having relatively consistent monthly-ish updates.
Shiro K
Kilerbomb: It seems, that I ran in this permanently block for one of my worlds too.
During development, I had almost daily uploads without issues (world was set to "Private"). After realease, I had some short intervalled patches. The "Updated" entry started to stuck then. Today, I uploaded a new patch after 3 weeks of pause. The "Updated" entry is still Dec 27 and my world doesn't appear in the recently updated list today.
As creator, you spend a lot of time to build worlds and serve a good quality to players. But if some short interval quality updates blocks you totally from that "Recently Updated" list, you will have no attention anymore. And if users checks your world page, it looks as your world is dead, because of the wrong "Updated" entry.
It's absolutely ok, that creators cannot spam the "Recently Updated" list and there is some cooldown time. But block worlds forever and not refresh the "Updated" entry, will probably disencourage developers to continue on their projects. The bad thing also is - you will not be notified, if your world is currently blocked.
Tupper - VRChat Head of Community
Hi Tupper - can you please take an eye on this and clarify, what creators can do, to not run into this problem? What we have to do, to unblock our worlds from this (probably permanent) block.
Affected world for me: wrld_1f5f79e9-dcdf-4e54-9422-a868b96c872c
Shiro K
Addition: I made a own canny already some time ago, which relates to this. Also I found other similar posts.