Fiesta Fan Forums - [RELEASE] Fiesta Auto-Login Tool

Fiesta Fan Forums (http://www.fiestafan.com/forums/index.php)

- Fiesta General (http://www.fiestafan.com/forums/forumdisplay.php?f=6)

- - [RELEASE] Fiesta Auto-Login Tool (http://www.fiestafan.com/forums/showthread.php?t=9107)

[RELEASE] Fiesta Auto-Login Tool

Not sure exactly where goes; please move to a different section if need be!

For my return to FiestaFan.com I had to do something for the masses. I made a small program that will automatically log you in when you start the Fiesta Launcher.

This is a not GUI program so there is nothing to look at. All it does is sit in the background using a miniscule ammount of system resources and waits for the launcher to run. When it does it automatically fills in your username and password and hits the login button.

Note: It WILL wait for all updates to complete first, so no violation of TOS =)

Source code included and please read the readme!

If you have any questions please let me know.

Version 1:
http://filebeam.com/da9d1e6b913df07798bf21339d6abe7a

Version 2:
http://filebeam.com/2dc33926dc4b15ea8d4e6d30ca26e321

Version 3:
http://filebeam.com/5439eb26072131c16aa6053db2cf55b4

Code:

Scan Started Sun Jun 01 13:09:24 2008

-------------------------------------------------------------------------------





----------- SCAN SUMMARY -----------

Known viruses: 301201

Engine version: 0.93

Scanned directories: 0

Scanned files: 2

Infected files: 0

C:Documents and SettingsThievingSix.THIEVING-DAGANDesktopDelphi ProjectsFiesta AutologinFiesta Auto-Login.exe

C:Documents and SettingsThievingSix.THIEVING-DAGANDesktopDelphi ProjectsFiesta AutologinFiesta Auto-Login.zip

Data scanned: 2.15 MB

Time: 11.328 sec (0 m 11 s)

--------------------------------------

Completed

--------------------------------------

Eh.
Someone else try it first :$

Awesome! Extremely useful.

Can you post the code here first? And what language did you use?

I code in delphi, and the source code is in the zip file.

So what I understand from your code (although I've never seen that language before), you launch your window, look for the Outspark login window, find the textfields, wait for 1 second, and input the data if no updates are available, or if the window closes for updates.

Seems legit. One question, maybe I'm wrong, but you seem to code the program to run at windows startup. Why?

This may be a stupid question.. but bare with a programming noob...

where does it get your login and password from?

You input it in the program and then it stores it.

One more thing: Why do you set both email and password to lower case? People might have upper case letters in both.

Quote:

Originally Posted by Belaslav (Post 156657)

You input it in the program and then it stores it.

One more thing: Why do you set both email and password to lower case? People might have upper case letters in both.

How do you input it into the program?

OK, let us take each question one at a time =)

Quote:

Originally Posted by Belaslav (Post 156644)

The program runs like so:

Waits for the fiesta launcher to run
Finds the Email text box, Password text box, and the Login Button
Inputs the Email and Password into the correct edit boxes.
Waits until the Login button isn't disabled(No more updates).
Clicks the login button.
Closes the launcher once fiesta is running.

Also, the reason it runs at startup is so it will always be ready to auto log you in whenever you want to play. Easier than starting the Auto-Login Tool every time you want to login, that defeats the purpose.

Quote:

Originally Posted by Hessah (Post 156656)

This may be a stupid question.. but bare with a programming noob...

where does it get your login and password from?

When the program first starts up it reads from an INI file that is in the same folder as the program itself, download it and read the readme to know what I mean. =)

Quote:

Originally Posted by Belaslav (Post 156657)

You input it in the program and then it stores it.

One more thing: Why do you set both email and password to lower case? People might have upper case letters in both.

It doesn't set the password to lowercase, it sets the whole INI file lowercase so that when it finds the "email=" to find your email for example, it won't matter whether its "Email=" or "email=" or "EmAiL=".

Quote:

Originally Posted by Ninja_Medic (Post 156679)

How do you input it into the program?

Like stated above you put it into the INI file that accompanies the file. If you read the Readme.txt included you would know what I am talking about. =X

Having trouble with the INI file T.T

Error message:
http://img78.imageshack.us/img78/5103/randomqh8.png

So I put the email and password in with no spaces, as you said. But error message popped up when I tried to save it. Sorry, I iz hella noob with this kinda stuff X_X

Make sure that the program isn't running when you are changing the settings.

To close the program follow these steps:

Open taskmanager(I.E. Ctrl + Alt + Del).
Click the processes tab.
Find 'Fiesta Auto-Login.exe' and click it.
Click End Process.
Click OK to the resulting dialog.
Edit the LoginSettings.ini
Start the program back up.

Did what you said, still won't work

Hmm, well your error is happening because the Auto-Login Tool is running. Make sure everything named "Fiesta Auto-Login.exe" is not running in task manager.

A second option would be to copy the "Fiesta Auto-Login.exe" and "LoginSettings.ini" to a different folder. Then move the original ones to another folder as well. In the first one you moved edit the settings and run that one. Then restart your computer. After restart delete the ones you moved, not copied.

So it stores it in something that works like a clipboard?

OK, here is a detailed step-by-step analysis of how the Fiesta Auto-Login Tool works.

Program starts.
Reads loginsettings.ini for the login details.
Goes into sleep mode until the Fiesta Launcher is started.
When it is started it inputs your login credentials.
Waits for the login button to be enabled(Updates are done).
Clicks the login button.
Waits until Fiesta is running.
Closes the Fiesta Launcher.
Goes back into sleep mode.

Everything worked with the INI file... until...

http://img156.imageshack.us/img156/2637/67680134qr2.png that popped up when I tried to open Fiesta Auto-Login.exe

Oh and question... would you mind posting an .exe download link? .zip confuses me.

It's in a zip because it includes more than one thing. Right click it and click extract.

Also, your getting that error because a previous session of the program is running. End process on all running Fiesta Login exe's in the task manager as explained in an eariler post. You needed to edit the loginsettings.ini before you run the program as stated in the readme.txt =)

WHOO!

I figured it out! XD

This is really convenient!

No more typing for me. =D

Thanks for making such a cool program. :D:D:D:D:D:D:D:D:D:D:D:D:D:D:D:D:D

Quote:

Originally Posted by dako (Post 157234)

is it legit?

Fully.

Argh.

Let me try yet again.

Kay, I set it up properly, but when I click the icon ' Fiesta Auto-Login ' - nothing happens. It just blinks, then nothin happens :S

NVM. Didn't realize you have to have Fiesta Login window open.

Kay, finally got it! Great program :D

Okay...

it worked.. at first

until i restarted my computer...

do i have to re-activate the program every time i restart my computer?

Nope, if everything worked correctly it should start when your computer starts.

k i took a look at it.

1.) Do never and i mean never trust someone who asks for your login informations.(not even a tool).
2.) For me the tool just chrashes the launcher
3.) Never add yourself in "HKLM\Software\Microsoft\Windows\CurrentVersion\Ru n" without asking the user, a lot of secrurity tools go are very sensitive about that key.

