0.5.7 Minilogin, and LS release

[smogo]

Lot'sa people talking about LS and the stuff ... i've been working on a LS / minilogin for a while, so here it is. Many thanks to those who helped, both with information, sidework, and testing.


In the package you get source for both minilogin and regular login. Both should work on any network. Regular login would not work on Windows machines, as far as i tried.

It's designed for 0.5.7dr6 version. It could work with earlier versions too, though i did not test them. It requires some code changes to go with 0.5.8. Maybe i'll work on this, maybe not. So atm if you want so, start digging the code and just do it yourself.

In the package is a README file. You will read it, as it will avoid you 90% of troubles you could get in. The remaining 10% ... you're sol.

This is alpha developer release. No support

get it here

Have fun

[govtcheeze]

smogo, you complete me

/em races off to try this

[daeken_bb]

Very cool

Question, is the client-login protocol the same as the 5.8 clients?

[smogo]

Forgot to add (and did not include in the zip)
Regular version requires database with the followin tables :

-- MySQL dump 9.08
--
-- Host: localhost    Database: login
---------------------------------------------------------
-- Server version       4.0.15a

--
-- Table structure for table 'lslogin'
--

CREATE TABLE lslogin (
  id int(11) NOT NULL default '0',
  login varchar(30) default NULL,
  passwd varchar(30) default NULL,
  status tinyint(4) default '0'
) TYPE=MyISAM;

--
-- Table structure for table 'lsservers'
--

CREATE TABLE lsservers (
  socket tinyblob NOT NULL,
  category tinyint(4) NOT NULL default '0',
  alive datetime NOT NULL default '0000-00-00 00:00:00',
  handle varchar(100) NOT NULL default '',
  status int(11) NOT NULL default '0',
  zones int(11) NOT NULL default '0',
  clients int(11) NOT NULL default '0',
  url varchar(201) NOT NULL default '',
  name varchar(250) NOT NULL default '',
  version varchar(100) NOT NULL default '',
  protocol varchar(100) NOT NULL default '',
  type int(11) NOT NULL default '0',
  account varchar(100) default '',
  passwd varchar(15) default ''
) TYPE=MyISAM;

i strongly reocmmend you experiment with minilogin first, though

[Melwin]

Originally Posted by daeken_bb

Very cool

Question, is the client-login protocol the same as the 5.8 clients?

No.

[Cisyouc]

Im not able to run ls.pl. Every time I install a new module it says it requires I get a new one it needs.

[Elkay]

Hey,

I am trying to use minilogin and I am getting the following error when I click login from the login screen:

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

-->incoming
Client 192.168.1.1:1079 sent 14 bytes, message type : 0x01 retry count : 0x00
00 01 00 00 00 02 00 29 48 23 00 00 02 00
new client, sending reply to 192.168.1.1:1079
key is : 192.168.1.1:1079

-->incoming
Client 192.168.1.1:1079 sent 18 bytes, message type : 0x09 retry count : 0x00
00 09 00 00 01 00 01 00 00 00 00 00 00 00 00 00 04 00
opcode 1 , sequence id 0
key is : 192.168.1.1:1079

-->incoming
Client 192.168.1.1:1079 sent 4 bytes, message type : 0x15 retry count : 0x00
00 15 00 00
message type 0x15, packet # 0 received and acknowledged by client
key : 127.0.0.1:1470
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 1
key is : 192.168.1.1:1079

-->incoming
Use of uninitialized value in printf at client.pl line 60.
Client 192.168.1.1:1079 sent 2 bytes, message type : 0x06 retry count : 0x00
00 06
Attention !! unexpected packet
key : 127.0.0.1:1470
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 1
currently on :
server from 127.0.0.1:1470 : Elite Corral
client from 192.168.1.1:1079
key is : 192.168.1.1:1079

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

This keeps repeating until I close everything down, and the client freezes at connecting to login server until I terminate the process. I'm using the client that was live as of 9/6/04 (definitely pre-9/14). Any ideas? TIA.

[giulietta]

I can load mini-login
I can load world.exe
I can load 5 zones

all work perfect before client launch

I know my eqhost.txt is correctly labelled

that being said I will post anything needed to confirm or not confirm my problem as the case might be but this is what I thought helpfull right away... text from loginserver on client attempt

