- Joined
- Feb 22, 2008
- Messages
- 619
This one's pretty big because it's actually a large part of a map I've worked on a lot so far.
First of all I'll tell you what this bit is supposed to be.
Basically, it's a size-variable Prim's Algorithm (a procedural random maze generating algorithm) using only variables, a hashtable, and a multiboard.
I have a working version of the algorithm right now, but it uses units and unit groups instead of variables so it's a lot slower. I'm remaking the entire thing to get it to run faster.
If you'd like to see the map where this bit is 'extracted' from, here's the link to the thread about it. (If you go there to download the original map, use the second download link).
Because it's from a map and it's a work in progress, there may be some variables that don't do anything, redundant triggers, that kind of thing..
So far there are three real bugs, one of them new.
The first bug is that when it gives the "bug" error message, if you keep trying, it will eventually just have the line go up.
The second bug is that the path can go off of the edge of the map (there's a condition in there that should be stopping that from happening).
The third one is that the path will sometimes go in on itself. I really don't understand this one as I've put so many things in there that should be stopping it.
Now, let me let you know now that first of all, I only even discovered variables a couple of maps ago (about a year ago). I discovered hashtables during the creation of this map. Because of this, some of my techniques may be confusing, unordinary, or simply wrong. If they are, please ask me what I'm trying to accomplish. I don't know what the norms are and it would take a long time to explain everything one by one, so I'll do it as questions come up.
I say it's size-variable. This means that I want the size of the maze to be adjustable in-game. That's why some things, like the center of the maze, are in variables, and not just the raw number. Some other things aren't like this simply because it wasn't the goal while writing the particular trigger. While bug fixing, please keep the size-variable goal in mind.
Thank you for your help, or at least for clicking on this thread with the (possible) intention of helping. Message me or post here for any questions, I'll try to get back to you as soon as possible. Please don't link tutorials unless they solve a very specific problem of the bug! If you do link one, please also explain in detail how it will help. Thank you!
First of all I'll tell you what this bit is supposed to be.
Basically, it's a size-variable Prim's Algorithm (a procedural random maze generating algorithm) using only variables, a hashtable, and a multiboard.
I have a working version of the algorithm right now, but it uses units and unit groups instead of variables so it's a lot slower. I'm remaking the entire thing to get it to run faster.
If you'd like to see the map where this bit is 'extracted' from, here's the link to the thread about it. (If you go there to download the original map, use the second download link).
Because it's from a map and it's a work in progress, there may be some variables that don't do anything, redundant triggers, that kind of thing..
So far there are three real bugs, one of them new.
The first bug is that when it gives the "bug" error message, if you keep trying, it will eventually just have the line go up.
The second bug is that the path can go off of the edge of the map (there's a condition in there that should be stopping that from happening).
The third one is that the path will sometimes go in on itself. I really don't understand this one as I've put so many things in there that should be stopping it.
Now, let me let you know now that first of all, I only even discovered variables a couple of maps ago (about a year ago). I discovered hashtables during the creation of this map. Because of this, some of my techniques may be confusing, unordinary, or simply wrong. If they are, please ask me what I'm trying to accomplish. I don't know what the norms are and it would take a long time to explain everything one by one, so I'll do it as questions come up.
I say it's size-variable. This means that I want the size of the maze to be adjustable in-game. That's why some things, like the center of the maze, are in variables, and not just the raw number. Some other things aren't like this simply because it wasn't the goal while writing the particular trigger. While bug fixing, please keep the size-variable goal in mind.
Thank you for your help, or at least for clicking on this thread with the (possible) intention of helping. Message me or post here for any questions, I'll try to get back to you as soon as possible. Please don't link tutorials unless they solve a very specific problem of the bug! If you do link one, please also explain in detail how it will help. Thank you!
