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;

Have you tried this one?
 
http://herc.ws/board/topic/902-instant-third-class-jobs/

I'm done with it, but I haven't tested.
 
Would like to release it, that's the reason of doing the script in a more general and configurable way than what you just asked.
 
Upaste mirror: http://upaste.me/fb7712684462cbaf3
 
//===== Hercules Script =======================================================//= Multiple droprate on mob elements from a set (default set: elements).//===== By: ===================================================================//= jaBote//===== Current Version: ======================================================//= 0.9.0 alpha//===== Changelog =============================================================//= 0.9.0 Initial version [jaBote]//===== Description: ==========================================================//= Implements multiple drop rates on mob sets that change each week.//===== Warning: ==============================================================//= -> addmonsterdrop/delmonsterdrop script commands don't work well with mobs//= that drop the same item more than once.//= -> Doesn't work well with @reloadscript and/or server restarts (it will//= reassign a new set).//===== Additional information: ===============================================//= Configurations are located from line 22 (OnInit label).//=============================================================================- script element_drops -1,{OnInit: // Configurations START. // Add in mob IDs on the place of the numbers setarray .set_0[0], 1001, 1002, 1004, 1005, 1007; // Neutral setarray .set_1[0], 1001, 1002, 1004, 1005, 1007; // Water setarray .set_2[0], 1001, 1002, 1004, 1005, 1007; // Earth setarray .set_3[0], 1001, 1002, 1004, 1005, 1007; // Fire setarray .set_4[0], 1001, 1002, 1004, 1005, 1007; // Wind setarray .set_5[0], 1001, 1002, 1004, 1005, 1007; // Poison setarray .set_6[0], 1001, 1002, 1004, 1005, 1007; // Holy setarray .set_7[0], 1001, 1002, 1004, 1005, 1007; // Shadow setarray .set_8[0], 1001, 1002, 1004, 1005, 1007; // Ghost setarray .set_9[0], 1001, 1002, 1004, 1005, 1007; // Undead // Set to the name of the type of each set of $@set_X // BEWARE! Number of set of this array MUST be the same than the total // amount of sets (which is quite obvious). This is VERY IMPORTANT. setarray .names$[0], "Neutral", "Water", "Earth", "Fire", "Wind", "Poison", "Holy", "Shadow", "Ghost", "Undead"; // Set to the multiplication rate of drops (should be >= 1) // Examples: 100 = x1 (useless); 200 = x2; 50 = x0.5 // Based on final drop rates after battle conf calculations. .multiplicator = 200; // Force change of element each week? (1 = Yes; 0 = No) .force_change = 1; // Text message. You can change or translate it if you want, but be careful // not to touch the %s since you'll screw the dynamic formatting .announce_format$ = "The element %s has been doubled for this week."; // Atcommand name you want to use for keeping your users informed .atcommand$ = "ddw"; // Configurations END. Don't touch unless you know what you're doing. // Bind an atcommand bindatcmd .atcommand$,strnpcinfo(3)+"::OnCommand"; // Get the amount of sets and use an impossible set .amount = getarraysize(.names$); .set = -1; // Let it fall through the OnMon0000: label to assign first set on server // startup (or reloadscript)OnMon0000: .@old_set = .set; // Force the change of set if required if (.force_change) { do { .set = rand(.amount); } while (.set == .@old_set); } else { .set = rand(.amount); } // Restore old drops and assign new ones... if set hasn't changed if (.@old_set != .set) { freeloop(1); // We could be needing it // Restoring old sets, just if there was an old set if (.@old_set >= 0) { .@old_set_size = getarraysize(getd( ".set_" + .@old_set)); for (.@i = 0; .@i < .@old_set_size; .@i++) { // This is pretty ugly, but there's no other mean to do this. .@mobid = getd( ".set_" + .@old_set + "[" + .@i + "]" ); .@drop_count = getd(".mobdrop_count_[" + .@i + "]"); for (.@j = 0; .@j <= .@drop_count; .@j++) { // We only have to restore previously saved originals .@drop_item = getd(".mobdrop_item_" + .@i + "[" + .@j + "]"); .@drop_rate = getd(".mobdrop_rate_" + .@i + "[" + .@j + "]"); // This updates monster drop back to original state addmonsterdrop(.@mobid, .@drop_item, .@drop_rate); } } } // Applying multiplicator to new set for (.@i = 0; .@i < getarraysize( getd( ".set_" + .set ) ); .@i++) { // Get original mob drops .@mobid = getd( ".set_" + .set + "[" + .@i + "]" ); getmobdrops(.@mobid); setd ".mobdrop_count_[" + .@i + "]", $@MobDrop_count; // We'll need it for (.@j = 0; .@j <= $@MobDrop_count; .@j++) { // We only have to save originals setd ".mobdrop_item_" + .@i + "[" + .@j + "]", $@MobDrop_item[.@i]; setd ".mobdrop_rate_" + .@i + "[" + .@j + "]", $@MobDrop_rate[.@i]; // Calculate new rate. If it gives a value out of bounds, // addmonsterdrop will then take care of capping it inbounds // along with a warning we can safely ignore. .@new_rate = ($@MobDrop_rate[.@i] * .multiplicator) / 100; // This updates monster drop item if the mob already drops it addmonsterdrop(.@mobid, $@MobDrop_item[.@i], .@new_rate); } } freeloop(0); } // Announce new set for everyone and finish. .@announce_text$ = sprintf(.announce_format$, .names$[.set]); announce .@announce_text$, bc_all|bc_blue; end;OnCommand: // Announce set just for yourself and finish. .@announce_text$ = sprintf(.announce_format$, .names$[.set]); announce .@announce_text$, bc_self|bc_blue; end;} Please test it and point any bugs or errors you can find on it.
 
