User talk:Gregor

Duplicate image
Please don't re-upload an image (seemingly) just to change its description: the first Nov 25 upload didn't change the page summary anyway, so there was no need to re-upload with a new file comment (same as the original Nov 24 one). A page summary can always be adjusted afterwards. We're running low on disk space, and while the intermediate upload can be deleted to clean up the history, MediaWiki still keeps it on the file system so it's a waste of space. --Xymph (talk) 02:32, 25 November 2022 (CST)
 * Sorry, i was still figuring out how the upload worked and thought i had accidentally uploaded the wrong screenshot. I only saw afterwards that it just hadn't updated the picture yet. I was also surprised to see that there is no way to delete my uploads again in case of a mistake. That seems to be a rather weird technical limitation. I'll be more careful in the future. --Gregor (talk) 10:42, 25 November 2022 (CST)
 * Older revisions of images can be deleted with the appropriate account rights. Done now. But like any edit can be reverted, so can image revisions be restored by admins, that is why they stay (by default) on the file system. It's part of the wiki design, not an (inadvertent) limitation. --Xymph (talk) 10:54, 25 November 2022 (CST)

Magenta Spire
Please keep an eye on what others are doing: a ❌ was already uploaded, although it needed replacement anyway. So your upload can stay, but you may also want to check with Dusty Rhodes about not duplicating work on the Magenta Spire article itself. --Xymph (talk) 15:35, 10 December 2022 (CST)
 * Will do. Thanks for the heads-up! --Gregor (talk) 15:43, 10 December 2022 (CST)


 * Okay, last night was a bit hectic. You were upset that your "previous article [] was for some reason completely overwritten by content from duplicate article" and I'd like to apologize for that. The changes were briefly mentioned on Dusty's talk page, but possibly escaped your attention. Both articles originally needed clean up and further work, and Dynamo and I weren't sure how long Dusty's "little break" would take and what would then happen to both articles. So we chose to make a clear path, and your article -- while using the correct URL -- was far less complete than the other with its descriptions of custom content. So your article ❌ and Dusty's moved in its place as the better starting point for the remaining work. The moves are also logged in Recent Changes, so it is worthwhile to check that at least for any edits to your contributions and talk posts in discussions you're involved in, to quickly understand what is going on.
 * Anyway, I don't think it ever happened before in the nearly seven years that I've hanging out here, that two contributors created the same article at two distinct paths simultaneously, and as Quasar notes, we didn't handle that unusual situation very elegantly, or per normal wiki processes. Sorry again.
 * If you don't need that archived copy anymore, I can delete it. --Xymph (talk) 16:04, 11 December 2022 (CST)


 * All good. I did indeed not see the explanation on Dusty's Talk page at first, so i was a bit annoyed at seeing my article suddenly "disappear". Once i saw the explanation though, it all made sense, and as you said, it was a unique situation. You can delete my version of the article. I don't need it anymore. Thank you for the clarification. --Gregor (talk) 16:21, 11 December 2022 (CST)
 * Ok done. --Xymph (talk) 16:35, 11 December 2022 (CST)

The tumbling rocket of map32
Seeing as you couldn't reproduce the Eviternity map32 stuck rocket, I did some testing and found that the bug was caused by me using Boom compatibility, which as it turns out doesn't feature items tumbling off ledges like the more appropriate MBF compatibility does - thanks for taking a look!