Bah, simple when you know how :D

Thanks Image!

Hi again

I'm still struggling to get this working.

I'm getting the following error on the minilogin shell.
World.exe shows

I`ve ran in the loginserver.sql and configured the db.ini. Also ensuring that the its set to minilogin in the variables DB.

Any help would be great.

Thanks

War

You gotta set it to Public, not MiniLogin (it's in Variables)

The MiniLogin type will work I think, it just seems to have more checks like the world version and such :)

Anyway I'm still unsure about this, but what I'm looking for in this new mini-login, is unlimited user/player accounts. the reason for this is I already have hundreds of users for the AX_CLASSIC Server Repack (probably still have people that use my older MiniLogin package too), and they already have their characters and accounts made (the REPACK updates characters to newer versions of DB). My test server, which I don't promote and use at home, has 126 accounts - I need to protect those too, as I see people playing there.

I would even be willing to trade this feature off with only one game server able to connect LS. I would still greatly benefit because it has a true account system that doesn't require the old ip system

Three game servers hooked up to the LS would be nice, I could bring back my old ax_peq , and even some other old DB i was thinking of resurrecting.

Unlimited would be even nicer , all us "Minilogin" people could hook up with each other if we wanted.

But it's not needed - a true account system that doesn't require the old ip system is what I need, I think this wouldn't burst anybody's bubble.

Well the 'eqemu team' from what I understand was not too encouraged with the new minilogin, I am waiting on them to decide the next course of action for the login server since from what I read they are considering that as one option. I would rather they made that decision first, but if things continue to stall like they have who knows.

Well, Like I said nerf it down to one server on the LS.
Give me a good account system that doesn't require the old ip system . That's not asking for nothing other than an upgrade to the old Minilogin.
They can't feel threatened by that!

They didn't even like the idea that it authenticated user/pass.

Besides the point, if there was a public LS where you had unlimited accounts that anyone could get, it would be time for a login server list. I think if the LS is released to the public it should be a responsible release. Eg. there is some way for everyone to know about all login servers (that people host and want public), and some generic method for handling user accounts (this is more tricky and may not be possible). But a public server list would be key.

Isnt the server discussion area for precisly that listing your servers?

PLEASE relase a minilogin that has a good number of users allowed me personally im with angelox i only want one world server and a good ammount of accounts allowed black hand of doom had over 700 accounts before the change to your minilogin

oh one matter of note i tested the old minilogin theres no limit on users if there is supposed to be it doesnt work lol i made a ton of accounts and could login to one with a id of 199 in the database

Thats not really what I was getting at, some emulators have automatic server list that show user count and such. So you would have an 'active' list of login servers that you know are up.

well that wouldnt be hard to make at all wouldnt really be any different then making a page for account registration cept the server list page pings the ls listed in the database and shows if its up or down pretty simple php script to be honest

No heh...

I am not talking some shared login server, likely if everyone had their own login it would be individual user/passwords (that is an issue). But what im saying is each individual LS will try uplinking with a stats server and upload their current users/world information. Then a website can populate all that out.

Just to make it easy for the userbase to find reliable login servers and such.

I think if you gave people the option of autonomy (which obviously alot of people would like) from the "official" LS same as minilogin works now but with username and password authentication most people would still use the two public Loginservers, the only people that would change to the new improved minilogin would be people that either already use the currrent one or that are new users wanting a private server.

SoD has thier own login server and they are quite popular and autonomous they dont host anything on their ls but their own server and that is waht most people who want to use the minilogin option want i think.

that makes sense I personally wouldnt want to host any more world servers then my own so a minilogin with one world and a healthy ammount of user accounts allowed would be ideal for me and i think angelox as well.

I dont really want the responsibility of worrying about other peoples uptime if that makes sense

Maybe if there was more community involvement on this decision I would agree with it more but at this point its a small percentage voicing their opinion about public LS. There seems to be a few that want to keep it the way it is but ofcourse with a more reliable central LS.

But I am not sure I totally agree this should be the decision of the elite either... just saying.

Well most people have always used the public LS is the wayi understand it. Some prefer minilogin but im thinking that the people that use minilogin dont spend much time on the forums unless they are having a problem with it

Personally I dont see what their issue is with you releasing a decent updated minilogin personally I mean having done some googling it was yours to do with what you wish anyway originally. Even with unlimited accounts and 3 world servers its not like they would have to worry about competition from the general end user.

Like i said I think if you limit the world accounts to one only for minilogin then that should satisfy everyone, you have a new public LS opion up for the public ls users, and a good secure minilogin option for the minilogin users

But you are right It shouldnt be an elitist decision either

I'm with Angelox that an account-based (rather than IP-based) minilogin would be a great boon for the minilogin users. I don't think that's the part of the design that's causing the consternation though, right?

It's the effect of federating the servers and the potential problem of duplicate account names, right?

Clarification
 

Well, I'm trying to set up the minilogin, and think I've figured out the readme file so far; but I have a question about two instructions:
I set the user_active field at 1, but I'm not sure just what specifically I need to put for the name and password. Are the above settings ('username' for name and md5("yourpassword") for password) literal strings to be entered into these fields, or do they represent variables? In other words, do I replace 'username' with my own username and md5("yourpassword") with my own password, or do I type these lines in as literal strings into the db? My guess is that these are variables, but "md5" just seems like a strange way to note a variable.

Also . . .
Same question as before. Is 'accountname' my account, or is it a literal string of characters to be entered into the db? Same question for 'Public Name'.

I appreciate any help with this.

you set them to whatever you want them to be they are not variables user_active must be set to 2 or you cant login makle sure you ONLY Change yourpassword to what you want the password to be DO NOT REMOVE md5("") that is the encryption of the password and MUST Be there

insert into login_accounts set name='username',password=md5("yourpassword"),user_ active=1;

Replace username with the name you want your account to be.
Replace yourpassword with the password you want to use, md5 is an encryption technique.
The user_active field makes sure you can login, if it is 0, it will not let you.

insert into login_worldservers set account='accountname',password='yourpassword',name ='Public Name';
Replace accountname with a account you will use in your eqemu_config.xml under <account>
Replace your password with an account password which will also be reflected in the eqemu_config.xml
The contents of name do not matter as far as I remember, this just needs to have something there.

Thanks for the help. I see there is some conflict in the information. Is it user_active=2 (per Aergad), or user_active=1 (per the readme file)?

Any value that is not 0 should make the user active, but in reality it should be 1.

Thanks again. One more clarification. You wrote:

"Replace accountname with a account you will use in your eqemu_config.xml under <account>"

Here is the contents of my eqemu_config.xml (names and password have been changed). Which piece of information are you calling the "accountname"? Is it the shortname, the username, something else?

it should look something like

Do I need to change my host or port settings? I noticed they are different from yours.

well yeah tailor it how you need to but itll work if you set what i posted up properly

Hmm . . . not working.

On the start.bat I'm getting "[world_LS_ERR] Unable to resolve 'loginserver' to an IP."

On the minilogin.exe, I'm getting "Error in LoadWorldList query 'Select ID, account, name, admin_id, greenname from login_worldservers where showdown=1' #1146: Table 'peq.login_worldservers' doesn't exist."

Also, minilogin.exe is reporting lots of missing Opcodes from patch_6.2 conf, patch_Titanium.conf, patch_Anniversary.conf, patch_Live.conf, and error importing functions from EQCrypto.dll.

I'm certain I have something wrong here.

you have to make the table and you need to set loginserver to either the actual hostname (like eqemulator.net) or the ip of your loginserver ignore the errors about the conf and make sure you DONT put the loginserver in the same folder as the emu server files/ check the readme and all your settings in eqemu_config.xml

I'm using the readme file for the NewMiniLogin; to wit:
As far as I can tell, I have followed this to the letter. I would love to use yours, Angelox, but I can't have my db overwritten (any chance of separating out the minilogin by itself?).

Aergad wrote: "you have to make the table . . . "

The login_worldservers table does exist, but not under the peq db (as the error message indicates). The readme file says to create a "new" db, so that's what I did (I named the db "minilogin"). It is a separate db from my "peq" db, and it does contain the table in question. Did I misinterpret something? Is there a setting that is wrong? Do I need to point something in a different direction?

Aergad wrote: " . . . and you need to set loginserver to either the actual hostname (like eqemulator.net) or the ip of your loginserver"

Where exactly do I set this? There seems to be no place in the table to set this. Is this in the eqemu_config.xml file?

Aergad wrote: "make sure you DONT put the loginserver in the same folder as the emu server files"

They are in separate folders.

Aergad wrote: "check the readme and all your settings in eqemu_config.xml"

I thought I did all that.

Okay, I changed the default host in the db.ini to localhost, and now the error message is CheckWorldVerAuth . . . Table 'peq.login_versions' doesn't exist. I cannot find that table in either my peq db nor in my minilogin db.

Also World.exe is reporting, Could not connect to login server: TCPConnection::connect<>: connect<> failed. Error: 10061

I am not familiar with the PEQ database really, but you still need the tables included with the mini-login release. The CheckWorldVerAuth is because you have some database flag for MiniLogin, this is a regular Login Server. I think that was explained previously.

I created the minilogin db from the supplied .sql file in the NewMiniLogin folder, per the instructions in the readme file. After creation, I found that (my version of) the minilogin db contains four tables: login_accounts, login_authchange, login_worldservers, and variables. Are there supposed to be others?

Quoting previous post.

So, no change in the variables table from public to minilogin? I must have missed that one.

EDIT:

Ah, my bad.

I changed it back to Public. Here's the latest:

1. World.exe reporting [WORLD__LS_ERR] Could not connect to login server: TCPConnection::Connect<>: connect<> failed. Error: 10061

2. EQLaunch.exe reporting Connected to World: Localhost:9000

3. Minilogin.exe reporting . . .
Server mode: Standalone.
Login server listening on port:5999
here10!
Unknown LoginSOPcode: 0x3002 size:33

This is followed by what appears to be some sort of hash table for 0, 16 % 32.

Once Minilogin.exe is launched, World.exe reports "connected to loginserver: localhost:5999"

No login screen actually appears.

eqemu_config.xml what do you have for the login server.

image:

<!-- Loginserver information. -->
<loginserver>
<host>localhost</host>
<port>5999</port>
<account>root</account>
<password>root</password>
</loginserver>

Ehh im not so sure localhost is good to use... try 127.0.0.1

Not sure if this was intended for this post, but I did send you a PM a while ago Angelox.