If anyone can figure out why this map is dropping people randomly, much would be appreciated.

Sometimes it takes 5 seconds, other times it doesn't happen at all.

I've tested with private games, so I know it isn't drop hacks.

Attachments:

Post has been edited 5 time(s), last time on Mar 29 2011, 5:33 am by Ryu.

Just to be clear: the players drop from the game, not crash, correct?

Dropping is caused by losing synchronization. The most common cause of this is EUDs (but it appears those aren't being used for this map).

Maybe disabling the Barracks is causing the problem? Set Doodad State is known for sometimes dropping/crashing, and on some units, it will work some games, and crash a couple players other games.

If you want to try self-diagnosing the issue, you first need to find a way to effectively reproduce the problem. Then begin removing an element from the game, such as sprites, units, or triggers. Once you remove something that causes the problem to stop, you know that section is what is causing the problem.

TL;DR If they're dropping, it's probably triggers. If you can't reproduce it reliably, debugging will be difficult.

P.S.: Is this your map?

Correct, players are dropping, as well as myself.

I'll remove the disable barracks see if that fixes it.

Yea thats general the problem.. It's so random I don't even know where to begin. Although it could be the spawning, since before that it was working.

and yea, it's co-production between Zergling[SK] and myself.


EDIT:

Ok so, the disable was removed and it's still dropping =/

Post has been edited 1 time(s), last time on Mar 27 2011, 2:00 am by Ryu.

Mind testing it without sprites?

edit:
Take out stuff until the dropping stops. If that doesn't help, delete all triggers. If that doesn't help, delete all units.

Are you using extended players or funky colors or something out of the ordinary? Because these are buffer overflows and the main effect you use it for is actually just a side-effect and internally a lot more changes. This can lead to crashs, but doesn't always.

@ Ahil, Deleting all sprites didn't work, I'll try deleting units and deleting triggers slowly.

@ Raider, There is 1 extended player, but it's only at the very start of the map. I don't think that would cause random crash's 30 mins or 1 hour into the game. (I'm going to change it anyway tho just to make sure).
And theres no funky colours

Is anyone who is being dropped playing on a Mac?

Not that I know of, Zergling and me have windows, and still dropping.

Ok, the removal of extra players (player 10 and such) does not work, still dropped.

Now to delete units/triggers and go from there.....

Post has been edited 1 time(s), last time on Mar 27 2011, 4:26 am by Ryu.

this bug is so annoying...

I've never figured out what causes the desync, but it's likely a trigger.

Ugh, seems like the more we delete stuff the longer we can play... but it still drops lol...

If anyone can solve this problem, it would be amazing and you'll get put in the map as special thanks.

EDIT:

Ok we'll We've tried just about everything, even adding a pop limit so CCMU doesn't happen... Still nothing.

The weird part is some games don't drop at all, and some do. So I'm just going to say GG, Starcraft wins.

Post has been edited 1 time(s), last time on Mar 28 2011, 5:53 am by Ryu.

I have the same problem with a new kind of evolves I made about 1 week ago. People randomly get dropped.

Strange fact though: it only drop a whole team. Not 1 player, not 3 players and not 2 players on different team... it drop Team1 or Team2.

I do use alot of stuff though... including X2 speed, sprites and funky color.

Either way, I pretty much noticed it drop player more often, when all player use the mass command in middle. So my question is: Can it be related ? ( Thinking about, to much trigger at once ordering alot of units at once.

Maybe it gonna ring a bell to someone

Maybe something you used is just faulty, who knows. I hate when this kind of thing happens.

I will usually just save all my triggers in xtra edit and start over.

If players drop (instantly leave) that means their version of starcraft has a part of the memory different from the players still in the game (desynch). This is usually the result of using buffer overflowing conditions in triggers (EUDs or EPDs).

If players are counted down this is due to their starcraft client crashing or when they lose connection to battle.net.
Players crashing is usually due to using extended players (P13+). This is also a buffer overflow because technically these players do not exist and force a certain variable (color, speed, etc.) to be read from a random point in memory, resulting in odd behavior, which has useful side effects, but can also lead to crashes.

I can only suggest removing said causes from the map and check if the players are still dropping/crashing. I had a cool effect where resources would be invisible on the minimap, but I had to drop it because it caused occasional crashes.

It's usually terrain. Screen position over specific parts of terrain has caused people playing in one of my maps created with SCMDraft to drop. I fixed it by using the isom terrain brush around the screen location where people looked when they dropped.

So, this sounds like what is happening with you. Were you even editting terrain via cut/paste/tileset index? If so, keep track of where people are looking and when they drop.

This seems like the most plausible culprit.
Remember those "Don't look at the dot" games where once you look at the turret or that part of the map, you crashed/get dropped?

It is possible that you have a unit/sprite that's causing this..
what's worse is that this unit/sprite can be created some time after playing your map...

Try testing with full vision of your entire map, and once someone drops, try to find out where he was looking at

A year later....

So apparently someone removed all of the machine shops that were used as walls and it fixed it.

I'm not sure why this would cause an issue, but I'll go with it. Going to test it out a bit and see if it continues dropping.

It could cause an issue due to the program not being coded to anticipate such a usage of those machine shops.