Loading...

Top
PFQ Banner

This is PokéFarm Q, a free online Pokémon collectables game.

Already a user? New to PFQ?

Delete/Rename Site Skins

Forum Index > Core > Suggestions >

Pages: 12

ghostïfy's Avatarghostïfy
ghostïfy's Avatar
Alrighty, personally I find this quite difficult. As a user like me who creates skins all the time, I end up naming the skin wrong or I tend to insert a random name and it looks good. So basically, I would love to have a button where you could have skins being deleted or possibly rename the skin. It pains me to see a huge long list full of skins that I don't have use of anymore. Also another idea could possibly be to organize skins into folders like how the Image Uploader has them. The only thing I find negative is that if someone else if using your skin, it would be gone or hardly working. I looked in the rejected forums but couldn't find anything. I also heard that clearing your cache might delete/break your skins. Let me know what you think and if there's already a way to delete these skins! My poor eyesight can't see :')
Gilded's AvatarGilded
Gilded's Avatar
I do definitely support this overall; however, this suggestion has been made at least a couple times and both were rejected ^^' But, Niet's reasonings in those threads aren't exactly a hard "no" so maybe we can give it another shot?
┈┈┈┈┈┈┈┈┈┈┈ ┊ it/they/he ┊ ┊ pfp by box ┊ ┈┈┈┈┈┈┈┈┈┈┈
ghostïfy's Avatarghostïfy
ghostïfy's Avatar
Sorry, I guess I somehow skipped those while looking through the rejected forums ^^' Thank you for your opinion
doctormorbid's Avatardoctormorbid
doctormorbid's Avatar
i definitely support this! personally, when i was adjusting a skin i was creating, for whatever reason the new colours didnt apply when i edited, so i had to make a whole new skin MULTIPLE TIMES through copy pasting everything, so now im left with a few dead drafts. id like to get rid of them.. not sure if that's trouble on my end, but if not, it really needs fixing :c and! to compromise for any skins getting deleted that other users are using, how about a 'duplicate skin' button? that way people can ensure their skins wont be deleted if made by another user, and if you want to make a skin similar to one youve already made, it makes the process much easier
『 icon from mindhack 』
ghostïfy's Avatarghostïfy
ghostïfy's Avatar
Thank you for supporting this! I find that idea really cool, so then they can still use then skin they are/were using.
full support. its annoying when i name it wrongly, and i have too many site skins.
"Riddle me this, what makes the world go round? Why that's right, IT'S LOVE! Well, that and inertia along with the north and south poles, we don't talk about that tho."
ghostïfy's Avatarghostïfy
ghostïfy's Avatar
Bump
ghostïfy's Avatarghostïfy
ghostïfy's Avatar
bump
ghostïfy's Avatarghostïfy
ghostïfy's Avatar
bump
Aemilia's AvatarAemilia
Aemilia's Avatar
I'm gonna poke in here with a few ideas concerning this actually. I think being able to bare minimum rename skins is something that would be very handy. I have multiple skins that are literally duplicates of each other because I didn't realise at first that I had to clear cache in order to view edits to my custom CSS. This was a while ago now (several years at this point and in skins that I no longer use, though I could go back to them in the future, who knows). My ideas though concerning renaming skins specifically: - Firstly, able to rename it at all - A "tag" of some sort implemented, best location I would suggest is under Skin Metadata header as it would be the most relevant area. This "tag" would consist of a checkbox that you can toggle on/off to make it a public skin. By having it unselected (private) skin, this could make it so that only the user who created the skin can use the skin. Selecting the checkbox would then create a "public" skin. In the event a skin is selected as "public", this would mean any user, who has been given its path, can use the skin. If it's a public skin AND the original creator of the skin decides to rename the skin, the system could notify every user actively using the skin that it's pathway has changed and can allow the other users to update the pathway to still use the skin. Should the user make the skin "private" for any reason, the system could warn the user/let them know the skin is no longer allowed for public use. - Under this system, potentially could expand to allow for an area that you can see all public skins. This creates a problem though which I'll elaborate in my next point as a slightly different alternative. - Levels of publicity. Some skins are either commissioned or made for a friend (probably other things too, just two top reasons that I can think of). By implementing a third level, like "protected" this could allow for private skins for only certain "authorised" users to use the skin, whom the original creator can name and if it's a paid/gift type of skin, potentially allow for its "ownership" be transferred to them in the sense that they're the only user authorised to use it though maybe not necessarily edit it. Idk, haven't thought further on that yet. But by creating three levels this could present another idea. - Allow completely "public" skins to be shown in a list (after verifying legibility/credits/free use images first obviously) that allows users to create skins for the general population of the site to use. Similar to the official skins (which I feel we haven't had a new one in ages), it could be a small preview image of the skin (unlike how the current official ones you have to load each before you know how it appears) , and then select by radio buttons which skin a user would like to use. Idk how more to expand on this explanation rn at 0200 but just some random thoughts. I can pull together some images in the next few days as graphics can be very helpful to explain what I mean, just can't do so rn from my phone.
Buying: BSDs 20 ZC Prisms 70 ZC
Icons/Template by Aemilia

by Kaede

Pages: 12

Cannot post: Please log in to post

© PokéFarm 2009-2024 (Full details)Contact | Rules | Privacy | Reviews 4.6★Get shortlink for this page