Ind

Maki will be able to tell you how I can be spelling that, repeteadly, for over a week.

use them or you will have nightmares with ind screaming "THE SIGNATUREEEEEEEEEEEEEEEEEEES"

I've spawned my battering ram a few dozen times that day.

you can find some of the renewal supported listed here: SRC/map/config/#REMODE

(6:08:57 PM) ***Makizushi is dead now and cannot create topic OH REALLY? WHAT IS THIS THEN? AND WHERE IS MY THREAD D:<

I'm against, I'll post a quote from irc. [17:13:57] xazax: one of our goals was to provide as smooth switch from eA to rA as possible [17:16:53] xazax: and right now I can check the complete version history if each script file, not sure, if it will be still accessible after renaming [17:19:10] Ind: i agree with xazax 100%. this is a sorta cosmetic change with a implied inconvenience we have more important things to focus at, in my opinion.

Happy Holidays~!!

I vote for epoque's whops didn't notice gepard's one is like that. +1 gepard's =3

/me votes for DevilEvil to make a new one

should be fixed now, let me know if not.

haha the other day brian was wondering why nobody was reporting bugs with a version -- so this is where the bug behind it lies.

I used the old translation project for Lua and Data folder. Unfortunately the development of the project stopped. LINK We're picking up from where they stopped, we'll be providing up to date client data svn within the next few days

You shouldn't have gotten those errors if you used the data. The data I just linked you to contains all of the files you listed. Adding working third jobs to rAthena requires source edit..sorry can't help you with that. I don't mess around with the source. rAthena supports all 3.1x classes -- we'll get to 3.2 once we're done clearing up eAthena's flooded bug tracker -- we've sorted a few hundred reports since last week already.

ah i see now, well i don't have something like this ready, hopefully someone else who reads this does

for that you can conf/battle/client.conf aura_lv 9999 + @reloadbattleconf (or if you want it forever you dont need the @reloadbattleconf)

the "?" and "!" over the npc: *showevent <state>, <color>; Show a colored mark in the mini-map like "viewpoint" and an emotion on top of a NPC. This is used to indicate that a NPC has a quest or an event to certain player/s. state can be: 0 = disable ( Used to disable and remove the mark and the emotion from the NPC. ) 1 = exclamation emotion ( Used to show an important quest event to certain player. ) 2 = interrogation emotion ( Used to show an non-important quest event to certain player. ) Other value may cause client crashes. color can be: 0 = yellow 1 = orange 2 = green 3 = blue other values show a transparent mark in the mini-map.

what is it you want, server-wide, map-wide?

it breaks out of the loop when instance fails to attach, in that case .@i will be lower than 2 (because you are trying to attach 2 instances), and it deletes the whole instance set with instance_destroy

discussion thread for the bugreport:4249

I'd love to see a ro-chapter-organized list of features we have (and don't have) implemented

make sure your woe castles are flagged gvg and not pvp (emperium restrictions are only applied in gvg maps)

28

don't worry I did

Hello~!