Staredit Network

Staredit Network -> SCMDraft -> Forces in Trigedit

Report, edit, etc...Posted by ScrollMaker on 2005-06-19 at 10:06:25

I can't seem to get any trigger to work for a force. I keep getting the player name expected error. Any hints on getting this to work?

Edit: nvm

ADDITION:

QUOTE(ScrollMaker @ Jun 18 2005, 03:39 PM)

I can't seem to get any trigger to work for a force. I keep getting the player name expected error. Any hints on getting this to work?

Edit: nvm

Actually I still need help. That "nvm" was about something else.

Report, edit, etc...Posted by Snipe on 2005-06-19 at 11:28:10

Wow that was quit... Confusing.. You said somthing then quoted yourself? lol. anyways i don't understand your problem.

Report, edit, etc...Posted by LegacyWeapon on 2005-06-19 at 15:33:14

Make sure it is the Force name.

Report, edit, etc...Posted by chuiu on 2005-06-19 at 17:41:48

If you're using the color codes, make sure you change them to work with trigedits format. I find it pretty dumb we have to do that though.

Report, edit, etc...Posted by ScrollMaker on 2005-06-20 at 13:34:04

QUOTE(chuiu_os @ Jun 19 2005, 04:41 PM)

If you're using the color codes, make sure you change them to work with trigedits format. I find it pretty dumb we have to do that though.

I am using color codes. The exact string for the name as it shows it in the string editor for my force is "<7>Heroes". I tried each of the triggers shown below, but they will not work.

CODE

Trigger("<7>Heroes"){
Conditions:
Always();

Actions:
Wait(2500);
}

//-----------------------------------------------------------------//

CODE

Trigger("Heroes"){
Conditions:
Always();

Actions:
Wait(2500);
}

//-----------------------------------------------------------------//

CODE

Trigger("Force 1"){
Conditions:
Always();

Actions:
Wait(2500);
}

//-----------------------------------------------------------------//

Report, edit, etc...Posted by chuiu on 2005-06-20 at 14:16:04

Trigedit doesn't use the <#> convention. It turns them/reads them as something like //####. I told LW to change his guide but apparently he forgot to change it. I suggest you go into X-tra or something and put in every color code in a comment seperated by spaces and just save which one is which to a txt file or something. It's pretty stupid, I know, but you need to know the right ones if your force is using color codes.

Report, edit, etc...Posted by Shadow181 on 2005-06-24 at 09:47:05

I hope I can help:
I have had problems like that, but I managed to fix it and kind of modified my trigedit help thingie so now it is more helpful to me

.
So Download it and you can see. blah blah blah. Just download this:

And you will see what I mean.
Or you can see it here:

nvm, I will just copy the hole thing:
Forces Colored Text (this is what you need):
Light blue (1) = <1> = \x001
Light blue (2) = <2> = \x002
Green = <3> = \x003
Light green = <4> = \x004
Grey = <5> = \x005
White = <6> = \x006
Red = <7> = \x007
Invisible = <8> = \x008
Overlap back (Center align) = <C> = \x013
Overlap front (Right align) = <R> = \x012

Hope you like and that it is not too confusing

Report, edit, etc...Posted by chuiu on 2005-06-24 at 10:31:25

That entire thing is just spam, the readme contains most of it.

Report, edit, etc...Posted by Clokr_ on 2005-06-24 at 10:54:21

chuiu: he's just trying to help...

scrollmaker: looks like trigedit uses C format to add those characters wich is \x and the hexadecimal number of the character to place. You'll have to look at the guide to know wich number is wich mark :/

Report, edit, etc...Posted by Shadow181 on 2005-07-02 at 21:44:23

So did I help?

Report, edit, etc...Posted by Shadow_da_Sniper on 2005-07-03 at 22:05:44

I hope you did, cause you helped me a lot.

Report, edit, etc...Posted by Shadow181 on 2005-07-05 at 20:24:45

QUOTE(chuiu_os @ Jun 25 2005, 12:31 AM)

That entire thing is just spam, the readme contains most of it.
[right][snapback]243030[/snapback][/right]

awwww, comon!! That took me, what, 5 minutes to do. Don't be so critical bcause I was the only person to think of modifying my Trigedit guide...

Report, edit, etc...Posted by chuiu on 2005-07-05 at 21:37:07

LW was the first person to. He made what you probably edited. The previous one was very simple and lacked in essential information.

Report, edit, etc...Posted by LegacyWeapon on 2005-07-05 at 22:22:23

Just so you know, when you do enter '<8>' into TrigEdit and compile it, it will turn out to be '\x008'. That's why I didn't bother with the "excess" information.

Report, edit, etc...Posted by Shadow181 on 2005-07-06 at 01:35:31

QUOTE(chuiu_os @ Jul 6 2005, 11:37 AM)

LW was the first person to. He made what you probably edited. The previous one was very simple and lacked in essential information.
[right][snapback]254127[/snapback][/right]

when I said my trigedit guide I meant the version I downloaded from LegacyWeapon, I called it mine because it is on my computer.

Report, edit, etc...Posted by HeRtZ on 2005-07-06 at 05:42:35

i dont even understand why scmdraft doesnt have a normal trigger editor

that would be really nice if it did

but yeah i love the program and i dont know why i posted this.

Report, edit, etc...Posted by Shadow181 on 2005-07-06 at 05:50:35

QUOTE(HeRtZ @ Jul 6 2005, 07:42 PM)

i dont even understand why scmdraft doesnt have a normal trigger editor
[right][snapback]254476[/snapback][/right]

Well trigedit is pretty good because it makes it MUCH easier to copy and change triggers.

QUOTE(HeRtZ @ Jul 6 2005, 07:42 PM)

but yeah i love the program
[right][snapback]254476[/snapback][/right]

so do I

Report, edit, etc...Posted by Cole on 2005-07-06 at 10:42:31

QUOTE

i dont even understand why scmdraft doesnt have a normal trigger editor

It's actually pretty good....at least for me...beacuse of my style. I like having very orginized triggers. Not having to click move up or down a hundred times really helps

. Since I can start anywhere real easy, it works well for my style of doing triggers.

Though to each his own.

Next Page (1)