Euphy

Where?

As is, you can't do either.

It's in the Pre-Renewal folder.

What @United posted about is a config in conf/battle/skill.conf: // Dancing Weapon Switch // On official servers, a fix is in place that prevents the switching of weapons to cancel songs. // Default: yes dancing_weaponswitch_fix: yes

See: battleground system without waitingroom

Still, it's not doing much good to run this server-wide every 5 seconds, especially when 99% of people won't be running a timer at any given time. I wouldn't recommend using this as-is for highly-populated servers.

Sorry for the late reply, but both items are used in the official script.

This was taken care of in 2fe8140.

npc/re/merchants/ticket_refiner.txt

It would be cool if you spawned a permanent clone of the character to wander around in the jail, since I can't imagine that anyone would stay logged in for too long after dying. The best way I can think of achieving this is through storing all of the dead character data in a separate table (for persistence), then using something similar to mob_avail to summon and disguise un-attackable monsters as players (would require a bit of source modifications).

Why would you need to revive a Homunculus when you aren't an Alchemist?

[paste=523icup1gj1]

First, read doc/source_doc.txt for a general introduction. We also have Doxygen set up, and our developers are continuing to improve the documentation of rAthena's source code.

I don't see why it would be much easier to edit these in a database? None of the values get re-used by multiple NPCs, so there's little reason to store all of the items and success rates in an additional database (which would just be a waste of space).

It's in the repository. npc/custom/card_seller.txt

Given what KeyWorld posted -- that this isn't even possible client-side -- this is not worth implementing on the server end. If official clients happen to support this in the future, we can reconsider. Thank you all for your input.

March Digest 2014 The following digest covers the month of March, 2014. Development Team @Cydh has been moved to Community Contributors. Development Highlights Major updates: @Aleos had another terrific month of bug-squashing, fixing a large number of skill issues in particular. Rebellion skill updates. (dd67f9d) Updated quest system information icons. (5e02af2) Script command updates: Added 'questinfo' command and updated 'showevent' command. (5e02af2) Expanded 'countitem' and 'delitem' commands to cart and storage. (01c30bf) Removed 'getserverdef' command, replaced with a source function. (cad0a57) Statistics 7 authors have pushed 56 commits during this period. Thanks for submitting those pull requests! On master, 282 files have changed. There have been 6,053 additions and 4,533 deletions. My apologies for the delay; we've all been very busy lately, so thank you all for your patience.

1. Yes, cashshop is implemented for Ragexe clients (not RagexeRE). See db/re/item_cash_db.txt. 2. They're finished. Still some bugs, but the skills are all balanced. 3. Not a clue. There have been a ton of changes all-around, which you can read about in our Development News and monthly digests.

A better way to do this: OnPCStatCalcEvent: if (condition) { bonus bMaxHPrate,3; bonus bAtkRate,5; bonus bMatkRate,5; } end; 'OnPCStatCalcEvent' is a fairly new label that triggers each time a player's stats are recalculated.

See: http://www.eathena.ws/board/index.php?s=&showtopic=181741&view=findpost&p=1478950 In short, if you need a lot of variables, it's far safer to create a new SQL table for the data instead.

I'm referring to users' custom scripts. It was a pretty popular command.

It's one-handed.

By nature, you cannot retrieve passwords hashed with MD5. That said, you can attempt to retrieve them using some tools online, but you won't be able to find most reasonable passwords in those databases.

And then there's the issue of backwards compatibility. 'strmobinfo' is ancient. Is it worth breaking a ton of old scripts to save 30 lines of code?

doc/item_db.txt Type: ... 11 Usable with delayed consumption (intended for 'itemskill') Items using the 'itemskill' script command are consumed after selecting a target. Any other command will NOT consume the item.