Use GetLocalPlayer() to drop the player in quesition out of sync (disconnect them) from the rest of the players.
This is as easy as 123, basically create a location for him at point 0,0 and he will drop out of sync.
Then create your infinite loop (again within the asyncronous block to stop you creashing the rest of the players). This will have to be stackless (I advise an event related loop).
Incase you are not aware, GetLocalPlayer() returns a different player for each computer instance running your map for a specific host instance. Computer slots or empty slots or neutral slots can not be returned via GetLocalPlayer().
An example of its use...
JASS:
//before code.
if GetLocalPlayer == yourplayer then
//OOS code.
endif
//after code.
The before and after code will run for all players. The OOS code will run only for the human player playing the player contained in the variable yourplayer.
Be advised that adding something like this to a map will most likly get the map
rejected due to being totally stupid as far as programming goes and being totally retarded as far as map design goes. The rejection reason could be one of the following as an example. . .
Map has buggy code, falls into infinite loop.
Map could cause data loss due to itentional crashing on single core processors.
Map does totally stupid things for no reason like crashing players for buying an item.
How many comercial games do you play that specially and with intent crash players for doing something? I in my experience have not encountered any such game and probably with a very good reason.
