I mostly have problems when trying to play UMS maps with anti-hacks triggers or things I am not aware about. I do not hack in any ways and my friend tells me the problem comes from within my iMac.

What happen is when I join a map thta I cannot play, everything goes fine until I press start in the briefing. Once I do, Starcraft crashes and close.

Anybody know how to fix this problem? There are some good maps I havent been able to play because of this.

yep, this happens, something with the maps and the lack of certain unit sprites or something.

Some maps you can't even click on at any time or it crashes.

Deal with it or use bootcamp.

Anti-hack triggers are probably not the problem, if you're crashing. The crash-type (vision-based) antihacks are platform-neutral, while EUD-based antihacks almost always drop you rather than crash you (these can also be made platform-neutral with a minimal amount of effort, but unfortunately, map makers often don't bother).

Some older mapping tools (StarForge, for instance) have been demonstrated to occasionally cause corruption that will crash Mac users. The corruption is easily fixed, but unfortunately, once again, many map makers don't take the time. Some protection methods have the same issue: there are other protection methods that are at least as strong, and don't crash Macs, but people still use the unfriendly ones out of sheer thoughtlessness.

Finally, certain advanced map features (4x speed, for instance) are simply not Mac compatible. These features aren't massively common; usually the problem is something fixable and people just didn't take the time. Nevertheless, there are a few maps that simply can't be made platform-neutral. For those, you'll need to find a way to run Windows Starcraft, either with bootcamp or some form of emulation (I use VMWare).

AH triggers can crash you. CHW5.0h has older AH triggers, and it crashes mac users during the mission briefing.

Anything that causes a buffer overflow(extended players, portraits, unit deaths, units, etc.) has the potential to cause a crash to Macs, because while they may edit one section of memory on Windows that creates a cool effect, they target a completely different section for Macs, so at the least they'll cause a desync.

Weird thing is, I CAN go through sometimes if I continually try to enter it, either out of luck or when my friend host it right after (I can host the game) I crash several times.


Just wanted to know if it was possible to bypass it by just tricking my Mac.

1. virtualbox
2. tinyxp
3. windows version of SC.

You can bootcamp too, but virtualbox will run SC in a window or fullscreen without rebooting. That, or, you know, get a real operating system.

Can you guys tell me what triggers exactly crash my Mac? It would be appreciated thanks.

the ones with the "memory" condition in SCMDraft, which you can't open in OSX. They're also the "deaths" trigger which have an extended player or extended unit, then usually have a create action.

EUDs are quite difficult to comprehend. If you wanted to fix the anti-hack triggers, you'd have to add a separate condition which detects which version of SC you're using. That in itself is hard enough, especially without OSX. I don't have OSX, nor do I have any inclination of getting it.

The fact of the matter is that OSX doesn't have the resources Windows does when it comes to SC.

Actually, it's not necessary to do things that way. Although Oblivion is now protected against our Mac-friendly antihack, there are still things to be learned from the system:
1) Many EUDs are actually harmless to Macs. They won't work, to be sure, but they also won't crash. You will, of course, get problems when dealing with shared-action triggers, because they'll go for the PC users and not the Mac users, resulting in a desynch. But many non-shared EUD triggers will not fire, or more rarely, will fire at different times, for the Mac player, but won't result in a crash or anything.
2) Given (1), creating a Mac-friendly antihack is actually quite easy. All you need to do is add an EUD condition of some sort that will always fire for PC users and not for Mac users. In making our antihack, we cheated a little bit and simply used keypress detection for a number of common keys; sure, the hacker would theoretically be able to avoid it, but any benefit that they could get from hacking would be greatly outweighed by not being able to use hotkeys (or chat, or change maphack state, or even, if you wanted to get really adventuresome, move the screen by keyboard. Feel free to add as many "traps" as you want.) Anyway, those conditions were never satisfied for Mac users, even though the anti-hack conditions always were (due to the differences in memory configuration). So the result was:
-PC user, not hacking: Keypress detection always (in practice) satisfied; hack detection not satisfied. Trigger does not fire; no action is performed.
-Mac user: Keypress detection never satisfied; hack detection satisfied. Trigger does not fire; no action is performed.
-PC user, hacking: Keypress detection always satisfied; hack detection satisfied. Trigger fires for player only, performing a public action, causing player to desynch and be dropped from the game.
Testing with a mixture of Mac players, PC players without hacks, and PC players with hacks confirmed that the anti-hack was still successful at defeating the then-current version of Oblivion, while causing absolutely no problems to Mac users.

Of course, a mere few days after we came out with the system, Oblivion was modified to feature a general blanket protection against EUD antihacks... Given that, as far as I have been able to test, none of the EUD antihacks actually get through for the latest Oblivion versions, you might just want to save a couple of minutes and rip the anti out altogether instead of modifying it for compatibility. But that's another issue entirely.