submitted 1 year ago by Kalcifer@lemmy.world to c/canvas@toast.ooo

8 comments fedilink hide all child comments

Show the timer for all the succeeding stacked pixels. Currently, you can only see the timer for the first pixel. I propose that the timer should be shown for all of the pixels in the stack, and not only the first.
A neat feature that r/place had was that you could click on a pixel and see the username of the account that placed it. I propose the same feature.
Consider creating a permanent canvas. It could be neat to see how a large, permanent canvas evolves over a long period of time.

If any of these suggestions require the modification of underlying code, and are not simple config changes, then I will suggest them upstream -- please let me know.

you are viewing a single comment's thread
view the rest of the comments

[-] grant@toast.ooo 12 points 1 year ago

To answer some of these:

That sounds like a neat idea, try searching through Pxls's github issues to see if it's already suggested or not
That already exists actually! Shift + Click (or hold down on mobile) on a pixel to get who placed it :)
Pxls runs a permanent canvas already for year-round fun at pxls.space

[-] emi_x@lemmy.world 3 points 1 year ago

a decent number of pxls regulars use a userscript to track timer on pixels 2-6. im unsure if there was ever any consideration to add that as a native feature though as its inefficient to stack pixels anyways so the extra timer is only useful to tell you if the next pixel in the stack is sooner than a full cooldown.

[-] Kalcifer@lemmy.world -1 points 1 year ago

A couple more ideas popped into my head:

When placing a pixel on your own pixel, the time delay should be the same as placing over a virgin background. I don't see the point in punishing a user for drawing over their own art.
Defenders should have a more favorable time delay than attackers. For example, when placing a pixel over someone else's pixel that replaced your previous pixel (defending), the time delay should be short (e.g. the same as when placing over a virgin background), whereas when you place a pixel over someone else's pixel that wasn't preivously the location of one of your own (attacking), you should get the longer time delay (e.g. 1 minute).

[-] emi_x@lemmy.world 4 points 1 year ago

it might be unpopular opinion, but the 2x cooldown for replacing previous pixels shouldnt even exist. you get into odd situations where greifers have advantage when your piece uses virgin pixels. but you can also use this 'feature' to cause more problems as a griefer if you are smart about it. find virgin pixels in the art space and place on those so you keep low CD but the repair crew gets double CD.

and then you have the issue where if you want to update your art, you get double cooldown for the new piece cus you are going over pixels.

overall CD should be the same regardless of what or where you are placing, it levels the playing field for everyone. this is not really a great solution to getting the canvas filled out when it can be used maliciously and repairing gets nerfed for it

[-] Kalcifer@lemmy.world -1 points 1 year ago* (last edited 1 year ago)

Yeah, I'm starting to agree. I've found that it gets to a point where you essentially just cant keep up with the griefers if you are drawing over virgin pixels. I second the idea of making it the same cooldown for placing pixels for everybody. I don't think theres a way to structure it to always favor defenders. There will always be an edge case where the attackers will have the upperhand.

I'm also starting to think that being able to have multiple pixels queued can also put a defender at a disadvantage. When your actively placing pixels, you are always at 1 pixel with a cooldown, but someone could come along with 6 stored pixels, and just dump them consequtively in a spot giving them a permanent space advantage that you will never be able to recoup if the attackers keep at it.

[-] emi_x@lemmy.world 2 points 1 year ago

coming from experience, your second point isnt really a big deal. you will almost always be a few pixels behind on a persistent grief, the extra 5 to start doesnt really change much