Erid

Yeah, great news!, I don't know why, but this made me very happy, it always annoyed me having to use set.

I'm guessing you mean r15521 =P I like how the explanation is well detailed in mob_item_ratio.txt

I haven't try it, but I must say I really like the way you're showing your script in this post, and I love how the code looks, I'll use it as an example every time I'm gonna script something. Great work and thanks for sharing.

It could be that there's a "," missing, it should be "commands: 0,0".

I like the idea, but working how xazax said.

I think it's ok to use Athena, it was the original. Interesting picture, I had never seen it. We could update the Wikipedia article to include rAthena, or is it too soon? Article: http://en.wikipedia.org/wiki/Emulator_(Ragnarok_Online)

I tried it out, it works for some .lub files, for example, jobname.lub gave me an error. It seems luadec does not work with the new 5.1 lua files neither (I don't now if the client use them anyways).

Yo veo que van avanzando bien, han ido arreglando bugs olvidados y parece que la comunidad tiene ánimos de mejorar esto, incluso veo bastantes de eAthena aquí. Otro detalle importante es que ahora la comunidad tiene más facilidad de ayudar, el equipo de desarrollo está más atento y crece constantemente, podemos ver entre los Core Developers ahora a Epoque y Protimus por ejemplo, se ve cambio y progreso. Ciertamente es un buen momento para empezar a programar para RO, de esta manera incluso podemos ayudar al futuro de rAthena, dado que el éxito depende de nosotros (la comunidad), cada uno tiene su manera, a veces basta con mantener el foro activo para motivar. P.D: Ademas se trata de trabajar la idea de que la administración no dependa de una persona, así evitar un incidente como ocurrió con Paradox.

I prefer rAthena, but I wouldn't bother to use RAthena, I just hope we stick with one =).

Jguy have some good points, I like the idea of having a nearest goal than kRO, it would help a lot to first reach iRO and then move on to kRO. Using kRO as a goal seems too far away and the lack of information doesn't help. I just hope we don't forget that our final goal is kRO.

It seems it would be good to wait since things are moving fast, I'll see in which way I could help, that's a good idea. Anyway I'll analyze every option and see how far rAthena is regarding in 3rd classes support, because I don't thing my friends mind them don't fully working, it's mainly to play and test. Thank you very much .

Ok, but where would I find something to base on, I'm almost sure I don't need to start from 0, since there is a lot being developed. For example, I download 3CeAM and look for the code of the renewal mechanics in rAthena, but which source files should I seek for?, I mean, there should be at least which ones are the ones that matter, something that could guide me. I don't expect to get everything held in a golden plate =S, I'm just looking for guidance, something that requires less time, I don't know if it would be better to use brAthena and re-translate the main NPCs for example (re-translate would be copy & paste the NPCs from rAthena, but I don't know if most of them match =/).

Thanks, then it means I should use 3CeAM from this repository: http://3ceam.googlecode.com/svn/trunk/rewrite/, but where is the renewal version of it?, sorry, I'm really outdated in all of this.

Hi, I have been a lot of time with just little updates about eAthena and RO in general, so I'm really lost in what's related to the new mechanics and 3rd class implementation in the current emulators. I'm interested in making a (mostly) test server for me and my friends to play around, nothing serious, but I would love to implement the new mechanics and 3rd classes, for what I've read 3CeAM supports 3rd classes but without the new mechanics, brAthena seems very good but everything is in Portuguese and eAthena is just very outdated. My main question would be: Which emulator or combination of emulator and patchs is best for implementing new mechanics and 3rd classes? and what are the implications in relation to maintainability of each one? Don't get me wrong, I'm looking forward for this new fork, it seems to be going on a very good path, for what I've seen it's improving a lot the code and documentation, but meanwhile I would like to know what could be a good option. I would appreciate your help and any bit of updated information you can give me, or even some advice in this regard. Thanks.