Which part of the login server is responsible for successful logins?

I compiled some old login server and inside the source code there are several cpp and header files. Such as login_packets.h, tcp_threads.cpp, dbcommands.cpp, etc.

Which file controls the actual login success part? I know it depends on the accounts in the DB but is there a way to just ignore the DB accounts and passwords so that it lets me log in with any random acc ID and pw?

@[Only registered and activated users can see links. Click Here To Register...]
@[Only registered and activated users can see links. Click Here To Register...]
@[Only registered and activated users can see links. Click Here To Register...]
@[Only registered and activated users can see links. Click Here To Register...]

Quote:

Originally Posted by annoyinglyUgly I compiled some old login server and inside the source code there are several cpp and header files. Such as login_packets.h, tcp_threads.cpp, dbcommands.cpp, etc. Which file controls the actual login success part? I know it depends on the accounts in the DB but is there a way to just ignore the DB accounts and passwords so that it lets me log in with any random acc ID and pw? @[Only registered and activated users can see links. Click Here To Register...] @[Only registered and activated users can see links. Click Here To Register...] @[Only registered and activated users can see links. Click Here To Register...] @[Only registered and activated users can see links. Click Here To Register...]

What do you want to do with Login Server?

Quote:

Originally Posted by annoyinglyUgly I compiled some old login server and inside the source code there are several cpp and header files. Such as login_packets.h, tcp_threads.cpp, dbcommands.cpp, etc. Which file controls the actual login success part? I know it depends on the accounts in the DB but is there a way to just ignore the DB accounts and passwords so that it lets me log in with any random acc ID and pw? @[Only registered and activated users can see links. Click Here To Register...] @[Only registered and activated users can see links. Click Here To Register...] @[Only registered and activated users can see links. Click Here To Register...] @[Only registered and activated users can see links. Click Here To Register...]

The rule is simple - you can't completely ignore the DB part unless you can mock the account/character object. It's probably easier to fix the DB connection instead. especially if you know the code quality by #indy from the client. I didn't look into the server source, though, it's just based on my other experiences.

Quote:

Originally Posted by ethbtc What do you want to do with Login Server?

I want to log in with the 2008 server files.([Only registered and activated users can see links. Click Here To Register...])

Quote:

Originally Posted by adek1994 The rule is simple - you can't completely ignore the DB part unless you can mock the account/character object. It's probably easier to fix the DB connection instead. especially if you know the code quality by #indy from the client. I didn't look into the server source, though, it's just based on my other experiences.

Indy coders had autism or something. When I try to log in it instantly says login failed and says the following in server console:

NDLogin console:
[Only registered and activated users can see links. Click Here To Register...]

DS_SERVER console:
[Only registered and activated users can see links. Click Here To Register...]

DS_SERVER source at line 122:
[Only registered and activated users can see links. Click Here To Register...]

NDLogin source "ComUDPPackets.h":
[Only registered and activated users can see links. Click Here To Register...]

Does this mean that some stored procedures are missing (MSSQL)? :confused:Or some tables are missing/bad? :(
@[Only registered and activated users can see links. Click Here To Register...] could you give some hints at least? please :((((( I've been trying to get this to work night and day... :(((((