jaBote

Find this line: announce strnpcinfo(1) +": Now playing '"+ .song$[.@option] +"' by "+ .artist$[.@option] +".", bc_map; and change to this: announce strnpcinfo(1) +": Now playing '"+ .song$[.@option] +"' by "+ .artist$[.@option] +" as requested by "+ strcharinfo(0) +".", bc_map;

setnpctimer script command doesn't want you to put a comma before the first argument setnpctimer <tick>{,"<NPC name>"};

In fact, I'd have abused the OnMinute00 label adding an else announce "blahblahblah" after the first if gets closed, so that no timers are needed and it's more efficient solution

You should actually give a chance to it, since it's more like a win-win situation. Only drawback is that it's possible (not sure) that item parsing will be few milliseconds slower, but gives lots of advantages worth to give a test in.

¿Más extenso en qué sentido? No estoy especialmente entendido en clientes, aunque si haces broadcast por scripting puedes probar esto: announce "<text>",<flag>{,<fontColor>{,<fontType>{,<fontSize>{,<fontAlign>{,<fontY>}}}}}; Por desgracia, no hay mucha documentación respecto a cómo funciona el parámetro fontSize. Si pretendes cambiar el tamaño general de los broadcast desde los @comandos, puedes intentar modificar toda llamada a las funciones clif->broadcast o intif->broadcast dentro del emulador, en src/map/atcommand.c a sus versiones con más parámetros (clif->broadcast2 e intif->broadcast2) y por supuesto añadir tú mismo el resto de los parámetros que requiere la función (puedes obtenerlos buscando la función clif_broadcast2 src/map/clif.c línea 5726; e intif_broadcast2 en src/map/intif.c línea 161). Aún así, se ha reportado que los últimos clientes no son capaces de mostrar texto de un tamaño diferente por defecto, por lo que no existe garantía de que aún así no funcione. Más que nada te ofrezco esto como ayuda y no una forma de editar el cliente porque para desgracia general, si el conocimiento sobre los clientes son limitados y relativamente pocas personas saben montar un cliente en condiciones con las herramientas que hay, las personas que hoy día siguen en el mundillo del RO y SABEN editar el cliente (haciendo ediciones propias, no usando un diff patcher para aplicar diffs sino creándolos ellos mismos) las puedo contar con los dedos de una mano y me sobra más de uno, y además ninguno es hispano. ¡Un saludo!

Server software has stopped reading that messy txt file for the new, more readable conf file. You should use the new format on your server if it runs an Hercules version newer than when the update was introduced. However, you can use this Dastgir tool to convert back to .txt and Haruna's converter to conf whenever you find it convenient.

When a value is zero, the variable is destroyed server-side. If you want to add a variable to an account, just insert a row. Just remember: account_id is the account ID of the player you want to give points to; key is the variable name (DO NOT FORGET ABOUT THE '#'!), in this case #KAFRAPOINTS or #CASHPOINTS; index is the index of the var. Leave to 0 by default since if you use any other, you should access to #var[index]; value is obvious, don't you think?

AFAIK, the game considers MvPs as these monsters which have mvp_exp on their mob_db entry. And don't know how is a mob considered miniboss, but I've believed to date it has to do with the "boss" mode on the mob DB: db/mob_db_mode_list.txt At least in src/map/battle.h, line 31... #define is_boss(bl) (status_get_mode(bl)&MD_BOSS) // Can refine later [Aru] Hope it helped, even if being off-topic.

Um pouco máis simple. Execute este trecho de código na main database: #Database: ragnarok#Table: loginlogCREATE TABLE `loginlog` ( `time` datetime NOT NULL default '0000-00-00 00:00:00', `ip` varchar(15) NOT NULL default '', `user` varchar(23) NOT NULL default '', `rcode` tinyint(4) NOT NULL default '0', `log` varchar(255) NOT NULL default '', INDEX (`ip`)) ENGINE=MyISAM ; P.S: Infelizmente, eu não sou bom em Português. Posso tentar de ajudar-le em Espanhol ou Inglês se prefere.

Estaba esperando a poder utilizar el emulador en casa y probar, aunque en casos de problemas en un emulador compilado y sin modificaciones que afecten al respecto, lo mejor que puedes hacer es abrir un bug report y especificar qué es necesario hacer para reproducirlo. Un saludo.

Use a SQL query. On cellphone so can't specify much. Try something like this on a backup: DELETE FROM char_acc_reg_str where name = "#minute" OR name = "#limit" Edit: got it totally wrong on cellphone, sorry!

Somente troque a loginglog tabela na log database para a main database.