Programming Tips
4.) Close a file after u are not using it anymore. Same goes for all handels
5.) Change the timer proc.
- The handels wont change, in the same launcher instance
- Check if the launcher is ready for input or still initialising
- Check if the client was closed, because the launcher stays in the bg while fiesta is running.
- Move all the code out of the Form(the best is if u dont need any form or timer)
- Make a little bit more readable :D it looks kinda weird will all the exits(returns).

----

And if the tool is talkactive or not i can not say. Delphi applications are a pain in the ass to debug. So i wont take a look into it :mad:

hmm a program to be more lazy! how neat! lol though i dont think im gonna need it cause i have 2 accounts that i switch through on fiesta, soo umm the whole typing in a username and password wont be needed after you use this program, though err thats it? kinda pointless, no? ^^ i just dont get it >.>

Quote:

Originally Posted by MaxOff

k i took a look at it.

1.) Do never and i mean never trust someone who asks for your login informations.(not even a tool).
Which is why I provide the source, compile it yourself if you don't trust me.
2.) For me the tool just chrashes the launcher
I doubt it crashes it, since it is only happening to you it's your problem not the programs.
3.) Never add yourself in "HKLMSoftwareMicrosoftWindowsCurrentVersionRun " without asking the user, a lot of secrurity tools go are very sensitive about that key.
I find it pointless to ask since security tools are going to go off when the person says yes anyway, plus this program isn't useful if you have to run it every time...
Programming Tips
4.) Close a file after u are not using it anymore. Same goes for all handels
Again, the file handle for the loginsettings.ini was never closed because I didn't want people editing it while the program was running. Also the other handle to the launcher(hProcess) never needed to be closed because it was used to kill the launcher. I.E. The handle became invalid anyway.
5.) Change the timer proc.
- The handels wont change, in the same launcher instance
No, the window handles don't change. Your point?
- Check if the launcher is ready for input or still initialising
Again, an extra piece of code that windows checks for itself. Pointless. The only time this is needed is when I wait for the Login button to become enabled.
- Check if the client was closed, because the launcher stays in the bg while fiesta is running.
No, it doesn't. I terminate it once Fiesta is running for that reason.
- Move all the code out of the Form(the best is if u dont need any form or timer)
Again, that would have been more complicated and pointless.
- Make a little bit more readable :D it looks kinda weird will all the exits(returns).
It's perfectly readable to me, sorry but I don't take everyone's reading preferences into account.

