Jump to content

aabarreto

Members
  • Content Count

    32
  • Joined

  • Last visited

Everything posted by aabarreto

  1. Hey ho! Thanks for the amazing job! But I'd like to point one thing and also ask for help. So, the file for hercules emulator has some issues, I had to git clone it and then copy+past the "import" folder from your file. Nooow, for my issue: I don't have a clean KRo client. I downloaded that file but only received the regular kro =-| What should I do? Edit: I figured out I should use the client of the other folder, the one I pasted, lol. Still, I couldn't connect... I don't know what's wrong since the message is in korean, buuut, I used the admin acc as told. Also, the map and char servers are ok, but the login server keeps like this: [Info]: Attempt to connect to login-server... [Status]: Connecting to 192.168.0.8:6900 [Info]: Pinging SQL server to keep connection alive... [Info]: Pinging SQL server to keep connection alive... [Info]: Pinging SQL server to keep connection alive... [Info]: Pinging SQL server to keep connection alive... [Warning]: Connection to Login Server lost. [Info]: Pinging SQL server to keep connection alive... [Info]: Attempt to connect to login-server... [Status]: Connecting to 192.168.0.8:6900 [Info]: Pinging SQL server to keep connection alive... [Info]: Pinging SQL server to keep connection alive... [Info]: Pinging SQL server to keep connection alive... [Info]: Pinging SQL server to keep connection alive... [Warning]: Connection to Login Server lost. [Info]: Attempt to connect to login-server... [Status]: Connecting to 192.168.0.8:6900 [Info]: Pinging SQL server to keep connection alive... [Info]: Pinging SQL server to keep connection alive... [Info]: Pinging SQL server to keep connection alive... [Info]: Pinging SQL server to keep connection alive... [Warning]: Connection to Login Server lost. [Info]: Attempt to connect to login-server... [Status]: Connecting to 192.168.0.8:6900 [Info]: Pinging SQL server to keep connection alive...
  2. Then I'll try everything again tomorrow...
  3. Thank you, but I ended up giving up on doing it myself and posted a freelancer job offer online in my region, lol If you or someone be interested in getting paid with brazilian poor money, please tell me, lol
  4. Ok, I gave it a try using xampp... And got a bunch of errors (it's written in Portuguese, but you may see the error codes) Now I'm trying to figure out what's going on... Ok, I managed to make it work... Now, another problem. I configured everything to port 3306, but xampp will only open while using port 3307, since the 3306 is already occupied... Any idea of how to solve it?
  5. The guide didn't say I needed to use phpmyadmin, so I just don't have it... I'll take a look on how to use it
  6. What should I do? The user isn't supposed to be "root", I guess, but "qwert", as in the files I edited...
  7. Good afternoon! I'm probably the worst dev-pretender out there... I really know close to nothing. I'm trying to run my own server following this guide: Now, for the problems: 1. In step 4 (4a and 4c) I'm not sure what I should do... Should I just copy the content from import-tmld into import and keep the other files, then just paste everything? 2. I did as stated above and soon before step 5 I tried to run the servers... But they don't., as you can see the in the image that follows. Anyway, I did everything exactly like told in the guide, making the exception for the doubt in the item "1" above. What am I doing wrong? In Hercules I have a different error... Also, all those are in red in Hercules: Those are my files in "import" folder from Hercules battle.conf char-server.conf inter-server.conf login-server.conf logs.conf map-server.conf msg_conf.txt script.conf socket.conf sql_connection.conf And those are all my files in "import" folder from rAthena. atcommands.yml battle_conf.txt char_conf.txt inter_conf.txt inter_server.yml log_conf.txt login_conf.txt map_conf.txt packet_conf.txt script_conf.txt
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.