SEITENBUCH reupload issue

[gritty pivot]

Sorry if this broke something. Usually republishing a version fixes most problems. It does not seem to have wiped all the data about your mod, since you can still see your creation timestamp of months earlier

Created 13.04.2023
I will check with the workshop backend team on this and let you know about it.

Do you have any further information for us what "testing on publishing" meant? What were the things you did? What were you doing when something went wrong?

[celest yacht]

It seems you deleted all previous versioning from 16/11/2023 17:28:48 and before

@golden gazelle What exactly did you do?

step by step

[golden gazelle]

I was testing if you could reupload a mod without having the source files, by bundling some empty project and then replacing the content of ArmaReforgerWorkbench/publish/ with another pak etc. before uploading.
To do that, I took an obsolete old mod I still had in the publish folder, which was no longer on the Workshop. That mod depended on Seitenbuch, I which I did not consider relevant at the time.
I created an empty project (https://reforger.armaplatform.com/workshop/5EEEE9332833A41A-publishingtest), bundled it, replaced the bundle with the bundle of the obsolete mod, then uploaded it. Since this was just a test, I did not edit the GUID of "publishing test" to match the one of the obsolete mod.
The test was successful, everything worked just as expected, however I believe when I opened "publishing test" afterwards and clicked Remove from Workshop, it remained on the Workshop and apparently Seitenbuch (the dependency of the obsolete pak I uploaded) was deleted instead.
I still am not sure why exactly it did that, but one more noteworthy thing is that when opening the obsolete mod in the Workbench, it just opens the Seitenbuch dependency, no sight of the actual mod you selected. That's probably just because the mods second dependency is missing, but it could be related to the deletion issue as well, I'm not sure.

[gritty pivot]

Hello,
I have info from the workshop team and it is not possible to restore those old versions. Downloads and rating stats are lost with them. The subscriptions to your mod should not be affected as those are tied to the mod itself and not the asset versions. The team has requested some more info on potential reproduction steps.

1. If I understand correctly you made a new mod via workbench, then you somehow manually copied around files and then published the 5EEEE9332833A41A-publishingtest? And you wanted to remove that again after your successful test, but then your main mod was removed?
2. Are you positive you did not accidentally open your main mod and pressed delete there?
3. If you are sure you opened the publishing test mod to remove, what was its relation to the main mod? Because it does not seem to have any dependencies.
4. Also you said you replaced the bundle and then uploaded, however the workbench does not have bundle and publish as separate steps anymore, its just one button now. Did you press publish and then declined the confirmation popup to upload and then replace data or what? When you then upload again it would replace the bundle though? Or did you exchange the files while inside the promt and then just pressed yes after replacing them?
5. What data did you replace from where to what. Just because its listed as dependency would make your main mod disappear if you delete another mod.

We are trying to find the link to the main mod in this to see how the delete could have possibly happened

[golden gazelle]

I was initially very sure that I did not accidentally open Seitenbuch, but I tried to replicate the last few steps again and it did not have success.
While it's possible that I just missed something, I would for this reason assume it was just an oversight until you hear of another incident, it's been multiple days now and I don't remember much myself anymore, especially given a whole day passed between clicking Remove and seeing Seitenbuch deleted.

If this was actually just a mistake on my end, I apologize - the reason I brought it up is that I was fairly sure I did open the right project - but memory is unreliable and it's impossible for me to tell at this point.

[golden gazelle]

In any case, is there any chance the download count or popular ranking could be reverted manually?
The mod used to be in the top 10 of the terrain category, now it remains somewhere on Page 5 far beyond even unfinished test mods and has not risen since despite still getting significantly more downloads than any mods in front of it.
It seems the workshop now treats Seitenbuch like a mod that got 600 downloads over 7 months, not 600 downloads in 3 days.
I don't see how that would ever change, unless the download count is manually reverted. Or I somehow completely delete and reupload it with a new GUID, which would break all dependencies.

[gritty pivot]

Unfortunately we are unable to manually edit any of the stats for you. If the popularity pagination is important to you, you can wait and it will naturally move the pages forward over those test mods etc that will not get any further downloads - or as you mentioned remove your mod (again) and upload under a different GUID.

[golden gazelle]

Hm, I see. Just out of curiosity, is this for technical or for policy reasons?

[celest yacht]

Without proper history data, it is dangerous and unfair to do so. We might lock you with an offset of thousands of counts if we were to do those things

If you want to somehow regain all that (Force players and servers to sub and download again) then delete the actual mod and create a new listing

Otherwise you will still have this corrupted listing

Issue though are scenarios and dependencies

[golden gazelle]

Understood. 👍
I decided to reupload Seitenbuch as a new mod, but want to keep the old one up as an empty legacy version that depends on the new Seitenbuch for continuity reasons (so the new one is automatically included and dependencies don't break).
~~However, while publishing the "legacy update" works, it will always end with this:

DEFAULT : Project uploaded successfully
DEFAULT : Checking addon processing status...
DEFAULT (E): Addon processing failed
RESOURCES (E): Publishing failed
https://reforger.armaplatform.com/workshop/5B037111349D2447-Seitenbuch-LegacyShell
The mod details are updated, but the downloadable pak doesn't change (it should just be an empty mod but remains the same) and the dependency is not added. The old images also remain, even though I did not reupload these, only the thumbnail.
Any idea why this might be the case?~~