Closed Juknum closed 1 year ago
black and red should switch imo. My reasoning is as follows:
green and red is unanimously understood as yes and no and black is more severe than red
red is for invalid, black is for something that passed out (somewhat died)
The bot should also losslessly compress every texture before pushing it to the repositories
EDIT: DO NOT do this, it breaks Bedrock and 1.12- packs
also might be nice that when a texture gets pushed the description in the discord message gets put as the description of the commit (so that if it's a bugfix/a major change people on the github know that more easily) now that each texture is pushed separately
oh yeah also I agree with nick about switching the invalid and failed colors, failed should be red since that's the color of the downvote button/symbol and black is more serious.
Paired with App#81:
When submitting a texture, the bot should look what projects the texture is featured in, display that in the embed, and, when pushing, it should push it to the appropriate repositories for all projects.
The project the texture is used in should also be displayed in embeds of commands such as /texture
.
Since we now have programmer art branches for versions ≥1.14, those should be used to compare submitted textures against when submitted to a programmer art project (currently only CF32PA)
Once a texture passes voting, the authors of this texture should also be given the Contributor role unless they have it already
Contributors can be listed without being mentioned (only writing their names should work)
This might be weird if multiple users in the server have similar names, I'd suggest using Discord IDs in addition to pings in case you don't want to bother the co-author. Would also be helpful if the user is no longer in the server like Lethal or Cituation.
Also a bug I've noticed, Managers and Council members cannot currently speak in voting channels like they can on the old submission system, which is very useful for short announcements, instapass/invalid reasonings, etc
More of a feature, but if a texture is being replaced when submitted, show the current one in the comparison image next to the new one, so people don't have to search it up to see if the new texture is an improvement or not.
Just noticed, the v3 submissions don't display the file paths in the submission embed. Please re-add that, it's very useful for me
Just noticed, the v3 submissions don't display the file paths in the submission embed. Please re-add that, it's very useful for me
It's useful, but it takes a lot of space, space which can increase in the future. The best compromise would be a link to the webapp where all paths are there
I'd remove the tags in favor of the filepaths tbh, tags are just a watered-down version of the filepaths anyways and are way less useful
agreed
In light of recent events, I think it's safe to say that v3 submissions have been abandoned and will likely not be continued. However, many of the proposed changes have found their way into the current submission system in some form since the creation of this comment, so I'm going to close it for now.
Submission System v3
"Frontend" part
.json
file on any changes"Backend" part
Features
.zip
with multiple textures.tga
(MCBE) files168
159