Report, edit, etc...Posted by n2o-SiMpSoNs on 2004-11-15 at 18:48:45
| Trigger |
| Description: |
| Lag Test |
| Players: |
| ¤ player 1 |
| Conditions: |
| ¤ Player one brings at least one any unit to location 'X' |
| Actions: |
| ¤ Create 255 units at 'X' Create 255 units at 'X' Create 255 units at 'X' Create 255 units at 'X' Kill all any unit at 'X' |
What am i doing wrong to do a lag test???
Do i need to make it a switch?
or do i put a preserve trigger??
Report, edit, etc...Posted by .Coko[CK] on 2004-11-15 at 18:52:29
Make sure that location is minimum size and over unplaceable terrain with a building, or ground unit and that you move the man away and include Preserve.
Report, edit, etc...Posted by n2o-SiMpSoNs on 2004-11-15 at 19:14:18
Thank You!! Preserving trigger worked when i tried it.
Report, edit, etc...Posted by Zero on 2004-11-15 at 19:45:25
You need to make it to create a unit at (location) and then create evrey thing...but you could also do it for certain people.
Report, edit, etc...Posted by KaboomHahahein on 2004-11-15 at 19:52:42
InSaNeMaPpEr, do you have any idea as to what you are talking about? Because...
1.What you just said made no sense at all.
2. The answere has already been asnwered.
1.What you just said made no sense at all.
2. The answere has already been asnwered.
Report, edit, etc...Posted by greenreaper on 2004-11-15 at 20:19:06
Well, when you do the "lag" test, it only detects slow computers, not "laggy" internet connections. When a player activates a lag test, you could also put "display trigger" to display "blank" and play a "blank" noise to that players wouldn't have to see/hear those annoying 'UNITS CAN'T BE PLACED' error. 
Report, edit, etc...Posted by Zero on 2004-11-15 at 20:20:26
Slow computer = Laggy game...so the person must be laggy if they have a slow comp or internet connection
Report, edit, etc...Posted by n2o-SiMpSoNs on 2004-11-15 at 20:32:34
All the lag test does is make a bunch of observers in a little itty bitty location and then kill them..(CAUSING LAG) then their name pops up. Then you use the banner and ban them because you cant have lag in bounds or else it sucks...!
EDIT:*or else*
EDIT:*or else*
Report, edit, etc...Posted by (U)Bolt_Head on 2004-11-15 at 20:53:22
People actually do this? how retarded.
Report, edit, etc...Posted by Coop on 2004-11-15 at 21:03:23
i think bounding is so dumb. so boring and it's all repititous anyway
Report, edit, etc...Posted by KaboomHahahein on 2004-11-15 at 21:06:25
Just for the record there are 300+ bounds out there on battle.net. Stop making bounds unless you find a cool way of making new obstacles and cool new concepts in them.
Report, edit, etc...Posted by Deathknight on 2004-11-15 at 21:17:22
QUOTE
What am i doing wrong to do a lag test???
Everything.
First, get rid of those create unit triggers. That just makes everything look like
... Next, find some other method of "testing how fast the person's computer is".Report, edit, etc...Posted by Zero on 2004-11-16 at 11:17:55
I was testing some things on my map for a "lag test" i found out if you keep enabling and disabling the doodad state for a supply depot...it causes people to lag out/drop...but the problem is that the person has to be looking at the supply depot for it to work...so if you find a way to keep a person's screen on it..it will cause him/her to drop.
Report, edit, etc...Posted by .Coko[CK] on 2004-11-16 at 13:05:26
It will cause anyone to drop up, because you shouldn't do it in front of the screen. Christ.
Report, edit, etc...Posted by KaboomHahahein on 2004-11-16 at 16:08:29
Yes he is saying that so he can help you. You should be happy so many people are willing to help you. And we all already know about that some disabled buildings/units will cause you to crash. "Advanced"...
Report, edit, etc...Posted by .Coko[CK] on 2004-11-16 at 16:21:15
Simple way of testing if someone lags is to only play on LAN, or failing that, buy everyone a broadband connection, lag is almost a certain factor in games. Accept and move on.
Report, edit, etc...Posted by Chill on 2004-11-16 at 21:53:34
Creating a load of burrowed units at the same location and then telling them to unburrow works better than unplaceable units.
load of burrowed units at the same location and then telling them to unburrow works better than unplaceable units.Report, edit, etc...Posted by eXiLe on 2004-11-16 at 22:54:05
Honestly, I hate people who hate bounds...Although I myself know that bounds are the same thing, why do you people always say Bounds Suck. I just play them for fun and sometimes make them. Can't people just make the type of map they want? Why do you people always say bounds suck?? I know that many of you do not like them, but I do not know why. Just play for fun geez.
Report, edit, etc...Posted by Zero on 2004-11-17 at 21:57:31
I dont like them because these days the bounds are getting impossible to beat...and they are barely no skill in making them
Report, edit, etc...Posted by KaPS on 2004-11-28 at 16:27:27
Kinda weird how this went from lag tests to attacking/defending bounds. But o well.
The way i do lag tests is:
Player 1 brings at least 1 'Lag Tester' to 'Lag Test'
then
Display for current player 'Lag Test'
Move all 'Lag Tester' for player 1 at anywhere to 'Lag Restart'
Wait for 5000 (ms)
Center View for current player at 'lag test'
Create 50 'Lag Tests'(Protoss Observers) for player 8 at 'Lag Test'
Create 50 'Lag Tests'(Protoss Observers) for player 8 at 'Lag Test'
Create 50 'Lag Tests'(Protoss Observers) for player 8 at 'Lag Test'
Create 50 'Lag Tests'(Protoss Observers) for player 8 at 'Lag Test'
(That repeats until u only have 3 more slots left for actions)
Kill all 'Leg Tests' for player 8
Preserve Trigger
Comment: Lag Test
The way i do lag tests is:
Player 1 brings at least 1 'Lag Tester' to 'Lag Test'
then
Display for current player 'Lag Test'
Move all 'Lag Tester' for player 1 at anywhere to 'Lag Restart'
Wait for 5000 (ms)
Center View for current player at 'lag test'
Create 50 'Lag Tests'(Protoss Observers) for player 8 at 'Lag Test'
Create 50 'Lag Tests'(Protoss Observers) for player 8 at 'Lag Test'
Create 50 'Lag Tests'(Protoss Observers) for player 8 at 'Lag Test'
Create 50 'Lag Tests'(Protoss Observers) for player 8 at 'Lag Test'
(That repeats until u only have 3 more slots left for actions)
Kill all 'Leg Tests' for player 8
Preserve Trigger
Comment: Lag Test