----

And if the tool is talkactive or not i can not say. Delphi applications are a pain in the ass to debug. So i wont take a look into it :mad:
How are they a pain in the ass, you just need to know what your doing. The source isn't provided for you to change, it's there in case you don't trust the compiled executable.

All in all you seem like you read the source but mentioned stupid things without thinking about how it worked. Don't do that.

Quote:

Originally Posted by Aryia (Post 157562)

Yup, just a time saver. =P You got to be real lazy to use this XD

Quote:

Originally Posted by MaxOff(Me)

Red: ThievingSix commentar
Blue: MaxOff commentar

I want to be green now =)

Quote:

Originally Posted by MaxOff (Post 157769)

k i took a look at it.

1.) Do never and i mean never trust someone who asks for your login informations.(not even a tool).
Which is why I provide the source, compile it yourself if you don't trust me.
I do trust the code, but not the binary. Noone says that the binary contains the same instructions as the source code
Which is why, if you didn't trust the binary, you can compile it yourself.

2.) For me the tool just chrashes the launcher
I doubt it crashes it, since it is only happening to you it's your problem not the programs.
Well it chrashed, and since its your programm that forced the launcher to crash. Make out of it what u want
OK, in a technical view it "crashes". A better word would have been "terminates". I suppose that I could have been nicer to the launcher and close it with a WM_Close message, but since it's not doing anything Windows critical I see no need to.

3.) Never add yourself in "HKLMSoftwareMicrosoftWindowsCurrentVersionRun " without asking the user, a lot of secrurity tools go are very sensitive about that key.f
I find it pointless to ask since security tools are going to go off when the person says yes anyway, plus this program isn't useful if you have to run it every time...
It is good pratice to ask the user before. But of course u dont have to do it.
Yeh, you got me there. I should have asked but I didn't see a big reason to.

