pada

Members
  • Content Count

    44
  • Joined

  • Feedback

    0%

Community Reputation

4 Neutral

About pada

  • Rank
    Vassal

Profile Information

  • Current Mood
    Joyful
  • Gender
    Not Telling
  • Country
    Japan

Recent Profile Visitors

1,340 profile views
  1. weird, with build zoned geo, and pathmaker 64 pathnode i get //viewpn results as such in game but for the most part, pathing seems to be fine, it just always bothered me that //viewpn was so broken, maby i am wrong about the packets not changing....
  2. Have you tried to build pathnodde with path64 for new clients and managed to //viewpn ingame? every time i have, //viewpn is massively screwed with lines/dots everywhere and massively broken, i am worried it is not actually building valid PN, as these primitive packets have not changed.
  3. i think Function User::GetDefaultExpDownValue Is what you are looking for
  4. I am pretty sure that the character count per server is what is contained in that second loop, though personally i have not bothered with a new Auth yet. i am pretty sure the loop is something like count of servers with characters, then a for each server, how many characters exist.
  5. They have IP connections because all logic is still done via packet send/recv, they just have a shared "data pool" to pull current information from, basically is how to look at it. but l2server/l2npc must be on same machine still
  6. No scripts have the concept of Geodata information besides the x y z locations, you would need to parse the actual conv.dat's to get more detailed Geo info without help from L2server
  7. It is most definitely not Java :)
  8. cdddddSdddddSSddddd is the response format, it should be opcode, unk, maxplayers, currentplayers, playing, privatestores, iobuffersize+uptime, currentnpccount, currentworldobjectcount, lastworldobjectcount, unk, unk ,builddate, buildtime, protocolversion, inspectorcrc, unk, unk, unk
  9. It should be something like 07 00 0E FF FF FF FD for the raw bytes sent, as you have to send packets size as well before opcode
  10. can just send a raw tcp packet to the L2Server with that opcode/-3, thats all. Some private servers block the packet, but any retail ncsoft server will respond
  11. Yes, 0x0E, with a version of -3 will respond with a packet of a bunch of info, logged in users, shops, server binary build dates, uptime petition info, ect. theres also a version you can send to crash the server with a special key if its enabled in l2server.ini :D
  12. VersionPacket with a parameter of -3 if i remember right, will send a response containing all of that information. Though it can be easily blocked/tampered with in the case of private servers running an extender :)