Talk:Message
| Remember to sign your comments! | |
| Use ~~~ to sign with your username. | E.g., JT |
| Use ~~~~ to sign with your username and the current date. | E.g., JT 14:38, 31 March 2006 (EST) |
What is no time is specified, is there a default time that the message stays up? --User:Blakestr
- Definitely. I'll have to test to give you an exact figure, but it certainly does have a default time. --JT 15:01, 31 March 2006 (EST)
Tegid 23:42, 5 April 2006 (EDT): Does Message support 10 variables like MessageBox or just the two as per the example? If ten, should we put [var1], ... ,[var10] or something similar in place of [var1], [var2] ?
- I'm the one who added the 10 max information to MessageBox based upon the CS warning "max variables of 10 exceeded". However I just tested both Message and MessageBox and the max is actually 9. I'll edit Message and MessageBox to reflect this. I think keep the example as "[var1], [var2]"; it's less confusing, and once you work out how to do two more should be simple. —mmmpld 00:46, 6 April 2006 (EDT)
Tegid 01:06, 6 April 2006 (EDT): So the next question is, is there a format command to display References? The %f commands aren't doing it. Neither does %h %l or %r though %r actually prints an r and the others print nothing.
- I want to know the answer to this too, is there a way to output the reference in a message?--Omzy 00:41, 10 June 2006 (EDT)
- A reference-variable isn't just the FormID or we could use unsigned longs instead. It's rather a pointer structure of which the FormID is just one element. So no, I don't think there's any way for a script to access the FormID-value of a reference. --JOG 04:45, 10 June 2006 (EDT)
- Use %X.
- E.g.
- set mySelf to getSelf
- message "%X" mySelf
- -- Thalassicus
- A reference-variable isn't just the FormID or we could use unsigned longs instead. It's rather a pointer structure of which the FormID is just one element. So no, I don't think there's any way for a script to access the FormID-value of a reference. --JOG 04:45, 10 June 2006 (EDT)
Ericpar 20:31, 14 August 2006 (EDT) Has anyone actually tested the DisplaySeconds parameter? Becuase no matter what value I supply for this parameter, the message always stays up for its default duration (approx 3 seconds). E.g., "Message 'Hello World', 1" and "Message 'Hello World', 100" behave identically on my system. I have the official 1.1 patch, and I tested this with no mods loaded. If I type "Message 'Hello World', 1.0", it complains that the DisplaySeconds parameter must be an integer, so it definitely takes a parameter for the display time, but the implementation appears to be broken.
- Dragoon Wraith TALK 23:30, 14 August 2006 (EDT): I've been using the 1s display time, as well, and while I haven't specifically timed it, seems to me that they do, in fact, last longer than 1s. You may be right.
Arthmoor 06:12, 6 September 2009 (EDT) It looks like the message will remain on screen for fQuestDelayTime seconds. I just had a script I'm debugging spam the message display with one set for .01 and it was impossible to read the output.