-pref not working; command line parameter order issue

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Select the "-perf" command line.
2. The application will place the "-perf" at the end of the string.
3.

What is the expected output? What do you see instead?
To function the "-perf" command must be the first parameter passed to the exe 
file.

What version of the product are you using? On what operating system?
v0.6

Please provide any additional information below.
It would be nice if the default behavior would post this parameter to the start 
of the command line list.

Original issue reported on code.google.com by kza...@gmail.com on 1 Nov 2011 at 3:41

[GoogleCodeExporter]

I can look into this for you. I was not aware -perf needs to be the first 
parameter. Is this documented somewhere?

Original comment by keke...@gmail.com on 4 Mar 2012 at 3:56

• Changed state: Accepted

[GoogleCodeExporter]

No, it is not documented anywhere.  I found that it works when it is the first 
parameter by process of elimination.  Until 2010 it had to be the last 
parameter.

Original comment by kza...@gmail.com on 4 Mar 2012 at 6:25

[GoogleCodeExporter]

I tested and I wasn't able to reproduce this issue. -perf was working as 
expected with it was the last parameter. Can you give me sample argument list 
to test with the -pref being last but not working?

Original comment by keke...@gmail.com on 7 Mar 2012 at 1:43

[GoogleCodeExporter]

The command line set "-windowed -email=kzaske@gmail.com -password=password 
-character= "name" -perf" did not work for me but the command line set "-perf 
-windowed -email=kzaske@gmail.com -password=password -character= "name"" does.

Original comment by kza...@gmail.com on 7 Mar 2012 at 1:50

[GoogleCodeExporter]

I just tested this to be sure just before I posted.

Original comment by kza...@gmail.com on 7 Mar 2012 at 1:51

[GoogleCodeExporter]

Try removing the "=" after parameters, the proper syntax is to just leave it as 
a space. The argument wizard (button in the argument line) should not be 
putting in the "=" unless you are manually doing this.

Please see:
http://wiki.guildwars.com/wiki/Command_line_arguments

Having
-windowed -email kzaske@gmail.com -password password -character "name" -perf

should work.

Original comment by keke...@gmail.com on 10 Mar 2012 at 2:41

[GoogleCodeExporter]

Hmmm...  That worked just fine, thanks.  I have been using command parameters 
to autologon long before Factions.
I believe they (the = charectors) date back to shortly after Guild Wars was 
released and were (at the time) required.  When the "new" -character parameter 
came out the example provided by ArenaNet had the equals symbol being used and 
it did not work without it, if memory serves me correctly.  
So when did they do away with the = requirement?

Original comment by kza...@gmail.com on 10 Mar 2012 at 12:07

[GoogleCodeExporter]

I am going to mark this as resolved. I am not aware of when they had the = as a 
requirement. If it is before the time of the wikis then the history of those 
pages would not reveal much either.

Original comment by keke...@gmail.com on 10 Mar 2012 at 5:13

• Changed state: Done

[GoogleCodeExporter]

OK, no problem with marking it resolved.  Yes, it was long before wiki.

Original comment by kza...@gmail.com on 10 Mar 2012 at 5:14