Leaderboard

In 9744ba4 I made the first update to what will be a series of updates to our source to standardize and document all functions and other things that are deemed important for both developers and aspiring hackers. We hope this ends up being a tool to help the standard user figure out what the functions are doing. We've had Doxygen available on the site, but no one ever decided to standardize code for it, so it just became an outdated, unused, unhelpful tool. We are aiming to change that by making everything be pulled into Doxygen, once it gets updated and pointed to GIT. So let me post some of the basics here as far as what we, the Core Development team, have decided upon. All documentation should have proper grammar and be understandable to degree All functions shall have standardized documentation directly above the function header (see below and file) Documentation shall not be nothing but a credit (IE: // [Akinari]) All documented code shall follow these comment standards'///' Is a Doxygen comment for one line '///<' Used for variable declaration commenting '/** **/' Standard function documentation '//!' For TODO and FIXME '//' Regular comment not shown in Doxygen Over the course of the next few weeks/months that these files are being standardized, it is very likely those with modified source files will run into conflicts. I highly advise you stay aware of these changes and update according to your time constraints. In general we attempt to avoid major file changes, but standardization has been held off for far too long. Occasionally with these file changes we will also do some small optimizations and, while we do test the changes, please know that these can cause new bugs, so report these accordingly. With that being said, I will keep a record as to what files get completed here and update it accordingly. Thanks for your time and if you have any comments or questions, feel free to post. status.c [ 9744ba4 ] - There are a few notes and a function or two without documentation, but standardizing it is done unit.c [ bf7e8ea ] Doxygen link has been updated to: http://rathena.org/doxygen/

This? 501,Red_Potion,Red Potion,0,50,,70,,,,,0xFFFFFFFF,63,2,,,,,,{ atcommand "@monster 1871"; },{},{}

Well, in this case, all I can deduce from the src, is that it effectively makes it so players can kill one another in the specified cells. The names cell_pk & cell_pk_check are just that in themselves. Names. You can change those names to cell_pvp if you wished too. In fact, it is VERY easy to make custom cells, in rA, the only part that makes custom cells difficult, is whether or not those cells hold any real function. Keeping that in mind, I wrote a few scripts that uses custom cells to determine location, thus eliminating the use of OnTouch NPCs. It is quite effective. All in all, my suggestion is simply change out the word: pk and put your prefered word: pvp

That revision you pointed to has nothing in it. It's just some added (and commented) lines where they were starting to implement something. We already have our own version of VIP in the works and it's almost done, but because of the recent lack of activity, it needed to be updated and finalized. It's in testing phases now.

- script atcmd_example -1,{ OnInit: bindatcmd "question",strnpcinfo(3)+"::OnAtcommand"; .x_radius = 10; .y_radius = 10; .x_center = 150;// radius... center... no need explanation it's obvious .y_center = 150; end; OnAtcommand: do { .@x = rand( (.x_center-.x_radius), (.x_center+.x_radius) ); .@y = rand( (.y_center-.y_radius), (.y_center+.y_radius) ); .@loop++; if ( .@loop == 1000 ) { message strcharinfo(0), "Too much people. You must wait. Command failed."; end; } } while( getareausers( "prontera",.@x,.@y,.@x,.@y ) || !checkcell( "prontera",.@x,.@y,cell_chkpass ) ); warp "prontera",.@x,.@y; createchatroom( getcharid(3), "Question", "",5 ); sit; end; }

Implemented 99098c1 *bonus_script "<script code>",<duration>{,<flag>{,<type>{,<char_id>}}}; This command attachs script to player within specified 'duration' in second. flag: &1: Remove when dead &2: Removable by dispell &4: Removable by clearance [TODO] &8: Save script when player logout and continue when player login back type: 0 = Buff 1 = Debuff NOTE: - Cannot stack same bonus - Max. bonus_script for a player is 10 (pc.h MAX_PC_BONUS_SCRIPT) Example: - Apple gives you +5 Str bonus for 1 minute when it's consumed. 512,Apple,Apple,0,15,,20,,,,,0xFFFFFFFF,63,2,,,,,,{ bonus_script "{ bonus bStr,5; }",60; },{},{}