P.S.: I've made an effort to make it extra readable so that anybody could modify it if they wanted.

And if your system claims you haven't dos2unix, yum install dos2unix

Rental items are supposed to be standalone equipments, this is why you're experiencing these issues.
 
Just look at what your inventory table is (or another table that manages items, actually):
CREATE TABLE IF NOT EXISTS `inventory` ( `id` int(11) unsigned NOT NULL auto_increment, `char_id` int(11) unsigned NOT NULL default '0', `nameid` int(11) unsigned NOT NULL default '0', `amount` int(11) unsigned NOT NULL default '0', `equip` int(11) unsigned NOT NULL default '0', `identify` smallint(6) NOT NULL default '0', `refine` tinyint(3) unsigned NOT NULL default '0', `attribute` tinyint(4) unsigned NOT NULL default '0', `card0` smallint(11) NOT NULL default '0', `card1` smallint(11) NOT NULL default '0', `card2` smallint(11) NOT NULL default '0', `card3` smallint(11) NOT NULL default '0', `expire_time` int(11) unsigned NOT NULL default '0', `favorite` tinyint(3) unsigned NOT NULL default '0', `bound` tinyint(1) unsigned NOT NULL default '0', `unique_id` bigint(20) unsigned NOT NULL default '0', PRIMARY KEY (`id`), KEY `char_id` (`char_id`)) ENGINE=MyISAM;  
nameid is the item ID# of that particular item and expire_time is the time at which the item expires. So, if you compound a card onto an item, all the entry information for the card is deleted and the equipment info is updated with the card inserted on its correct slot, making the expire_time of the card nowhere to be found, thus rendering it permanent.
 
A polite guess (not sure) is that if you rent slotted equipment and insert permanent cards on it, they should be lost once the rental time expires .
 
P.S.: This is not a script concern, moving to General support section .

I'm done with it, but I haven't tested.
 
Would like to release it, that's the reason of doing the script in a more general and configurable way than what you just asked.
 
Upaste mirror: http://upaste.me/fb7712684462cbaf3
 
