Hard Light Productions Forums
Modding, Mission Design, and Coding => The FRED Workshop => Topic started by: The_Force on May 18, 2012, 01:22:16 pm
-
Possible? How? :confused:
-
Put a # before the message sender in the SEXP.
e: # not $ you ****ing idiot battuta
-
Put a # in front of the sender's name, for example #Alpha 1.
-
nither of those work, what I'm trying to do is send the message form the players pilot, so if the players pilot was called vampire it would read as coming from vampire.
-
Yes, you need to set the message sender as #Vampire, it will work.
Remember that you do this in the SEXP, not in the ship editor callsign field. You need to right click on the argument in send-message and manually edit it with 'edit data'.
-
Yes but if the player sets his name as someting else then they won't match, I'm looking for something like $callsign.
-
Wait, you mean the player's profile name?
-
Yes, sorry about being unclear.
-
Hmmmmmmm. Have you tried setting the value of a string variable to $callsign? Does that work?
-
No it just sends the message from command.
-
Hmm, this is an interesting puzzle.. I must try some things...
-
I'm pretty sure I saw this in one campaign I played... I just forget which one
-
I wonder if #$callsign would work. My hunch is no.
Assigning $callsign to a string variable and then using when-argument should do the trick though.
-
I wonder if #$callsign would work. My hunch is no.
Assigning $callsign to a string variable and then using when-argument should do the trick though.
Question is, how do you assign $callsign to a string variable? I just tried entering it directly as the value and it doesn't work.
e: haha, if you do '#$' you get some other currency marker, idk what
-
lol, it looks like the galactic credit symbol from star wars
-
lol, it looks like the galactic credit symbol from star wars
Oh what really? That's awesome. Pics? :P
-
So I played around with this a bit. So it looks like the "$Callsign" is NEVER parsed/replaced in string literals or variables, making it impossible to set ships' callsigns or names to the player's callsign. It's only parsed in text in messages, which does not include that ship's name. Including $callsign in the field for sending messages (like "#($callsign)" or "# $callsign") simply displays the "$callsign" text.
A script might be able to get the value into a variable, or possibly FSO could parse the $callsign string in events- I doubt that would break anything, so maybe the SCP would take a look at it.
-
Well code change is no good due to the mission being for saga :mad: :banghead: Looks like I'm stuck.
-
You could ask the saga devs for help....
-
lol, it looks like the galactic credit symbol from star wars
That probably comes from your guys' using my FotG font in BP--it would just display a $ in a normal font.
-
lol, it looks like the galactic credit symbol from star wars
That probably comes from your guys' using my FotG font in BP--it would just display a $ in a normal font.
BUSTED!
-
lol, it looks like the galactic credit symbol from star wars
That probably comes from your guys' using my FotG font in BP--it would just display a $ in a normal font.
BUSTED!
More like swashmebuckle busted, for being AWESOME
On trial by judge (no peers located) - GUILTY! Going to MUSIC JAIL
-
lol, it looks like the galactic credit symbol from star wars
That probably comes from your guys' using my FotG font in BP--it would just display a $ in a normal font.
BUSTED!
More like swashmebuckle busted, for being AWESOME
On trial by judge (no peers located) - GUILTY! Going to MUSIC JAIL
:lol:
-
Can I get a witneeeeeeeeeeeeeeeeeeeess?