Contributors cannot update workshop content.

[unreal mortar]

The Steam workshop allows adding other users as "contributors" to content. Contributors have most of the permissions of the owner of that content, including the ability to update it. VTOL VR does not acknowledge this. If a contributor attempts to update workshop content, it will appear successful, but it actually instead deletes the WorkshopItemInfo.xml file and uploads it as new content (under the contributors own account).

Updating multiplayer workshop campaign version to 20
Checking if we can update a workshop item.
- We could NOT update this item. (You're not the owner of this item. (ownerID == 76561197997557607))
Creating temp file for upload: 
Creating a WorkshopItemInfo xml for Sypwn's Other Missions
Beginning workshop upload task.
Uploading xml with new file ID
Creating a WorkshopItemInfo xml for Sypwn's Other Missions
 - There's already an item info file.  Deleting it. (C:\Users\Sypwn\AppData\Local\Temp\VTVRTEMP0\WorkshopItemInfo.xml)
Workshop upload complete. IsError=False, ErrorMessage=Upload success!

This makes it notably harder for multiple people to collaborate on complex campaigns and missions. It also means owners of highly popular content cannot "hand off" maintenance to other users if they are no longer interested in maintaining it themselves.

At one point in the past, I modified CheckUpdateValidRoutine to simply skip the ownership check, and the contributor was then able to update the content as expected.

[dense dagger]

I just experienced this bug too

[dense dagger]

is there any mod that modifies this to mkae stuff uploadable?

[unreal mortar]

@tiny patio I dug into this and I see why it's a problem. Facepunch.Steamworks provides no easy way to check if we are a contributor. (A simple 1-result query might be possible using SetCloudFileNameFilter on native Steamworks API, but this isn't exposed by the current stable version of Facepunch so I can't test it.)

I rewrote CheckUpdateValidRoutine to use available Facepunch API calls to check if the user is a contributor, posted here: https://discord.com/channels/319915885575798785/1359318360973770914

Though this implementation would exacerbate another existing issue which is that if the ownership check comes back negative or fails for any reason, the fallback is to attempt to upload it as a new item. It may fail on unstable internet (or Tuesday evening) resulting in unintentional duplicate content. It should instead prompt the user if they'd like to upload as a new item instead.