//===== Hercules Script =======================================================//= Multiple droprate on mob elements from a set (default set: elements).//===== By: ===================================================================//= jaBote//===== Current Version: ======================================================//= 0.9.0 alpha//===== Changelog =============================================================//= 0.9.0 Initial version [jaBote]//===== Description: ==========================================================//= Implements multiple drop rates on mob sets that change each week.//===== Warning: ==============================================================//= -> addmonsterdrop/delmonsterdrop script commands don't work well with mobs//= that drop the same item more than once.//= -> Doesn't work well with @reloadscript and/or server restarts (it will//= reassign a new set).//===== Additional information: ===============================================//= Configurations are located from line 22 (OnInit label).//=============================================================================- script element_drops -1,{OnInit: // Configurations START. // Add in mob IDs on the place of the numbers setarray .set_0[0], 1001, 1002, 1004, 1005, 1007; // Neutral setarray .set_1[0], 1001, 1002, 1004, 1005, 1007; // Water setarray .set_2[0], 1001, 1002, 1004, 1005, 1007; // Earth setarray .set_3[0], 1001, 1002, 1004, 1005, 1007; // Fire setarray .set_4[0], 1001, 1002, 1004, 1005, 1007; // Wind setarray .set_5[0], 1001, 1002, 1004, 1005, 1007; // Poison setarray .set_6[0], 1001, 1002, 1004, 1005, 1007; // Holy setarray .set_7[0], 1001, 1002, 1004, 1005, 1007; // Shadow setarray .set_8[0], 1001, 1002, 1004, 1005, 1007; // Ghost setarray .set_9[0], 1001, 1002, 1004, 1005, 1007; // Undead // Set to the name of the type of each set of $@set_X // BEWARE! Number of set of this array MUST be the same than the total // amount of sets (which is quite obvious). This is VERY IMPORTANT. setarray .names$[0], "Neutral", "Water", "Earth", "Fire", "Wind", "Poison", "Holy", "Shadow", "Ghost", "Undead"; // Set to the multiplication rate of drops (should be >= 1) // Examples: 100 = x1 (useless); 200 = x2; 50 = x0.5 // Based on final drop rates after battle conf calculations. .multiplicator = 200; // Force change of element each week? (1 = Yes; 0 = No) .force_change = 1; // Text message. You can change or translate it if you want, but be careful // not to touch the %s since you'll screw the dynamic formatting .announce_format$ = "The element %s has been doubled for this week."; // Atcommand name you want to use for keeping your users informed .atcommand$ = "ddw"; // Configurations END. Don't touch unless you know what you're doing. // Bind an atcommand bindatcmd .atcommand$,strnpcinfo(3)+"::OnCommand"; // Get the amount of sets and use an impossible set .amount = getarraysize(.names$); .set = -1; // Let it fall through the OnMon0000: label to assign first set on server // startup (or reloadscript)OnMon0000: .@old_set = .set; // Force the change of set if required if (.force_change) { do { .set = rand(.amount); } while (.set == .@old_set); } else { .set = rand(.amount); } // Restore old drops and assign new ones... if set hasn't changed if (.@old_set != .set) { freeloop(1); // We could be needing it // Restoring old sets, just if there was an old set if (.@old_set >= 0) { .@old_set_size = getarraysize(getd( ".set_" + .@old_set)); for (.@i = 0; .@i < .@old_set_size; .@i++) { // This is pretty ugly, but there's no other mean to do this. .@mobid = getd( ".set_" + .@old_set + "[" + .@i + "]" ); .@drop_count = getd(".mobdrop_count_[" + .@i + "]"); for (.@j = 0; .@j <= .@drop_count; .@j++) { // We only have to restore previously saved originals .@drop_item = getd(".mobdrop_item_" + .@i + "[" + .@j + "]"); .@drop_rate = getd(".mobdrop_rate_" + .@i + "[" + .@j + "]"); // This updates monster drop back to original state addmonsterdrop(.@mobid, .@drop_item, .@drop_rate); } } } // Applying multiplicator to new set for (.@i = 0; .@i < getarraysize( getd( ".set_" + .set ) ); .@i++) { // Get original mob drops .@mobid = getd( ".set_" + .set + "[" + .@i + "]" ); getmobdrops(.@mobid); setd ".mobdrop_count_[" + .@i + "]", $@MobDrop_count; // We'll need it for (.@j = 0; .@j <= $@MobDrop_count; .@j++) { // We only have to save originals setd ".mobdrop_item_" + .@i + "[" + .@j + "]", $@MobDrop_item[.@i]; setd ".mobdrop_rate_" + .@i + "[" + .@j + "]", $@MobDrop_rate[.@i]; // Calculate new rate. If it gives a value out of bounds, // addmonsterdrop will then take care of capping it inbounds // along with a warning we can safely ignore. .@new_rate = ($@MobDrop_rate[.@i] * .multiplicator) / 100; // This updates monster drop item if the mob already drops it addmonsterdrop(.@mobid, $@MobDrop_item[.@i], .@new_rate); } } freeloop(0); } // Announce new set for everyone and finish. .@announce_text$ = sprintf(.announce_format$, .names$[.set]); announce .@announce_text$, bc_all|bc_blue; end;OnCommand: // Announce set just for yourself and finish. .@announce_text$ = sprintf(.announce_format$, .names$[.set]); announce .@announce_text$, bc_self|bc_blue; end;} Please test it and point any bugs or errors you can find on it.
 