reading : 127.0.0.1 testing testing
setting 0 to id 591, testing / testing
udp server listening on port : 5996
tcp server listening on port : 5996
now to work ...
currently on :
new incomming server ...
key : 127.0.0.1:1663
key : 127.0.0.1:1663
opcode : 4096, length : 607
World protocol : 0.3.10
World version : 0.5.7-DR6
World account :
World name : dukemiesters
World key : 127.0.0.1:1663
World passwd :
World url : 127.0.0.1
World type : 0
World category : 34
key : 127.0.0.1:1663
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
key : 127.0.0.1:1663
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
currently on :
server from 127.0.0.1:1663 : dukemiesters
key : 127.0.0.1:1663
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x00
32 00 00 00 4c 2d 01 00 59 00 1d ffffff82 ffffff9a ffffffa9
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x01
32 00 00 01 4c 2d 01 00 59 00 ffffffbb fffffff5 ffffff91 1d
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x02
32 00 00 02 4c 2d 01 00 59 00 ffffff8a 1d ffffff8b ffffff80
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x03
32 00 00 03 4c 2d 01 00 59 00 2c 6a ffffff80 34
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x04
32 00 00 04 4c 2d 01 00 59 00 ffffffe9 ffffffcd ffffffbe ffffffba
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x05
32 00 00 05 4c 2d 01 00 59 00 4f ffffffba ffffffb5 0e
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x06
32 00 00 06 4c 2d 01 00 59 00 7e 52 ffffffaf ffffff93
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x07
32 00 00 07 4c 2d 01 00 59 00 ffffffd8 25 ffffffa4 27
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x08
32 00 00 08 4c 2d 01 00 59 00 2e 6d ffffffd4 ffffffce
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x09
32 00 00 09 4c 2d 01 00 59 00 ffffff88 1a ffffffdf 7a
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x0a
32 00 00 0a 4c 2d 01 00 59 00 ffffffb9 fffffff2 ffffffc5 ffffffe7
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x0b
32 00 00 0b 4c 2d 01 00 59 00 1f ffffff85 ffffffce 53
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x0c
32 00 00 0c 4c 2d 01 00 59 00 ffffffda 22 fffffff0 ffffffdd
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x0d
32 00 00 0d 4c 2d 01 00 59 00 7c 55 fffffffb 69
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x0e
32 00 00 0e 4c 2d 01 00 59 00 4d ffffffbd ffffffe1 fffffff4
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x0f
32 00 00 0f 4c 2d 01 00 59 00 ffffffeb ffffffca ffffffea 40
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x10
32 00 00 10 4c 2d 01 00 59 00 7a 5c 06 67
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x11
32 00 00 11 4c 2d 01 00 59 00 ffffffdc 2b 0d ffffffd3
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x12
32 00 00 12 4c 2d 01 00 59 00 ffffffed ffffffc3 17 4e
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x13
32 00 00 13 4c 2d 01 00 59 00 4b ffffffb4 1c fffffffa
Attention !! unexpected packet
key : 127.0.0.1:1663
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 5
currently on :
server from 127.0.0.1:1663 : dukemiesters
key : 127.0.0.1:1663
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 5


please assist

[daeken_bb]

Are you sure you're using the proper client revision?

[Cutter]

ok, i am using 5.7dr6
and using a client that logs into eqemu servers when i am online..

i tried minilogin.. and works great .. i login..
using dave davespassword

get to the part where you select a server..

see my server..
then the comes the part where it starts to load graphics blah blah..

well it dont get to that part.. and just goes back to login screen

btw what should my eqhost.txt say now?

im excited about using this... cause i was probably one of the lots thats been crying about it.. btw thank you so much

[Elkay]

Yes I get to server select just fine with eqemu loginserver.

[Cutter]

yes, i do also
so, waiting on response.. i know it works ... just gotta figure out what im doing wrong

[Elkay]

Also a quick FYI.. my patch date is around 9/6/04, definitely pre-9/14 but not sure if there was any other patching in between those dates.

[Cutter]

I dont think so... i read the readme file and the person he was talking to seemed to log right in no problem..

[killspree]

9/6/2004 date of live patch does NOT work with 5.7dr6, that's your problem if you're experiencing any with this minilogin, most likely.