last thread: >>33092624 Water mural complete edition

File: 1500751154627.png (40KB, 1078x472px) Image search: [Google]

40KB, 1078x472px

>>33145296
There's also this located at http://pixelcanvas.io/@-1286,549 it's almost done.

>>33142790
I'll move Ralts in between Totoro and Quilava.

File: pixelcanvas.io (-1251,493) 2017-07-29T00-39-21Z.png (82KB, 1600x770px) Image search: [Google]

82KB, 1600x770px

Done, now I'll move Leafeon over by Celebi.

>>33146065
Leafeon is not bot protected?

File: pixelcanvas.io (-1129,498) 2017-07-29T01-26-44Z.png (136KB, 1600x770px) Image search: [Google]

136KB, 1600x770px

>>33146322
You mean the small sprite? I don't know. The area I'm moving it to is a little I can't do these parts of the outline.

>>33146341
I will help, but if his bot is on, we will need some help from the botfag

File: 250px-Vp_logo.png (53KB, 250x250px) Image search: [Google]

53KB, 250x250px

should we make our logo, maybe give us more luck for this summer cup.

>>33146866
Where would it go?

>>33146883
don't know, just an idea

File: Pory.png (5KB, 150x190px) Image search: [Google]

5KB, 150x190px

I made a Pory

File: option_two.png (113KB, 271x431px) Image search: [Google]

113KB, 271x431px

Grid of Pory

Here is my masterpiece. I speak only the truth.

File: pixelcanvas.io (-1790,593) 2017-07-25T09-48-24Z.png (10KB, 360x517px) Image search: [Google]

10KB, 360x517px

>>33147934
Forgot pic

>>33147941
>masterpiece
>messed up the x

File: 1500963616771.jpg (27KB, 371x578px) Image search: [Google]

27KB, 371x578px

>>33147955
I posted the wrong pic. I didn't want to shit up the thread with 3 posts posting the same thing.

>>33147968
>I didn't want to shit up the thread
Who cares? Barely anyone posts here shit it up all you want.

File: realgrid.png (75KB, 824x1280px) Image search: [Google]

75KB, 824x1280px

>>33147929
fucked the grid sorry

>>33147979
Nice, this is actually going to be the first shiny on the canvas isn't it? I wonder if the anon that kept asking to make one of the eeveelutions shiny is still around.

File: pixelcanvas.io (-1408,20) 2017-07-29T14-38-05Z.png (82KB, 1600x770px) Image search: [Google]

82KB, 1600x770px

>someone wasted their time doing this
Why didn't they just fill in the white parts? It makes no sense.

page 9

>>33150106
wtf when was that?

>>33152451
Earlier, I just checked and whoever did it is doing it again right now.

>>33152457
I would help fix it, but i am with proxy bug today...

>>33152466
There wasn't much, it's already fixed. Something tells me it's gonna happen again though.

>>33152466
literally refresh the page. Restart your browser

File: pixelcanvas.io (-1230,548) 2017-07-29T21_53_25Z.png (26KB, 1280x611px) Image search: [Google]

26KB, 1280x611px

>>33146800
Everything is done except for that corner.
Can anyone contact the botfag?

File: pixelcanvas.io (-1154,-165) 2017-07-29T21_32_02Z.png (39KB, 1288x708px) Image search: [Google]

39KB, 1288x708px

Hey, /vp/, did you really just steamroller over a faction? One that incorporated your border into their megaman? And then you just decided to go over flags? And now you don't like the color they added, and have incorporated that colored rainbow into their art, so you are whiting it out?

What is wrong with you?

>>33153859
It's been like that for a long time.

File: pixelcanvas.io (-935,-159) 2017-07-29T21_21_24Z.png (60KB, 1288x708px) Image search: [Google]

60KB, 1288x708px

>>33153885
Several days at least. This faction routed around your barrier, and added it to their background.

This looks like it's detonating so, let's stop that here, now.

Stop bitching and solve the problem. Reroute wall under megaman

>>33153859
Because according to a few, it would look like we were catering to flags, which would anger(?) the void.

>>33153916
>reroute wall under megaman
>expose them to the void
what did they mean by this?

This extension to the wall was built hastily in response to the rogue void's direct threat advancing over our north border. We made rash decisions with few people involved.

Now that there's time to think let's do it again, but properly.

Don't we have a NAP with the void? Aren't there better ways?

>>33153949
It's rogue.

The damage is already done. It's not worth worrying about it.

>>33153929
Isolate Megaman with a light, solid background. This would involve going over the text below, but it wouldn't be a retarded rainbow. Besides, it is only the rogue void, and they have a tendency to go elsewhere.

>>33153949
The void in question doesn't represent any of the main chunks. It's one guy trying to make trouble

>>33153983
>implying the void won't eventually spread up there
better protect stuff ahead of time

Also, removing color out of the border at this point is lowering the cooldown. You are replacing 1:20 green with 0:30 white.

>>33154048
Which will quickly enough go back to being high cooldown. The sooner it's changed, the better.

>>33154083
I ask that the area be left as it is until the creative strangers are swallowed up by the void.

bump
>tfw fucked up Porygon's outline

/bant/ is looking to build and further control the region south of the vulpix Lillie. We shouldn't build in that area, and they shouldn't mind our current presence.