I noticed several optimizations in your map-making code, and I was wondering whether you would mind if I optimized it? Our goal for any code that's listed on this wiki is that it is as optimized as possible, because we don't want to give somebody bad code. I'm not saying your code is bad, I'm just saying it could use some optimization.
Date: 01 Oct 2007 23:11
Number of posts: 6
RSS: New posts
I think we should merge the information on this page into Making Maps.
It's always great to see new contributors!
This page could use some change.
First, I think the title is misleading. "Easy Map Making" has little to do with this page, it's about moving a one-pixel guy around the screen and collision detection.
Second, the body text of the page. There were clear spelling errors and other small things that could easily be improved.
Last, the code. There are several problems (and I'm sorry Tezza, but unlike burr, I do think the code is bad, in the sense that it didn't actually function). There were capitalization errors and missing parentheses. As burr said, the code is unoptimized…And worst of all, it doesn't even loop…?
I'm going to go ahead and change things, since Tezza never replied to burr's post…In 2007.
Does anyone know what the function of this program was supposed to be? For one thing, there isn't even any kind of loop. Second, it's…. well horribly inefficient. It turns the current position off, then changes the position variable and if that spot is already on it moves the variables back and turns the old position back on. It looks like it's just a collision detection routine than "map making". I'm thinking we should scrap this page and just add using pxl-Test( to the movement in maps page.
It recalls Pic1. Then it draws a dot. You control it with the arrow keys (well, you do since I edited it xD). All that it does is prevent you from sharing a pixel with something else (just run it with like a block in the middle of nowhere, you'll see).