Magnetix

I think the thread can be found either eA forums or 3ceAM forums...

Glad it helped. And sorry for not being so specific.

Np, glad to help a fellow newbie..

Check your services and see if mysql instance is running... Start>Type Services>Open Services>Check for MySQL5 make sure it is set to run every startup..

Actually if things didn't go out of hand back in eathena, eathena would've become like the current rathena. but rathena is much better.. As for 3ceam, it can be merged since both forked from the same source. If rytech is going to decide to use rathena's sources as base for 3ceam, it will take some time. There is already a huge gap between eA and rA.

When you're playing on a same machine with your server, you should use 127.0.0.1 in clientinfo, else you won't be able to connect. Now if the machine is in the same network as the server use LAN/WAN, and for people who are outside your network, use WAN. In port forward, local IP should ALWAYS contain the LAN IP of the machine your server running.

It says here notice the date of your client and lub from the client provided.

LOL i think I know why... The map looks fantastic, unfortunately I dislike strong colors. O_O I wanted to try it out, hopefully you'll be able to tone down the colors for a bit.. *my eyes are stupid*

No,no. You got it wrong... For your local IP address, it is wrong to use your Router's Address.. It should be the IP of the machine itself... Open your command prompt and type ipconfig and then use the ip from IP Address. usually its 192.168.1.2 or 192.168.0.2 and btw try the configs I posted above.

Make sure the following has to be the same in date Client == Packetver == Lua/Lub

can you tell me your client version?

Yes you can do that. But be sure config is set to read SQL db. If not, then there will be no point of adding your mob_db to your schema.

Please use the following first and then tell us if this worked. conf/char_athena.conf login_ip: 127.0.0.1 char_ip: 127.0.0.1 conf/map_athena.conf char_ip: 127.0.0.1 map_ip: 127.0.0.1 conf/login_athena.conf // SQL account.sql.db_hostname: 127.0.0.1 account.sql.db_port: 3306 account.sql.db_username: <Your DB ID> account.sql.db_password: <Your DB Pass> account.sql.db_database: <Your DB> //account.sql.codepage: account.sql.case_sensitive: no account.sql.account_db: login //account.sql.accreg_db: global_reg_value search your clientinfo.xml and replace with these values <address>127.0.0.1</address> and see if everything will work as intended. IF it did work change these values. conf/char_athena.conf login_ip: 127.0.0.1 char_ip: WAN IP/No-IP conf/map_athena.conf char_ip: 127.0.0.1 map_ip: WAN IP/No-IP Make sure after you do the port forward thingy, reboot your router PROPERLY else the changes will be undone and reverted back.

HKLM In windows it's HKEY_LOCAL_MACHINE is a db where your hardware/software data/configs/infos are stored/loaded. In Ragnarok, after setting up using setup.exe, those settings are saved in HKLM(default location), thus it becomes a global settings wherein whenever you load your RO client, those settings found on that db will be loaded. HKCU, is also the same with HKLM where data/configs/infors are stored/loaded but the difference will be the settings/configs will only become available when a certain user is logged on. If settings/configs are created by User A, then expect these settings/configs will always be available for User A and not for User B. There are actually 2 ways to fix this issue. -First, when you are running Windows Vista/7 make sure to run your program as an administrator. To do this right-click the executable file and select "Run as Administrator". -Second, use the old setup.exe or patched setup.exe.. For newer clients, use the new setup.exe provided when you downloaded/updated your kRO.

I suggest you wait until pRO launches their local map on their servers. When they do that, try to anticipate which patch would include them. If not, after patching look for those in their GRF.

Use the following: conf/char_athena.conf login_ip: 127.0.0.1 char_ip: 127.0.0.1 conf/map_athena.conf char_ip: 127.0.0.1 map_ip: 127.0.0.1 conf/login_athena.conf // SQL account.sql.db_hostname: 127.0.0.1 account.sql.db_port: 3306 account.sql.db_username: ragnarok account.sql.db_password: ragnarok account.sql.db_database: ragnarok //account.sql.codepage: account.sql.case_sensitive: no account.sql.account_db: login //account.sql.accreg_db: global_reg_value search your clientinfo.xml and replace with these values <address>127.0.0.1</address> <port>6900</port> make sure clientinfo.xml is found inside your data folder, not outside nor the other folders(if you have any) that are also found inside data folder.

Actually I don't call myself an expert on this matter. But what makes me successful is that I always use google to search for solutions and alternatives. Reading will help too. If all else fail and still haven't found any solutions, I ask the members of this community. I'll be willing to help you, just visit my profile for my contact detail..

So did my solution worked? or I failed?

are you able to reproduce this bug with the current revisions?

Copying entire src folder won't help. You'll never know if your current src folder contains most of the same codes with the revision you're about to compile. And check if 3CeAM supports newer packets.

Since all servers run on the same machine, just let them connect through each other locally. In port forwarding, your router takes the data off of an external ip and sends the data to whichever machine corresponds the targeted internal address and vice versa if data originated internally. So if the origin is already within your network, why the need of establishing connections through WAN? ughh.. nvm my explanation, just trying to remember my lessons..

rAthena seems pleasing to my eyes.. it's like kRO, iRO, pRO, jRO, etc And somehow it became like a custom, specially when forking.. (Specially after forking eAthena)

@KeiKun Will it be better if he'll duplicate the GM class and just modify the sprite that he'll use? Possible?