Report, edit, etc...Posted by StarKraft on 2006-07-30 at 00:22:46
Actually I have no idea where to put this and I hope it's right under map making assistance.
Anyways, my question is easy. I was searching for some kind of a list that shows you what all can go wrong with maps (mainly triggering) and battle.net (mainly lag wise).
Is there such a list anywhere?
Anyways, my question is easy. I was searching for some kind of a list that shows you what all can go wrong with maps (mainly triggering) and battle.net (mainly lag wise).
Is there such a list anywhere?
Report, edit, etc...Posted by Shocko on 2006-07-30 at 00:42:32
1) did u check tutorials??
2) i know for a fact creating units or moving units causes lag, clicking a building like a pylon that is stacked a lot causes IMMENSE lag, too many units creates lag, moving lots of units creates lag, playing with sumbody that has a fisherprice modem creates lag. hope i could help
2) i know for a fact creating units or moving units causes lag, clicking a building like a pylon that is stacked a lot causes IMMENSE lag, too many units creates lag, moving lots of units creates lag, playing with sumbody that has a fisherprice modem creates lag. hope i could help
Report, edit, etc...Posted by Snipe on 2006-07-30 at 01:42:39
QUOTE(StarKraft @ Jul 29 2006, 10:22 PM)
Actually I have no idea where to put this and I hope it's right under map making assistance.
Anyways, my question is easy. I was searching for some kind of a list that shows you what all can go wrong with maps (mainly triggering) and battle.net (mainly lag wise).
Is there such a list anywhere?
[right][snapback]534584[/snapback][/right]
Anyways, my question is easy. I was searching for some kind of a list that shows you what all can go wrong with maps (mainly triggering) and battle.net (mainly lag wise).
Is there such a list anywhere?
[right][snapback]534584[/snapback][/right]
No there isn't. You learn from your experiences of map making. Map making assistance is mainly for helping with triggers. If somthing goes wrong with a trigger make sure all the variables add up. If it's for a program ask in the topics.
Report, edit, etc...Posted by StarKraft on 2006-07-30 at 01:50:16
I'm sorry that's not what I meant.
I meant like could it be that some triggers won't work on battle.net or stop working whilst play or other things that can go wrong especially when it comes to lag maybe.
Just to prevent me and others who read it of even making these mistakes if there are any.
All because I want to try to do a map for next month's contest and I wan't it to be working at least
I meant like could it be that some triggers won't work on battle.net or stop working whilst play or other things that can go wrong especially when it comes to lag maybe.
Just to prevent me and others who read it of even making these mistakes if there are any.
All because I want to try to do a map for next month's contest and I wan't it to be working at least
Report, edit, etc...Posted by Zeratul_101 on 2006-07-30 at 01:55:48
pause and set next scenario(or w/e the action is) don't work in multiplayer.
ADDITION:
ps, you make it work by testing/debugging it. playing the map dozens of times if need be.
ADDITION:
ps, you make it work by testing/debugging it. playing the map dozens of times if need be.
Report, edit, etc...Posted by Desperado on 2006-07-30 at 02:11:03
QUOTE
some kind of a list that shows you what all can go wrong with maps
Well, I tried compiling a known list once, here are some excerpts from it:
#1: You forgot to save.
#2: You forgot to compile your triggers.
#3: You are hosting the wrong map.
...
#866: You used Command instead of Bring.
#867: You are running the trigger for the wrong player
#868: You are running the trigger for too many players.
#869: You have disabled conditions.
#870: You have disabled actions
...
#5449: You have forgotten about old triggers which conflict with the new ones.
#5450: You are using units that crash StarCraft.
#5451: You are using sprites that crash StarCraft.
...
#307562: Your map does not exist.
#307563: You do not exist.
#307564: The people you are playing with do not exist.
...
#2900383: You have bad RAM.
#2900384: Your StarCraft disc is bad.
#2900385: You are referecing sounds that don't exist.
#2900386: You are a Mac user, and God hates you.
...
Once I got up to ten million things that could go wrong, I realized the search for everything that could go wrong was hopeless, stupid, and ignorant of me.
Report, edit, etc...Posted by StarKraft on 2006-07-30 at 08:12:53
QUOTE(Desperado @ Jul 30 2006, 07:10 AM)
Well, I tried compiling a known list once, here are some excerpts from it:
#1: You forgot to save.
#2: You forgot to compile your triggers.
#3: You are hosting the wrong map.
...
#866: You used Command instead of Bring.
#867: You are running the trigger for the wrong player
#868: You are running the trigger for too many players.
#869: You have disabled conditions.
#870: You have disabled actions
...
#5449: You have forgotten about old triggers which conflict with the new ones.
#5450: You are using units that crash StarCraft.
#5451: You are using sprites that crash StarCraft.
...
#307562: Your map does not exist.
#307563: You do not exist.
#307564: The people you are playing with do not exist.
...
#2900383: You have bad RAM.
#2900384: Your StarCraft disc is bad.
#2900385: You are referecing sounds that don't exist.
#2900386: You are a Mac user, and God hates you.
...
Once I got up to ten million things that could go wrong, I realized the search for everything that could go wrong was hopeless, stupid, and ignorant of me.
[right][snapback]534636[/snapback][/right]
#1: You forgot to save.
#2: You forgot to compile your triggers.
#3: You are hosting the wrong map.
...
#866: You used Command instead of Bring.
#867: You are running the trigger for the wrong player
#868: You are running the trigger for too many players.
#869: You have disabled conditions.
#870: You have disabled actions
...
#5449: You have forgotten about old triggers which conflict with the new ones.
#5450: You are using units that crash StarCraft.
#5451: You are using sprites that crash StarCraft.
...
#307562: Your map does not exist.
#307563: You do not exist.
#307564: The people you are playing with do not exist.
...
#2900383: You have bad RAM.
#2900384: Your StarCraft disc is bad.
#2900385: You are referecing sounds that don't exist.
#2900386: You are a Mac user, and God hates you.
...
Once I got up to ten million things that could go wrong, I realized the search for everything that could go wrong was hopeless, stupid, and ignorant of me.
[right][snapback]534636[/snapback][/right]
#307562: Your map does not exist.
#307563: You do not exist.
#307564: The people you are playing with do not exist.
LMAO!#2900383: You have bad RAM.
Yup had that a year ago, then I removed 1 pair of ram and it worked again.
#2900386: You are a Mac user, and God hates you.
Thanks for the rest of the list and 1 more question. What is debugging for because the stuff I actually learned from tutorials and tested on test maps worked and I never compiled it
And I also didn't compile the map I sent to vic
Report, edit, etc...Posted by fritfrat(U) on 2006-07-30 at 14:47:20
Seeing as it was so comical, maybe we could make a topic in Miscellaneous where each new person adds on a new "thing that can go wrong."
Debugging basically means "taking the bugs out of the map and making it work." As you make more maps you get prone to how you make the mistakes you make, preventing it from happening next time. Much more efficient than reading a list of 10 million possible errors.
Debugging basically means "taking the bugs out of the map and making it work." As you make more maps you get prone to how you make the mistakes you make, preventing it from happening next time. Much more efficient than reading a list of 10 million possible errors.
Report, edit, etc...Posted by Zeratul_101 on 2006-07-30 at 15:00:19
QUOTE(StarKraft @ Jul 30 2006, 06:12 AM)
What is debugging for because the stuff I actually learned from tutorials and tested on test maps worked
[right][snapback]534711[/snapback][/right]
[right][snapback]534711[/snapback][/right]
debugging(AKA testing) is a process in which testers run the map several times in order to find logic errors created by the mapmaker. It is up to the mapmaker to make the necessary changes to eleminate or reduce the effects of said errors.
all i have to say, if you've never tested/debugged your map, you have a LONG way to go to become a good mapmaker.
you say the test maps you've created worked fine. thats because they're test maps. incredibly simple and only have one purpose. they lack the other triggers and trigger systems that would be in an actual gaming map. These said other triggers are what would cause bugs.
Report, edit, etc...Posted by SunMoon_Emperor on 2006-07-30 at 16:49:56
QUOTE(Desperado @ Jul 30 2006, 01:10 AM)
Well, I tried compiling a known list once, here are some excerpts from it:
#1: You forgot to save.
#2: You forgot to compile your triggers.
#3: You are hosting the wrong map.
...
#866: You used Command instead of Bring.
#867: You are running the trigger for the wrong player
#868: You are running the trigger for too many players.
#869: You have disabled conditions.
#870: You have disabled actions
...
#5449: You have forgotten about old triggers which conflict with the new ones.
#5450: You are using units that crash StarCraft.
#5451: You are using sprites that crash StarCraft.
...
#307562: Your map does not exist.
#307563: You do not exist.
#307564: The people you are playing with do not exist.
...
#2900383: You have bad RAM.
#2900384: Your StarCraft disc is bad.
#2900385: You are referecing sounds that don't exist.
#2900386: You are a Mac user, and God hates you.
...
Once I got up to ten million things that could go wrong, I realized the search for everything that could go wrong was hopeless, stupid, and ignorant of me.
[right][snapback]534636[/snapback][/right]
#1: You forgot to save.
#2: You forgot to compile your triggers.
#3: You are hosting the wrong map.
...
#866: You used Command instead of Bring.
#867: You are running the trigger for the wrong player
#868: You are running the trigger for too many players.
#869: You have disabled conditions.
#870: You have disabled actions
...
#5449: You have forgotten about old triggers which conflict with the new ones.
#5450: You are using units that crash StarCraft.
#5451: You are using sprites that crash StarCraft.
...
#307562: Your map does not exist.
#307563: You do not exist.
#307564: The people you are playing with do not exist.
...
#2900383: You have bad RAM.
#2900384: Your StarCraft disc is bad.
#2900385: You are referecing sounds that don't exist.
#2900386: You are a Mac user, and God hates you.
...
Once I got up to ten million things that could go wrong, I realized the search for everything that could go wrong was hopeless, stupid, and ignorant of me.
[right][snapback]534636[/snapback][/right]
LMAO!!!!