Leaderboard

Hi, my name is Sebastian, im testing and playing with the Ragnarok Emulators since its a good tool for improve my skills in a bunch develop areas. I really hope improve my knowledge and why not, help the community. Grettings from Colombia.

Hello, everyone! I'm Lynx of SolaceRO. I'm sharing our old database that's worth 1 month of research and application. I used to own SorinRO back in 2016. It's at episode 6 when it died. In our database, we have corrected the mob stats, drop, and spawns. Please keep in mind that this is not 100% accurate to the official server. I have used the following references: Leaked Aegis files for RussiaRO and MalaysiaRO WoE and Juno Guidebook (based on PhilippineRO) Old emulators (Fusion, Vidar, Freya, jAthena, etc.) P.S. Use it at your own risk. Review the files before implementing. SorinRO EP5 Spawn & Mob_Db.zip

short answer: no, because client limitation!, or you can make mod by using vending system, google this word "Selling Refined Item by NPC as Vending List"

Hello just been an hour since i fix my izlude too, if you change your izlude map to the new one make it recognize by your server update everything you need not only GRF. if you are having trouble with your tiles that notwalkable and walkable . you are almost there man ! you already change the GRF and added your desire izlude map but you did not update in the server files . Update your map_cache using weemapcache 1. Open your server map_cache inside db/pre-re/map_cache or db/re/map_cache 2. Click the file button 3. Select your Updated izlude map rsw 4. Hit the button of save. 5. Copy the file created and paste it/use it to your server. 6. Restart your server. Note: Everything should be fine now, If this guide works dont forget to hit the solve button so other newbie will recognize it. Much Love Enjoy browsing rAthena.

Actually from re-reading I caught something....it kind of looks like your MySQL is actually refusing the connection almost....I'll do some digging and see what the true error means After a bit of searching I found this: "Server dropped an incorrect or too large packet. If mysqld gets a packet that is too large or incorrect, it assumes that something has gone wrong with the client and closes the connection. To fix, you can increase the maximal packet size limit “max_allowed_packet” in my.cnf file, eg. set max_allowed_packet = 128M, then sudo /etc/init.d/mysql restart." This may or may not be the issue but worth a try