Report, edit, etc...Posted by warhammer40000 on 2005-02-25 at 21:13:42
So everyone has encountered that problem with the 1000 milliseconds equaling 1 sec instead of 100 equaling 1 sec. well mine goes deeper. way! For some reason, sometimes my wait, equals nothing. it'll be like--
EX.
send transmission set whatever secs say yadda yadda ya.
wait 99999999999 milliseconds
kill some unit somewhere
AND IT KILLS THAT SOME UNIT SOMEWHERE RIGHT AWAY! (that wasn't the only an examp i have more up my sleeve!!!) uh..... help!?! if you need it more detailed tell me or somthin i dunno...
Really, all that I have is a basic editor that they gave me with starcraft, because blizzard hates Mac.
PS. Praise Satan
EX.
send transmission set whatever secs say yadda yadda ya.
wait 99999999999 milliseconds
kill some unit somewhere
AND IT KILLS THAT SOME UNIT SOMEWHERE RIGHT AWAY! (that wasn't the only an examp i have more up my sleeve!!!) uh..... help!?! if you need it more detailed tell me or somthin i dunno...
Really, all that I have is a basic editor that they gave me with starcraft, because blizzard hates Mac.
PS. Praise Satan
Report, edit, etc...Posted by BeeR_KeG on 2005-02-25 at 21:23:58
1000 milliseconds = 1 second
This can't be changed because we are using a system of measurement and it can't be changed just becasue we want to. You could change the miliseconds to centiseconds so that 100 centiseconds = 1 second.
Umm... Why would you possibly want to wait so long? That is a wait of 15 days and it doesn't surprise me that waits bug up and go instantly after a set amount of time.
This can't be changed because we are using a system of measurement and it can't be changed just becasue we want to. You could change the miliseconds to centiseconds so that 100 centiseconds = 1 second.
QUOTE
wait 99999999999 milliseconds
Umm... Why would you possibly want to wait so long? That is a wait of 15 days and it doesn't surprise me that waits bug up and go instantly after a set amount of time.
Report, edit, etc...Posted by warhammer40000 on 2005-02-25 at 21:28:29
QUOTE(BeeR_KeG[eM)
,Feb 25 2005, 09:23 PM]1000 milliseconds = 1 second
Umm... Why would you possibly want to wait so long? That is a wait of 15 days and it doesn't surprise me that waits bug up and go instantly after a set amount of time.
[right][snapback]153241[/snapback][/right]
That was an example i really didnt mean 9999999999 millisecs!!!Umm... Why would you possibly want to wait so long? That is a wait of 15 days and it doesn't surprise me that waits bug up and go instantly after a set amount of time.
[right][snapback]153241[/snapback][/right]
Report, edit, etc...Posted by Rantent on 2005-02-25 at 21:46:31
Then what did you mean? Because your making less sense to me now than you were at the begining.
Report, edit, etc...Posted by warhammer40000 on 2005-02-25 at 22:03:43
QUOTE(Rantent @ Feb 25 2005, 09:46 PM)
Then what did you mean? Because your making less sense to me now than you were at the begining.
[right][snapback]153253[/snapback][/right]
I mean it could be to 1 millisecond to 999999999 milliseconds it doesn't matter, almost all the triggers just go instantly![right][snapback]153253[/snapback][/right]
Report, edit, etc...Posted by Mini Moose 2707 on 2005-02-25 at 23:03:15
First off, why is this in Concepts?
Secondly, post the map. Triggers don't screw up like that for no reason, nor does your description provide any of the other factors that can cause it to screw up.
» Moved to Assistance
Secondly, post the map. Triggers don't screw up like that for no reason, nor does your description provide any of the other factors that can cause it to screw up.
» Moved to Assistance
Report, edit, etc...Posted by DevliN on 2005-02-25 at 23:31:39
Either you used too many waits, accidentally made hyper triggers, or purposely made hyper triggers and forgot about them.
And do you even know how to use the send transmission trigger? I think that is your issue. You have the transmission being sent with a short wait time and then the actual wait trigger after it is too short, thus killing the unit quickly.
Post the map. You make no sense at all.
And how do you expect to get help when you aren't even posting the problem?
And do you even know how to use the send transmission trigger? I think that is your issue. You have the transmission being sent with a short wait time and then the actual wait trigger after it is too short, thus killing the unit quickly.
Post the map. You make no sense at all.
QUOTE
That was an example i really didnt mean 9999999999 millisecs!!!
And how do you expect to get help when you aren't even posting the problem?
Report, edit, etc...Posted by warhammer40000 on 2005-02-26 at 00:20:19
QUOTE(DevliN @ Feb 25 2005, 11:31 PM)
Either you used too many waits, accidentally made hyper triggers, or purposely made hyper triggers and forgot about them.
And do you even know how to use the send transmission trigger? I think that is your issue. You have the transmission being sent with a short wait time and then the actual wait trigger after it is too short, thus killing the unit quickly.
Post the map. You make no sense at all.
And how do you expect to get help when you aren't even posting the problem?
[right][snapback]153343[/snapback][/right]
ugh.... first of all... why dont you just TAKE ME BEHIND THE DUMPSTER AND SHOOT ME!?!?!?!? And do you even know how to use the send transmission trigger? I think that is your issue. You have the transmission being sent with a short wait time and then the actual wait trigger after it is too short, thus killing the unit quickly.
Post the map. You make no sense at all.
And how do you expect to get help when you aren't even posting the problem?
[right][snapback]153343[/snapback][/right]
look, there are so many of the wacked up triggaz i gotta puke so i just made an example... but i'll check what u said anyway.Report, edit, etc...Posted by MindArchon on 2005-02-26 at 00:22:17
Its your transmission trigger I beleive.
Set the transmission time to 0.
Set the transmission time to 0.
Report, edit, etc...Posted by (U)Bolt_Head on 2005-02-26 at 00:23:30
I almost fell out of my chair laughing lol, thanks.
milli is the prefix meaning 1000th
so 1 second is equal to 1000 milli seconds.
Also the wait attached to a transmission doesn't work that way. You will need another wait after the transmission to delay the killing of the unit.
milli is the prefix meaning 1000th
so 1 second is equal to 1000 milli seconds.
Also the wait attached to a transmission doesn't work that way. You will need another wait after the transmission to delay the killing of the unit.
Report, edit, etc...Posted by warhammer40000 on 2005-02-26 at 00:26:39
uh... thx mindarchon and bolthead.... at least i didnt picture u with a bloody axe in ur hand when i read ur reply! 
I'll try ur stuff out and i'll see if it works! thx 
I'll try ur stuff out and i'll see if it works! thx Report, edit, etc...Posted by DevliN on 2005-02-26 at 00:27:01
QUOTE
ugh.... first of all... why dont you just TAKE ME BEHIND THE DUMPSTER AND SHOOT ME!?!?!?!?
Well then nothing would change on your map. Even though I may have seemed harsh, everything I sai din that post was helpful to you now and for future reference. Its always good to actually explain your problem rather than just give an example that doesn't make sense to us.
Report, edit, etc...Posted by warhammer40000 on 2005-02-26 at 00:31:15
Thats very true... i think my problem is fixd so thx.. im just not gonna try it right now but probly tomorrow..... i hope i will look like this--- 
Report, edit, etc...Posted by Red2Blue on 2005-02-26 at 00:44:47
I posted a concept on how wait triggers gone wild,
I believe it was called: 'Synced/Sliced Wait',
I could be wrong.
Refer to that if your problem isn't solved.
I believe it was called: 'Synced/Sliced Wait',
I could be wrong.
Refer to that if your problem isn't solved.
Report, edit, etc...Posted by RexyRex on 2005-02-26 at 00:45:30
Don't use waits in transmissions, I don't like them .
Transmission, time: 0.
Wait(1000);
Simple, and it works.
.Transmission, time: 0.
Wait(1000);
Simple, and it works.
Report, edit, etc...Posted by Red2Blue on 2005-02-26 at 00:51:02
Sorry a bit off topic,
Wtf is a Karma?
I accidentally clicked on [Give] for someone else...
Did I give something I owned? Minerals?
How can I remove this karma?
Wtf is a Karma?
I accidentally clicked on [Give] for someone else...
Did I give something I owned? Minerals?
How can I remove this karma?
Report, edit, etc...Posted by RexyRex on 2005-02-26 at 00:54:33
Look in the FAQ forum. There is a new topic about it.
Wow we sure went off topic
.
Wow we sure went off topic
.Report, edit, etc...Posted by www.com.au on 2005-02-26 at 01:40:53
lol yeh check either the latest forum in garbage or FAQ..
wouldnt it be funny if we spent like 8 pages talking about karma? lol anyways...
wouldnt it be funny if we spent like 8 pages talking about karma? lol anyways...
Report, edit, etc...Posted by LegacyWeapon on 2005-02-26 at 01:46:56
QUOTE
TRANSMISSION
A transmission is a combination of several different actions. First, you need to specify which unit at a location you want to send the transmission. This unit’s portrait will be displayed for the duration of the transmission. You then need to select a WAV file to play, how long to animate the unit portrait, and what text message to display for players that have Subtitles turned on. The player receiving the transmission will receive a minimap ping when the transmission starts, and can press the space bar to center their screen on the unit sending the transmission.
The wait is for "how long to animate the unit portrait."A transmission is a combination of several different actions. First, you need to specify which unit at a location you want to send the transmission. This unit’s portrait will be displayed for the duration of the transmission. You then need to select a WAV file to play, how long to animate the unit portrait, and what text message to display for players that have Subtitles turned on. The player receiving the transmission will receive a minimap ping when the transmission starts, and can press the space bar to center their screen on the unit sending the transmission.
We really do have tutorials for everything. It was in Reference Lists -> Trigger Actions...
Report, edit, etc...Posted by (U)Bolt_Head on 2005-02-26 at 03:43:46
QUOTE(Red2Blue @ Feb 25 2005, 11:44 PM)
I posted a concept on how wait triggers gone wild,
I believe it was called: 'Synced/Sliced Wait',
I could be wrong.
Refer to that if your problem isn't solved.
[right][snapback]153446[/snapback][/right]
I believe it was called: 'Synced/Sliced Wait',
I could be wrong.
Refer to that if your problem isn't solved.
[right][snapback]153446[/snapback][/right]
R2B your Sliced Wait tutorial / idea is WAY beyond this persons scope of understanding. People need to learn not to overwelm beginners with really complex issues.
Report, edit, etc...Posted by warhammer40000 on 2005-02-26 at 19:51:22
QUOTE(RexyRex @ Feb 26 2005, 12:45 AM)
Don't use waits in transmissions, I don't like them .
Transmission, time: 0.
Wait(1000);
Simple, and it works.
[right][snapback]153448[/snapback][/right]
thx alot guys! all ur suppot n crap fixed my map! It all goes in order. well thx alot! .Transmission, time: 0.
Wait(1000);
Simple, and it works.
[right][snapback]153448[/snapback][/right]
Now back to my rpg... ull see a new rpg hitten the map soon! (not very soon, i'm working on two maps at the same time with a basic editor!)
Report, edit, etc...Posted by RexyRex on 2005-02-26 at 23:15:16
(w00t, another score for Rexy on helping out the poor souls in Map Making Assistance)
No problem.
No problem
.