Just using a bit of guesswork it is likely that the three <string> parameters would represent the following:
Recipient
Subject
Message Body
Of course, what order they go in isn't stated.
As for the <int> parameter, I think it may be something like the following:
Amount of inf to send
Type of Attachment to send (Inspiration, Enhancement, Recipe, Salvage, etc.)
Which attachment of the specified type.
Of course, not knowing what the valid integers are that it will accept doesn't help in determining how to use the command. Since ParagonWiki doesn't list this in the Slash Command List, it's still guesswork as to what is valid for int. You may want to look at /emailsend for help with the <string> portions. You could try the command in game and then compare what it says the parameters are to what ParagonWiki lists.
If the game spit out 20 dollar bills people would complain that they weren't sequentially numbered. If they were sequentially numbered people would complain that they weren't random enough.
Black Pebble is my new hero.
What were you trying to email? and was it to your global, or someone else?
"Most people that have no idea what they are doing have no idea that they don't know what they are doing." - John Cleese
@Ukase
Could this command be used in a macro or popmenu? I could see this being real useful for sending inspirations to email for storage on a long TF or Trial. If you figure it out, be sure to post back on what you learned.
Quote:
Int is short of Integer. Non decimal numbers.
|
Originally Posted by Apparition
I'm guessing that the <int> parameters correspond to codes for the type and ID of the attachment.
Thanks |
I have discovered the following parameters through trial and error.
/emailsendattachment <string1> <string2> <int1> <int2> <int3> <string3>
string1 = global name of the recipient.
string2 = subject field of the email
int1 = the amount of influence/infamy to attach
int2 = a type code : (2=inspiration, 5=enhancement, 11=salvage, recipes is still unknown)
int3 = the inventory location of the type: (0=lower left inspiration or the leftmost enhancement, or the first salvage in the inventory list)
string3 = message body
Example:
/emailsendattachment @apparition gifts 1000000 2 3 here you go.
will send an email to @apparition with the subject of gifts, 1000000 inf, the 4th inspiration from the inspiration tray and the message "here you go."
If anyone finds the type code for recipes please let me know.
Thank you very much for spending time on this, this is going to make emailing enhancements to myself SO much easier.
I'm sure the 15 second limit will still be there, but at least I can just mash a keybind for each slot and tab out for 15 seconds instead of having to open the UI every time.
Are the salvage slots just in the global order in "All" (i.e. no separate by tabs)? Was hoping for an easy way to do halloween salvage but it doesn't sound possible.
I first heard about this command from someone in a global channel that was having difficulty making it work. I looked at the parameters, made a guess, and had it work as expected after only a couple tries. The other person could not make it work at all, even after copy/pasting what I'd been entering.
With the help of others, we discovered that it was the space in his name that was causing the problem. We could all use the command to send mails to me or any of the other testers with one-word names. We could not get the command to send mail to multiple-word globals. We tried "@Global Name", @"Global Name", @Global_Name, and every other combination we could think of, but every mail we sent either failed with an error message, or disappeared, sent to a wrong address (for example, when someone tried @GlobalName).
I don't know if this bug still exists, or if it's been fixed.
@Roderick
Does anyone know what the /emailsendattachment parameters are.
The game returns...
Usage:emailsendattachment takes 6 args, you gave 4.
Send message <player names> <subject> <body> <influence>
emailsendattachment <string> <string> <int> <int> <int> <string>
The Send message line is consistent with the /emailsend command.
I'm guessing that the <int> parameters correspond to codes for the type and ID of the attachment.
Thanks