ShadowX256
Members-
Posts
17 -
Credits
0 -
Joined
-
Last visited
-
Feedback
0%
Content Type
Articles
Profiles
Forums
Store
Everything posted by ShadowX256
-
Share Vanganth Source Code.
ShadowX256 replied to SourceCode's topic in Server Shares & Files [L2OFF]
Inside of the release folder there is a file called "KeyGenerator.exe", just run it and give it the Hardware Fingerprint and a name and it will print out a key. -
Discussion Vanganth IL with C4
ShadowX256 replied to rteshima's topic in Server Development Discussion [L2OFF]
Well, I just copied the Skills/Items/HTML from PP-C4. -
Discussion Vanganth IL with C4
ShadowX256 replied to rteshima's topic in Server Development Discussion [L2OFF]
https://github.com/LoanX/C4Extender It works, but I wouldn't use it for a live server. -
Share Vanganth Source Code.
ShadowX256 replied to SourceCode's topic in Server Shares & Files [L2OFF]
https://github.com/LoanX/VanganthExtender -
Help C4 Authentication
ShadowX256 replied to ShadowX256's question in Request Server Development Help [L2OFF]
It works fine for C4, haven't touched the sources for months but it used to work fine, the following things need to be fixed: - Admin char moviment (it kinda does a moonwalking non-stop) - PIN code These are the bugs I've encountered SO FAR. -
Help C4 Authentication
ShadowX256 replied to ShadowX256's question in Request Server Development Help [L2OFF]
Thanks a lot, man. At least it logins just fine now, :D. I Removed IOBufferExt, LoginDb, and Encryption from his Network Module. So far this is what I've got: 1 - Empty Account 2 - After Creating the Character Probably I'll have to fix the CharSelectInfo, UserInfo, CharInfo and many more. Also, this UserSocket error bothers me a bit. But thanks a lot. -
Hello guys, I have been trying to connect C4 client with Vanganth Extender, but so far I've encountered many problems with the authentication itself. The RequestAuthLogin packets seem so different between the C4 and Interlude. C4 Type:0x08 (RequestAuthLogin) Size: 31+2 Recive time: 12:50:22:189 0002 s LoginName: r??????i 0014 d PlayKey2: 840685313 (0x321BD701) 0018 d PlayKey1: 2003475301 (0x776A9B65) 001C d LoginKey1: -829202813 (0xCE935E83) Interlude Type:0x08 (RequestAuthLogin) Size: 31+2 Recive time: 12:54:47:618 0002 s LoginName: root 000C d PlayKey2: 1 (0x00000001) 0010 d PlayKey1: 2 (0x00000002) 0014 d LoginKey1: 1 (0x00000001) 0018 d LoginKey2: 165717765 (0x09E0A705) 001C d d: 1 (0x00000001) Also, the C4 gets a LoginFail packet. Type:0x14 (LoginFail) Size: 1+2 Recive time: 12:50:22:197
-
Help L2AuthD 40504
ShadowX256 replied to ShadowX256's question in Request Server Development Help [L2OFF]
Thanks a lot, it totally worked, you and Anarchy were very kind to help me with this. I wish luck for both of you. Please mark the problem solved, SOLUTION: link to lin2db instead of lin2comm, no idea why it asks for L2Conn. -
Help L2AuthD 40504
ShadowX256 replied to ShadowX256's question in Request Server Development Help [L2OFF]
Yeah, I just tried that. It asks for the l2comm dsn file, but still doesn't work. -
Help L2AuthD 40504
ShadowX256 replied to ShadowX256's question in Request Server Development Help [L2OFF]
I don't think so, removed everything from the 2008 Installation before installing the 2005 Express one. Here is a screenshot of the Configuration Manager. -
Help L2AuthD 40504
ShadowX256 replied to ShadowX256's question in Request Server Development Help [L2OFF]
The AuthD returns "Invalid object name 'server' ", but once I run SELECT * FROM [dbo].[server] on Management Studio it works just fine. About the dsn, I just checked it again and it seems okay to me. The dsn files are down below. lin2clancomm.dsn [ODBC] DRIVER=SQL Server UID=sa DATABASE=lin2clancomm WSID=STRIKEX APP=Microsoft® Windows® Operating System SERVER=STRIKEX\SQLEXPRESS lin2comm.dsn [ODBC] DRIVER=SQL Server UID=sa DATABASE=lin2comm WSID=STRIKEX APP=Microsoft® Windows® Operating System SERVER=STRIKEX\SQLEXPRESS lin2db.dsn [ODBC] DRIVER=SQL Server UID=sa DATABASE=lin2db WSID=STRIKEX APP=Microsoft® Windows® Operating System SERVER=STRIKEX\SQLEXPRESS lin2log.dsn [ODBC] DRIVER=SQL Server UID=sa DATABASE=lin2log WSID=STRIKEX APP=Microsoft® Windows® Operating System SERVER=STRIKEX\SQLEXPRESS lin2report.dsn [ODBC] DRIVER=SQL Server UID=sa DATABASE=lin2report WSID=STRIKEX APP=Microsoft® Windows® Operating System SERVER=STRIKEX\SQLEXPRESS lin2user.dsn [ODBC] DRIVER=SQL Server UID=sa DATABASE=lin2user WSID=STRIKEX APP=Microsoft® Windows® Operating System SERVER=STRIKEX\SQLEXPRESS lin2world.dsn [ODBC] DRIVER=SQL Server UID=sa DATABASE=lin2world WSID=STRIKEX APP=Microsoft® Windows® Operating System SERVER=STRIKEX\SQLEXPRESS -
Help L2AuthD 40504
ShadowX256 replied to ShadowX256's question in Request Server Development Help [L2OFF]
Just switched the Screenshot to a bigger one. And the L2AuthDError.txt is bloody empty. Where can I see the user's rights? By the way, I tried to run it with SQL Express 2005, but the same errors happen. -
-
Share Vanganth Source Code.
ShadowX256 replied to SourceCode's topic in Server Shares & Files [L2OFF]
Well, I had a lot of issues with this project as well, you have to make the changes in the source code in order to use it. 1 - Make sure you have installed the x64 compiler on VS2005 2 - Did you take care of all the things related to the License? -
Help Vanganth Extender with C4 656
ShadowX256 replied to ShadowX256's question in Request Server Development Help [L2OFF]
Well, I tried using those too, but the same thing happens. Trying to use Visual Studio debugger attached to l2.exe, L2Server returns nothing, there are no Errors once I get disconnected. -
Help Vanganth Extender with C4 656
ShadowX256 posted a question in Request Server Development Help [L2OFF]
Hello, just attached the CachedExt.dll and IlExt.dll to the C4 PP Release and it seems to be working great. But, once I try to log in the server it automatically disconnects me. Also, there are no signs of any error on the L2Server, therefore, is there any way to debug it? I think there must be something wrong with the Networking which must be changed to C4 method on the Extender's sources.