Programming Tips
4.) Close a file after u are not using it anymore. Same goes for all handels
Again, the file handle for the loginsettings.ini was never closed because I didn't want people editing it while the program was running. Also the other handle to the launcher(hProcess) never needed to be closed because it was used to kill the launcher. I.E. The handle became invalid anyway.
Mhh great, u are so smart. Opening a file in with read and write share, so u block out other readers? Wait that makes no sence.... read and write share? Yes! Other programm can read and write the file while your Fiesta Auto-Login is running. But Notepad saves files without sharing so it fails. (anoying "feature" of notepad)
And actually expecting that windows cleans up after u, isnt very good pratice too
Ok, I guess I didn't set it to deny because I use a simpler version of file handles. A stream should do fine. Doesn't matter though, the resources used are discarded anyway when Windows shuts down. If your worried about a 300 byte file staying open then please, get over it =). Also, while it's not good practice. Windows does clean it up.

5.) Change the timer proc.
- The handels wont change, in the same launcher instance
No, the window handles don't change. Your point?
The code expect them to change nearly all the time
OK, the reason for an expected change in handles is because the fiesta launcher may run more than once. When a program is closed and reopened you need to refine them.

- Check if the launcher is ready for input or still initialising
Again, an extra piece of code that windows checks for itself. Pointless. The only time this is needed is when I wait for the Login button to become enabled.
There is a big difference between if the message queue is ready and if a button is enabled or not. Apperently u dont know that difference. And no Windows doesnt check that
There is NO possible way that the message queue not being ready will do anything to affect anything. Sending text to the text boxes after windows has established handles for them means, they are ready. "Apperently u dont know that difference".

- Check if the client was closed, because the launcher stays in the bg while fiesta is running.
No, it doesn't. I terminate it once Fiesta is running for that reason.
So what happends if Fiesta Auto-Login.exe is launched after a manual login?
I admit i wasnt very preciese. I actually meant the overall status of the client, not only if its running.
Re-read this entire conversation and you might realize that the program is meant to run at startup. Anyway, if it is run after a manual login, nothing would happen. What might?

- Move all the code out of the Form(the best is if u dont need any form or timer)
Again, that would have been more complicated and pointless.
Actually it would have made the programm: easier to read, faster and smaller. Especialy in the case of delphi.
OK, to me the size, speed, and ease of read didn't make it worth doing, but your right it would. I have a file path issue to fix as well so I can change it in the next release. The only reason that is a bit more complicated is because you can just drop the timer component on the form. When removing the form from the question it entails more work for a slight boost.

- Make a little bit more readable it looks kinda weird will all the exits(returns).
It's perfectly readable to me, sorry but I don't take everyone's reading preferences into account.
U dont have, too

----

And if the tool is talkactive or not i can not say. Delphi applications are a pain in the ass to debug. So i wont take a look into it
How are they a pain in the ass, you just need to know what your doing. The source isn't provided for you to change, it's there in case you don't trust the compiled executable.
With debugging i ment debugging on asm level, because i dont have an delphi debugger avaible right now, so asm had to suffice. And debugging delphi on asm level IS a pain in the ass.
And believe me, no windows user compiles progs before they use them. And i dont know why the linuxer love to do it. I only see wasted computer ressources in it.
Waste in computer resources??! LOL!

Red: ThievingSix commentary
Blue: MaxOff commentar
Green: ThievingSix commentary

Lol, battle of the programmers.

Too... much... quoted text.... x.x

Lol, read. YOU MUST ALL READ!!

Idk, go have some coffee or something.

Edit: Version 2 is up. See details in the changelog section of the Readme.

( refers to page before ) daamn so many colors lol that was interesting to read.

lol, would be funny if it had a sesson timer or something that recorded how long you played each time :eek:

Oooo, I can do that =D

Quote:

Originally Posted by ThievingSix (Post 158906)

Oooo, I can do that =D

yes, do that! =DDDDD

hhhmmm....

delphi language.....

interesting.....

ill edit this post after i compile...

i think theres something wrong with the binary... but lets see....

you should have use a much easier language. lol!

tip to people: dont just run any programs that ask for personal infos such as usernames and passwords. and i think this is against the ToS of outspark am i right? you cant use any 3rd party programs unless its approved by them.

overall...this would be a great program if proven to be clean...ill try to compile this when i got the time to make sure its safe. thanks for the thread starter.^^