P.S.: I've made an effort to make it extra readable so that anybody could modify it if they wanted.

It's quite simple.
 
Just compile in pre-renewal mode to ensure you've got pre-renewal mechanics, and disable any job npc you're not interested to have in your server on the npc/scripts_jobs.conf file.
 
Then, if you have a job changer NPC, ensure it won't change your players to any trascendent class. Trascendent and third jobs will still be available on the server, just via atcommands or if a script changes them to these classes (this happens on every current emulator), so you have to avoid the usage of these atcommands. No other script than a jobchanger or these specified in the file I linked should arbitrarily be able to change jobs, based on current Hercules version.

Just make your own item, and make sure its on use script is like this one:
.@addition = rand(20,50);#CASHPOINTS += .@addition;announce "You've earned " + .@addition + " Cash Points. Your current total is " + #CASHPOINTS + " Cash Points.", bc_self;  
 
 

Some SQL Query to help:
Delete atcommandlog and other logs older than 1 month: (2592000 = (60sec*60min*24hours*30days))
 
DELETE FROM `atcommandlog` WHERE UNIX_TIMESTAMP(`atcommand_date`)<(UNIX_TIMESTAMP(NOW())-2592000);DELETE FROM `picklog` WHERE UNIX_TIMESTAMP(`time`)<(UNIX_TIMESTAMP(NOW())-2592000);DELETE FROM `zenylog` WHERE UNIX_TIMESTAMP(`time`)<(UNIX_TIMESTAMP(NOW())-2592000);DELETE FROM `branchlog` WHERE UNIX_TIMESTAMP(`branch_date`)<(UNIX_TIMESTAMP(NOW())-2592000);DELETE FROM `mvplog` WHERE UNIX_TIMESTAMP(`mvp_date`)<(UNIX_TIMESTAMP(NOW())-2592000);DELETE FROM `npclog` WHERE UNIX_TIMESTAMP(`npc_date`)<(UNIX_TIMESTAMP(NOW())-2592000);DELETE FROM `chatlog` WHERE UNIX_TIMESTAMP(`time`)<(UNIX_TIMESTAMP(NOW())-2592000);DELETE FROM `loginlog` WHERE UNIX_TIMESTAMP(`time`)<(UNIX_TIMESTAMP(NOW())-2592000); 

