Leaderboard

E - Script Collection Last Update : September 10, 2013 Refine Function SQL Mission Board Monster Marching Vendor Control Advanced Stylist Coin Exchanger Doppelganger Race Of The Day Limited Items Multi Currency Shop Random News GM Online List Link Broken E-Inquiry DotA Runes Flower Counting Game Class Restriction Chain Quest Build Manager Misc Scripts : Freebies Script Card Trader Gold Room [ Pick Gold ] Gold Room [ Guild Tax ] Map Restriction [ GM Based ] Daily Reward Monthly Reward Monster Spawner Monster Summoner with Last Summoned Display Players Stats & Equipments 3rd Job Item Giver Exchanger [ Cashpoint to Coins ] Exchanger [ Poring Coin - Zeny ] Exchanger [ Points to Tickets ] Exchanger [ Item to Item ] Exchanger [ Item to Item ] Exchanger [ Multi Item to 1 Item ] Party Match Auto Ban Over Stats Users Soul Link Buff Kill Players gain Cash Points Party Members All Get Items [ Snippet ] Message Board Stalker Class Skill Reproduce NPC Multiple Selection Quest [ Template ] In-Game Item Rewarder In-Game Points Rewarder Invasion Event Custom Item Rate Status Point Seller [ Snippet ] Anti Bot Security Script Anti Bot Script [ Code / Question ] Item Combo Restriction [ LHZ Card ] Drop Item Upon Death PVP Switcher + Announcer [ Guild Master ] Rotating Waitingroom Messages +10 Refiner [ Specific Items ] Random Rate Item Exchanger MVP Invasion Premium Users [ Boost Rates ] Display Cutin Image upon Login Custom Randomed Box Items Kick GM during WOE Custom Crafting NPC Restrict Same IP [ Certain Map ] Coloured Items Exchanger Guild Master Changer Party Team PK Match Gambling Game IRC Channel Crafting NPC Guild Storage Restriction Stage Game [ Version 4 ] Monster Wiki Event [ Version 3 ] Special Thank you for my Tutor : Notes : I am a bit lazy to write all those Script Descriptions, i do believe that all of you able to get how this script works. Anyway, i will still doing my best to write the Updated Changelog or informations about the script as detail as possible. All the Scripts above are uploaded to Pastebin . Abide the Following Rule : Scripts Error / Not Working , you have to Explain it in Details. ( Add in Images / Modified Scripts ) Do not SPAM / BUMP in my Topic. Do not ask for Support stuffs for other Scripts in this Topic. Link Down , then drop [ @Emistry ] a message. I Reserved the Right for NOT Answering your Posts if you did not abide my Topic's Rules. Keep This In Your Mind : All the Scripts i distribute here are NOT FOR COMMERCIAL USES . DO NOT remove my Credits if you are using part of the scripts to modify your own. DO NOT re-release the scripts in any form / way. If you ♥ these Scripts , Click on to Vote this Topic up. Or you may also click on at above the Topic

@Moofie91 it seem fine for me, my map-server didnt crash even though i try to answer using your way. anyway, updated script to avoid this kind of "answer" which exploit the event behaviours.

Usually, it's caused by the size of file / the huge number of lines (entries, characters, texts). That happens all on the first time you upload them. on the next time, you'll just do some upgrades, so it's fine.. I mean, upgrades will upgrade (modify the values) and / or add some values (will never be more than 50 at a time). To solve this, if you are using PMA, then copy some parts from the .sql and paste it on PMA's SQL box and execute it. do it several times.

I doubt the space in the beginning of the name for the query was intentional, but I'll look into a solution for a name query with a space in the beginning of the name (though honestly, players shouldn't be allowed to have spaces in the beginning of their name).

isn't it called iteminfo.lua lub? wait. this structure.. not thinking so, rA uses a table like on SQL and TXT. try to open excel, import data from text file, select item_db.txt (pre-re, re both are fine) and delimit with a comma (,) then you can see it looks like a table. (it is a table) If your question is: "Will rA modify the structure to be like this?" then,,, I don't know. you got to ask the developers. Probably, they would ask you "why?" because: For every entry, you will need to write [ { ], [ <tab> ], [ ID: ] , [ AegisName ], etc right? each character has a size that will be written. it may be small. but, what about if Ragnarok keep developing and add more items? then the item_db.txt will be soooooo large. This is the current rA's item_db.txt (mine, not sure if updated): *btw, usually a single <tab> is considered as 4 white spaces. May be read as [4 white spaces] or [\t] accordingly. conclusion: that structure will take up so many spaces.

yes

it's possible. But, I'm not sure how. /src/map/atcommand.c @reloadscript is located on line #3795. you can add some C commands to add the cashpoints. and the @cash operation is on line #8178

You'll have to convert all variable declarations to use the set command. This script works as intended for rAthena emulators.

If you're running rAthena, you should be able to simply load the script and execute the command. Make sure you run the SQL query as well; I just tested this again to ensure its functionality, and it works fine. Note that if you've previously loaded this script into your server with @loadnpc, you'll have to unload it before loading it again (@unloadnpc reward).

Load the script and initialise the settings; since you're using eAthena, You'll have to modify the code a bit. Add this to line 35: OnWhisperGlobal: The final result should look like this: Then, whisper anything to npc:reward to initialise the settings. Note that you will not see @reward in your @commands list, since it was created via script.

Okay then, you surely have your vision here. But then, how could you detect when an external application injects and hooks into your client exe? Do you have a way to secure your packets? Do you have some kind to counter a macro like the auto-pot? Or are you just checking for some window title checks? Sadly, but in my opinion, these kind of checks won't work at all.. Or are you trying to decrypt every client resource? I don't know what kind of method you have in mind, but maybe it will work if there's some support in this matter. Keep informing us for any news, don't let your project die like the others, okay?