Kaori, this is the same guy who made the bugreport . Spanish (and other things to say to topic starter). Bueno, esperemos a ver qué encuentran los desarrolladores con esto, creo que hemos provisto suficiente información como para que se entretengan un rato .

Hola. Esperaba a tener disponible un espacio de pruebas antes de responder a tu tema. Veo que has abierto un bug report, por lo que he respondido con lo que he encontrado aquí. Un saludo.

It's official, these are the extra stat points you're normally given when rebirthing. Since your starting job wasn't high novice, the 100 extra stat points have to be manually added.

Well, after some source investigation, it's done that way because you can't do much more in scripting, unles you make your reset NPC give that many status points again.

You can use bg_leave script command for both purposes. I'd need your script to know what you're doing since that is just a queuing system but can use more variables. If you're using Hercules queue system, you could easily queueremove that guy if needed.

Try to update Hercules first if possible? I remember having recently seen a commit related to carts ~16 minutes ago from the date of this post. Maybe it fixes your problem (or not).

Storage is loaded upon logging in and dynamically refreshed when accessing it and storing/retrieving items, so chances are you'll need to relog in order to get the changes you made on storage. That, or make a script command that automatically opens your storage (if possible), adds the items and closes it (player won't ever realise that the storage has been opened because of the speed of the operation).

Your version is supposed to be this one: - script Sample -1,{OnInit: set .Delay,3600; end;OnPCKillEvent: if( Delay < gettimetick(2) ){ getitem 7227,1; announce strcharinfo(0) +"Killed " + rid2name(killedrid) + " At The PVP Room",bc_blue|bc_all; if( .Delay ) set Delay,gettimetick(2) + .Delay;}end;}} Changing the @VAR to VAR (without prefixes) and leaving the previous .VARs without being touched, as I said. Further advices, not for any purpose but for best scripting practices. This won't make your script better but at least easier to read and understand, think that you could en up making 500-line scripts: -> Make all your variables lowercase.; -> Name your variables differently. Even if .Delay (NPC var) is different from Delay (permanent character var) on script engine, it'd be better to have a different name for them. Examples: -> .Delay to .npc_delay -> Delay to player_delay

You can't do it via current scripting capabilities. Best approach you can do via scripting is MANUALLY disabling the protection either for some seconds then it gets reapplied or until when you manually reapply it. P.S.: That OnWhisperGlobal label you've added is useless, I'd remove it along with its content and its respective end and curly.

I don't know what is its file name (hope somebody else will tell you, I can't), but try to replace it with a transparent (color 0xFF00FF) 1x1 px image and it should work.

You haven't changed your variables well. I told you to change all @Delay for Delay and you've changed one to .Delay and failed to change the other.

Not good on client side (dunno how many times I ever say this on a single week ) but last time it happened to me, it was because of a misconfiguration either in the other servers' IP at conf/char-server.conf and conf/map-server.conf. If you're setting it as a local test webserver, please try with their default values (commented) so that server will autodetect. You'll receive warning messages but that worked for me.

Creo recordar que en los servidores oficiales se produjo un cambio en el comportamiento de Dragon Breath, pero no estoy seguro de la versión que está implementada en Hercules ahora mismo. Tampoco he trabajado mucho con servidores Renewal, así que esta respuesta puede no ser del todo satisfactoria, porque por desgracia no soy especialista en determinar el comportamiento de una habilidad. Hay dos habilidades de Dragon Breath, la de fuego y la de agua. Ambas funcionan igual, tienen la misma fórmula de daño y la única distinción que se hace en el código fuente entre ellas es que simplemente causan dos estados alterados distintos. Lo poco que he visto de interés en el código fuente acerca de esa habilidad, es que es un daño de tipo Misc, al que además se le añaden los flags de que son daños de tipo weapon y ranged. Según he podido probar en el emulador (última versión), cualquier reducción sea a DemiHuman o a ataques de rango funcionan por igual, y todos los intentos de daño han acertado independientemente del flee del objetivo. Puedes pedirle al administrador de tu servidor que lo compruebe ya que es en parte (si no totalmente) su deber hacerlo si no tiene la última versión del emulador sin modificar, ya que puede que él mismo lo haya modificado y lo que yo te estoy comentando no tenga ninguna validez. Yo personalmente no tengo problemas en responder lo que ocurriría normalmente mientras tenga tiempo, aunque la línea lógica de soporte es que tras recibir las consultas sea tu administrador quien haga tales pruebas en un entorno propio a tal efecto y si ve comportamientos bug o hay problema, venga a preguntarnos a nosotros. ¡Un saludo!