One of the main things you'd have to know is that unlimited web hosting is a scam. 90% of hostings that are saying unlimited are lying because that isn't true (just imagine millions of clients buying cheap, unlimited web hostings and uploading all of their files just to have a backup, which would be rather silly). You should rather go for unmetered when looking for these. And trust me, you'd rather prefer to know your limits than having a hard limit (usually under a Fair Use clause in the Terms of Service) and not knowing where it is.
 
Just think, buying hard drives for your data is expensive and you may not know, but carriers charge data centers based on the amount of data traffic they consume. It's rather common to have unmetered data transfer on shared hostings (web hostings) since your host wants you to be able to serve your web to any legit who requests it (that's why it's common to find some terms of service in hosts that bans directly or indirectly making download sites on shared web hostings).
 
Now, if you want a paid web hosting, think what hard disk space you need. You won't usually need more than 10 GB unless you're running a massive site or using your space inefficiently. As I said, you usually won't have to mind about transfer, but if your transfer isn't on the unmetered side try to have it around the 100 GB mark to make it on a very safe mark (unless you're running sites with tons of visits).
 
Hope this helped you.

¿Podrías decirnos qué cliente usas al menos y qué error exacto sale aunque sea a través de una captura de pantalla?
 
Si ya el cliente es complicado de por sí y no depende en ninguna instancia de ningún emulador (Hercules o rAthena) sino son clientes de Gravity modificados, con tan poca información no podemos hacer absolutamente nada.
 
Un saludo.

Nunca fui bueno con los clientes, para estas cosas mi compañero en esta sección es mil veces mejor que yo.
 
Si el cliente no lanza un error específico, yo no puedo aconsejarte otra cosa que probar con una instalación limpia de RO. Puedes coger un cliente ya hecho de los que se ofrecen en esta página y tratar de probar si tu servidor funciona poniendo tu cliente (y todos los archivos necesarios para ejecutar tu servidor) sobre este.
 
Mejor aún, si utilizas items custom en tu cliente, verifica bien la sintaxis del archivo que maneja los items (creo que era System/itemInfo.lub o lua desde la carpeta de tu cliente) o intenta usar uno limpio (ojo con tus custom ya que esos sí te lanzarán error ahora). A ver si llegas a poder ver correctamente la descripción de los objetos.

Você já viu a solução proposta pelo próprio terminal?
 
Somente mude as proposto e deveria funcionar.

Sorry my Portuguese isn't fluent and had to lookup that word on a translator (I try to form the sentences myself).
 
If you don't mind me using English:
Console already tells you how to fox the errors, just see that it proposes you to use lowercase versions of the script commands that are giving problems. You should amend these according to what the console tells you, so that you'll make your script work again.
 
Blame the scripter inconsistently using camelcase script commands back at Cronus, that's not good practice.

Tentando usar Português de novo:
 
O caráter em vermelho é o ponto exato onde o emulador acha que o erro é.
 
Tudos os script commands deven ser em minúsculas. Mude "Rand" para "rand" e faça assim para tudos os script commands que tirem erros.

¡Buenas! A todo el mundo, aclaro que este usuario me preguntó lo mismo por mensaje privado, al cual contesté y le pedí amablemente que lo publicara porque así podríamos enriquecernos todos de la experiencia común. Su mensaje privado contenía algún dato más como el servidor que administraba, por lo que puede que parezca que este mensaje no responda del todo a la pregunta del tema cuando en efecto respondo su mensaje privado. Adjunto mi respuesta íntegra (salvo la postdata en que le pido que lo publique aquí) de tal forma que él mismo lo puede comprobar si quiere.

Aprovecho para reiterar dos cosas que ya se dicen en el propio mensaje:
-> Primero: que administrar servidores no es ninguna ciencia exacta. Supongo que todos sabremos de memoria el dicho: cada maestrillo tiene su librillo;
-> Y segundo: que es una opinión personal acerca de cómo se debería manejar un servidor. Supongo que siempre habrá otras formas de manejar un servidor, las cuales respeto siempre que entre sus prácticas no se encuentren enviar a usuarios a hacer SPAM a otros servidores y premiarles por ello, atacar a otros servidores cuando empiezan a ser un problema para ellos (que por desgracia los hay) o hacer uso de otras prácticas dudosas. Respecto a los ataques DoS, recuerdo que en España (no sé en otros países) hacer ataques DoS o acceder de forma no autorizada a sistemas informáticos está penado entre seis meses y dos años de cárcel.

Sin más, aquí va mi mensaje:
 
 Espero que esta respuesta haya podido ayudar a más personas aparte de al usuario darknis.

Hola.
 
Realmente no te recomendaría cambiarlo. He jugado en servidores que falseaban los datos así y no es nada difícil comprobar que te están mintiendo. Y no es nada difícil saber eso si el número de usuarios no concuerda en todos sitios o incluso notas como usuario dentro del propio servidor que la gente no está sin más e incluso podría ser contraproducente.
 
Mi experiencia personal (como usuario de un servidor que decidió hacer algo similar) es que los vas a decepcionar más aún que si realmente propones un servidor nuevo (o aceptable), con ideas y lo que es más importante: tener buena cabeza. Máxime cuando habrá usuarios que en cuanto tengan la más mínima sospecha se pararán a comprobarlo por cualquier método a su alcance y no vas a tener respuesta, y más aún cuando mantener una mentira así es mucho más complicado porque tiene muchos puntos débiles, de los cuales personalmente no conozco todos y que deberías comprobar uno por uno personalmente.
 
Ten en cuenta que no vas a falsear las estadísticas de visitantes de una web (que es sencillo, porque puedes decir que tienes 10.000 visitas únicas al día usando por ejemplo un contador que te provee tu hosting, que permite no dejar rastro de la propia web) en que el visitante es fundamentalmente pasivo (no hacen nada en su gran mayoría) sino que vas a falsear las estadísticas de usuarios de un servidor, en que cada usuario es un agente activo y vaya, yo no me creería que en un servidor haya 100 personas pero en Prontera solo se vean 4 personas a lo sumo. O que haya 100 personas y solo veas 20 en WoE.
 
Todo lo anterior por no hablar de una posible reacción entre los usuarios: Si el administrador ha estado mintiendo con el número de usuarios online, ¿qué motivos reales tiene un usuario para creer en una posible honradez del equipo del servidor?, lo que siempre ha sido uno de los más grandes puntos de duda de los usuarios. Lo cual podría incluso, quizá, arriesgar más aún la importante inversión que puedas hacer en el servidor.
 
No obstante (y para mi desgracia), esto no es un foro sobre ética, sino un foro de soporte. Si bien estoy capacitado a objetar de conciencia para asuntos así, prefiero que una vez te he advertido seas tú mismo quien decida. Nunca he modificado el char server, aunque tras echarle un ojo, tiene toda la pinta de que la información que se envía al usuario sobre el número de usuarios online una vez es capaz de iniciar sesión correctamente en el login server se encuentra en src/login/login.c, línea 1184:
WFIFOW(fd,47+n*32+26) = server[i].users; A partir de esa línea puedes intentar guiarte.

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.

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.

Isso não é um problema, somente funciona como os emuladores oficiais. Mas agora que o mencionou eu acho que o Hercules deveria ter uma configuraçao para isso. Em verdade, tudo castelo sem dono sempre estará em WoE desde o início do emulador até que alguém os reclame.
 
A minha soluçao para isso é desativar tudos os npcs do castelos que eu não vou usar e pronto, mas eu tenho vistas outras como reclamar tudos os castelos pelo Staff.
 
Para retirar os castelos conquistados voçê pode facer um script com comandos setcastledata para mudar de guilda proprietária ou pode facer @agitstart, que lançara WoE em tudos os castelos para que voçe poda conquistar Fadhgridh e Swanhild pelo o Staff. @agitend terminará tudas as WoEs lançadas por @agitstart, mas a ultima opçao é um pouco máis insegura.

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.

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.

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.

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.

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.