Ind

Gift'o! From Hercules, to your server!
We wish you happy holidays, and thank you for your support.
May the New Year bring you happiness and peace.
 
2013-12-23c Client Support
Thanks to Yommy and Rytech! NPC Market Support A new type of NPC Shop where item availability is limited, for example you can have a vender start with 50x Red Potions and set mechanics for the red potions to be refurbished (for example could be as simple as a OnClock, where Red Potions are refurbished every y hour, or elaborate e.g. be connected with a game quest where players need to help a merchant npc get to the shop in order for it to be resupplied) Available as a NPC Trader subset (details will follow) @costume Oktoberfest NPC Trader
A whole different way to set up shops, they're easier to read and flexible to customize. Previous format still supported (in the scenario we drop the previous we'll provide a conversion tool) To begin with, 'trader' is a phony name, its only purpose is to sign the parser that 'this npc will open the shop when clicked'. the trader npc is in fact a 'script' type (and thus script types can create/manipulate trader shops, and open them with the help of openshop()). Normal Zeny Shop moc_ruins,93,53,2    trader    Item Collector#moc1    4_M_03,{ OnInit:     sellitem Scell;     sellitem Monster's_Feed;     sellitem Animal's_Skin;     sellitem Bill_Of_Birds; } Custom Shop Script has full control over currency, which allows for scripts to use anything, from quests, to items, variables, etca. For Example: prontera,153,152,1    trader    TestCustom2    952,{ OnInit:     tradertype(NST_CUSTOM);     sellitem Red_Potion;     end;   /* allows currency to be Red_Potion */ OnCountFunds:     setcurrency(countitem(Red_Potion));     end;   /* receives @price (total cost) */ OnPayFunds:     if( countitem(Red_Potion) < @price )         end;     delitem Red_Potion,@price;     purchaseok();     end; } NPC Market ShopThis is the type I mentioned earlier, where item availability is limited prontera,150,160,6    trader    HaiMarket    952,{ OnInit:     tradertype(NST_MARKET);     sellitem Red_Potion,-1,50;     end;   OnClock0000://resupplies red potions on midnight OnMyResupply://instead of midnight, a event could trigger HaiMarket::OnMyResupply     if( shopcount(Red_Potion) < 50 )         sellitem Red_Potion,-1,50;     end; }The quantity data is disaster-safe, I mean it is persistent to @reloadscript and server restarts (If there were 39 Red Potions on sale upon restart/reloadscript, it continues to be 39 instead of resetting back to 50). 7 script commands to help control (documentation for all of them is present in script_commands.txt): openshop,sellitem,stopselling,setcurrency,tradertype,purchaseok,shopcount Trader Design by
Yommy Haru jaBote mkbu95 Gepard Emistry Ind Special Thanks To
Haru Yommy JaBote Muad_Dib Link'u~!
Commit: https://github.com/HerculesWS/Hercules/commit/cf19b26d50ac96111e44c33a80afd1f1ea935cec NPC Trader Samples: https://raw.github.com/herculesWS/Hercules/master/doc/sample/npc_trader_sample.txt (Upcoming) GM Interface for Cash Shop Control

Found that on the new client, support is being worked on (Data thanks to Yommy <3).

Thanks Yommy/Rytech <3.
I'm working my ass off to get a hercules christmas patch out before the 25th, including some secret things as well as the new features this client provides (market, new gm tool, oktoberfest costume, and more)!

Thanks Yommy/Rytech <3.
I'm working my ass off to get a hercules christmas patch out before the 25th, including some secret things as well as the new features this client provides (market, new gm tool, oktoberfest costume, and more)!

Thanks Yommy/Rytech <3.
I'm working my ass off to get a hercules christmas patch out before the 25th, including some secret things as well as the new features this client provides (market, new gm tool, oktoberfest costume, and more)!

Thanks Yommy/Rytech <3.
I'm working my ass off to get a hercules christmas patch out before the 25th, including some secret things as well as the new features this client provides (market, new gm tool, oktoberfest costume, and more)!

Here is my christmas gift to Hercules. I wish you all have an awesome holiday and nice time with family.
I have included an xdiff file, but I recommend (when he manage to fix the multiple grf) you to use NEMO Client Patcher made by Neo.

You need to add the PacketShuffle stuff into src/map/packets.h, just follow the files pattern,
then edit src/common/mmo.h and change the PACKETVER to 20131223
do a recompile and the client will be able to connect.


2013-12-23cRagexe_v2.zip 2.5 MB
https://mega.co.nz/#!Yt1DQSQC!TWk1AQU8sTXpP_t57Uowpne2-ZYSPhTB2_4WT55PFcY


2013-12-23cRagexe_v2.xdiff 102 KB
https://mega.co.nz/#!ogUUFLQJ!CPbCaX29tJLe_JOoeQd1oR24ug8WL83B0z_2T1XTXfQ


This is a very new client, and it will probably require resources from the latest kRO updates.
so kRO will need to be fully updated, i recommend to use RO Patcher Lite made by Ai4rei.


Special Thanks to Rytech and Ind


See you in 2014.
Yommy
 
Ps
Neo posted.an update here
http://herc.ws/board/topic/3609-2013-12-23c-kro-client-merry-christmas-3/?p=24183
 
Thank you
 
Ps:
Neo posted some update here 

Introducing Hercules' Channel System
Hello~! - What?!
1st, it is a replacement for the old @main 2nd, it is a super ultra mega improvement compared to the functionality @main provided. 3rd, whops. there is no 3rd. channels.conf format
    /* default channels (available on boot) */     default_channels: {         /* channel_name : channel_messages_color */          main: "Orange" /* available as #main */         support: "Blue" /* available as #support */         trade: "Red" /* available as #trade */         offtopic: "Cyan" /* available as #offtopic */         /* as many channels as you like */     }     /* colors available */     colors: {         Default: "0xffffff" /* custom channels will use the first in the list unless a font is selected thru @channel */         Red: "0xff0000"         Blue: "0x83cfe9"         Orange: "0xe57c00"         Cyan: "0x00b89d"         Yellow: "0xffff90"         Green: "0x28bf00"         Normal: "0x00ff00"         /* as many colors as you like */     }     /* allow users to create their own (private) channels through @channels command? */     /* (must also allow players to use @channels in groups.conf) */     allow_user_channel_creation: true     /* "map_local_channel" is a instanced channel unique to each map */     map_local_channel: true     map_local_channel_name: "map" /* available as #map */     map_local_channel_color: "Yellow"     map_local_channel_autojoin: true /* can disable autojoin in specific maps through mapflag or zone: nomapchannelautojoin */     /* "ally_channel" is a channel shared by all your guild allies */     ally_channel_enabled: true     ally_channel_name: "ally" /* available as #ally */     ally_channel_color: "Green"     ally_channel_autojoin: true Notes on the format/configuration
default_channels is the list of reboot-persistent channels, you can setup as many as you like and each can have its own color for chat, which you can specify in colors (again, you can setup as many as you like) map_local_channel is a feature that grants each map its own instanced channel (available, by default as #map -- which can be changed as per map_local_channel_name) map_local_channel_autojoin whether users will autojoin the local channel when they load a map with it enabled map_local_channel_autojoin can be disabled on selected maps (e.g. if you dont want it on gvg maps) through a mapflag (with a horribly long name D:) '<map name><tab>mapflag<tab>nomapchannelautojoin' ally_channel_enabled is a feature that grants a instanced channel for each guild's allies (as well as their own members), available by default as #ally -- which can be changed as per map_local_channel_name ally_channel_autojoin whether users will autojoin their respective ally chats upon login. New Commands Explained
@join Simple: @join <#channel_name>or, for password-protected rooms: @join <#channel_name> <password> @channel Does a number of things. Create a new channel (option available as long as allow_user_channel_creation is enabled) @channel create <#channel_name> <password> List public channels (groups with hchsys_admin can view private channels as well) @channel list Change a channel's color (requires to be owner of said channel or be in a group with hchsys_admin permission) @channel setcolor Samples available colors and displays their keys/names @channel list colors Leaves a specific channel @channel leave <#channel_name> Binds your global chat to a specific channel, making everything you type that'd normally be displayed to nearby characters be redirected to that channel instead @channel bindto <#channel_name> Unbinds your global chat from the current (if any) binded channel @channel unbind Bans a specific character from a channel @channel ban <#channel name> <character name> Lists all banned characters from a channel (groups with channel system admin permission can also see their account id) @channel banlist <#channel name> Unbans a specific character from a channel @channel unban <#channel name> <character name> Changes a channel's options (for now, channel message delay and announce-when-someone-joins) @channel setopt <#channel name> <option name> <option value> How to speak in a #channel
You can either bind a channel to your global chat (see @channel bindto above) or PM the channel you want to speak to, if you attempt to send a pm to a non-password protected channel that you have not joined, you'll autojoin. Other stuff
as I coded this feature I also improved overall guild processing/lookup, extremely, extremely faster (did I already say its ridiculously faster? WoE overhead probably more than halved with this). over a hundred lookups were replaced by a cached guild state that takes only 4~8 bytes per player. The commit also fixed a "wearing-garment-removed-costume-garment-look" bug - special thanks to jTynne for letting me know~! Groups with channel admin permission can bypass the channel message delay Special Thanks
to Streusel for proposing an idea that'd end up as the @channel bindto feature. to Frost for proposing the per-channel message delay limitation to Fatalis for proposing what'd end up as the @channel ban, @channel unban and @channel unbanall to Zopokx for proposing an improvement to how the map/local channels function Links~!
Commit Commit (update)

Obtaining Hercules
Hercules is available through GitHub, a web-based hosting service for software development projects that use the Git revision control system.
Obtaining Hercules through Git on Windows Obtaining Hercules through Git on Linux Git Troubleshooting

  Support
Looking for assistance on getting Git to work? Post here

Alternatively...
GitHub also provides a SVN Mirror. We won't officially work to support many branches or repository-features in SVN, but it should remain in-sync with the latest stable release, based on master branch in git.
Windows
You need to download TortoiseGit The address is http://github.com/HerculesWS/Hercules  
Linux
Typing the following creates a working copy of hercules at your home directory svn checkout http://github.com/HerculesWS/Hercules ~/Hercules  
 
 

Obtaining Hercules through Git on Windows
Downloads
Download and Install MSysGit Download the latest TortoiseGit

  Installation
Alright, first go through MSysGit installer and just set it up (its used as a base for TortoiseGit). then once you install MSysGit, launch the installer you just downloaded for TortoiseGit, you'll be prompted by a window similar to the following


The next window is "Choose SSH Client", select "TortoisePLink", hit Next.


The next window is "Custom Setup", do not change anything unless you know what you're doing, hit Next.


We're done with the installation, that was easy, wasn't it?


Obtaining Hercules
Go to the folder where you want Hercules to be placed, right click and select "Git Clone..."


in the URL field, type the following:
https://github.com/HerculesWS/Hercules.git ensure the 'Directory' field is as desired, and hit 'OK'


Now Hercules is being downloaded


Just wait for it to complete the download of your working copy and you'll be good to go.

Updating Hercules
Right-Click the folder where you downloaded your working copy and within the TortoiseGit menu, select "Pull..." as shown below


On the following window just hit 'OK', and your working copy will update.

Obtaining Hercules through Git on Linux
CentOS
Step 1: rpm -Uvh http://repo.webtatic.com/yum/centos/5/latest.rpm Step 2: yum install --enablerepo=webtatic git-all Step 3: yum install --enablerepo=webtatic --disableexcludes=main git-all  
Debian/Others
 
Step 1: apt-get install git  
 
 
Obtaining a Working-Copy
Type the following to create a Hercules working copy in your home (~) directory
git clone https://github.com/HerculesWS/Hercules.git ~/Hercules Updating a Working-Copy
Type the following when inside your working copy
git pull

Git Troubleshooting
Please, commit your changes or stash them before you can merge.Aborting.Git doesn't update modified files even if they don't conflict unless they're properly "committed" in your local working copy, to do so is simple and advantageous (it will keep a log of your changes for yourself; so you can always go back and check what was changed and when)
- On Unixgit commit -am "your log message, anything at all" - On Windows
1. Right click your folder -> Git Commit -> "master"
2. (optional) type the log message
3. Hit 'OK'

wooo. I forgot to update this =x. Through the data Yommy harvested on November 29th, my findings:
- The official ID ranges are dumb: mob/homun/merc/elem/skill-units share the 1-50k range (his script caps the range at 42k, thats wrong btw) aegis sucky design is able to maintain that, thus why officials run on so many servers, because the 50k range can be offset into multiple zones, on our design (thousand times better (and efficient), must I emphasise) it would limit the amount of such units (e.g. default settings have 47k mobs, by using the official range map servers would have little room for more or custom mobs, nevermind homuns/skill-units/etca)
- Thanks to yommy again I was able to determine no client functionality is lost by us using custom ranges, the game clients do not rely on the ranges (have not for many years), instead it relies on objecttype -- this is used to determine what a unit is, not by its id.
- Even though the ids are different, it doesn't mean the AI cannot be used (I was successful at getting it to work, with 6 edits, as I will demonstrate)
-- all files that follow are located in his ./AI/USER_AI, do not mistake it for those in the ./AI/ folder.
--- in AI_MAIN.lua
---- Find "if (v > MagicNumber2) then" change to "if (v >= MagicNumber2 and v <= MagicNumber3) then"
---- Find "if (v < MagicNumber) then" change to "if (v >= MagicNumber) then"
---- Find "elseif (v < MagicNumber) then" change to "elseif (v >= MagicNumber) then"
--- in AzzyUtil.lua
---- Find "if (m < MagicNumber) then" change to "if (m >= MagicNumber) then"
---- Find "elseif (id > MagicNumber2) then" change to "elseif (id >= MagicNumber2 and id <= MagicNumber3) then"
---- Find "if (id>MagicNumber2) then" change to "if (id>=MagicNumber2 and id <= MagicNumber3) then"
--- Lastly, in Defaults.lua
---- Find:
MagicNumber =42000MagicNumber2 =100000Replace the chunk with:MagicNumber =110000000MagicNumber2 =2000000MagicNumber3 =100000000- Special Thanks to Yommy, Haru.

wooo. I forgot to update this =x. Through the data Yommy harvested on November 29th, my findings:
- The official ID ranges are dumb: mob/homun/merc/elem/skill-units share the 1-50k range (his script caps the range at 42k, thats wrong btw) aegis sucky design is able to maintain that, thus why officials run on so many servers, because the 50k range can be offset into multiple zones, on our design (thousand times better (and efficient), must I emphasise) it would limit the amount of such units (e.g. default settings have 47k mobs, by using the official range map servers would have little room for more or custom mobs, nevermind homuns/skill-units/etca)
- Thanks to yommy again I was able to determine no client functionality is lost by us using custom ranges, the game clients do not rely on the ranges (have not for many years), instead it relies on objecttype -- this is used to determine what a unit is, not by its id.
- Even though the ids are different, it doesn't mean the AI cannot be used (I was successful at getting it to work, with 6 edits, as I will demonstrate)
-- all files that follow are located in his ./AI/USER_AI, do not mistake it for those in the ./AI/ folder.
--- in AI_MAIN.lua
---- Find "if (v > MagicNumber2) then" change to "if (v >= MagicNumber2 and v <= MagicNumber3) then"
---- Find "if (v < MagicNumber) then" change to "if (v >= MagicNumber) then"
---- Find "elseif (v < MagicNumber) then" change to "elseif (v >= MagicNumber) then"
--- in AzzyUtil.lua
---- Find "if (m < MagicNumber) then" change to "if (m >= MagicNumber) then"
---- Find "elseif (id > MagicNumber2) then" change to "elseif (id >= MagicNumber2 and id <= MagicNumber3) then"
---- Find "if (id>MagicNumber2) then" change to "if (id>=MagicNumber2 and id <= MagicNumber3) then"
--- Lastly, in Defaults.lua
---- Find:
MagicNumber =42000MagicNumber2 =100000Replace the chunk with:MagicNumber =110000000MagicNumber2 =2000000MagicNumber3 =100000000- Special Thanks to Yommy, Haru.

their will be a huge update this month

Slightly bigger soon I guess since theres a few updates.

Added:
[*]Added support for automatic concatenation of adjacent string literals (09dd209)
[*]Improved scripting operators precedence rules (ac6ae8c)
[*]Added support for ++x / --x operators and changed the x++ / x-- operators to post-increment (9a802b9)

(they were authored in September, but actually pushed in November, so they were accidentally skipped in the digest)

We're changing up the way we bring out our Digests from this point onwards. We'll typically toss out new month digests on either the 1st, 2nd, or 3rd of every month depending on how long Github takes to process the total number of commits given in the month (especially if theres a lot of commits done on the last day of the month (30th's and 31st's))

November Digest 2013
The following digest covers the month of November 1st - November 30th 2013.


Team Changes [*]Patskie has joined as a Community Contributor.
Development Highlights
[*]Changed built-in keywords, variables, labels, functions, commands, Aegis IDs, and mob sprite IDs to case-sensitive (49d2dff) (c6c2ad1) (6e9c385) [*]Introduction of "Contributors of Athena throughout the Ages" (eeafd81) (c069e2e) [*]Added support for Max EquipLv in Pre-Renewal (972caf2) [*]Added emblem blank pixels check (e095650) [*]Introducing Character Ban Support (aee2f63) (Blog) [*]Fix of atcommand aliases on certain commands (5739588) [*]Updated char server's response to offline map server (d77c011) [*]Fixed char server's maintenance mode (ee281a2) [*]Official expiration timer support (7120b55) [*]Removal of Emperium Spawn Restrictions (8ecffa8) [*]Added inheritance support for item_db2 (d3fe9bb) [*]Removed redundant item_db2_re.sql (59b9acb) [*]ItemDB Overhaul (ed72a94) (Topic) [*]HPM Custom Data Structure Makeover (8fda38d) (Requested) [*]Added rAthena to Hercules log database upgrade (938ac2d) (Topic) [*]Added rAthena to Hercules main database upgrade (54c2500) (8f28388) (044332d) (f0591e6) (be6440d) (Topic) [*]Fixed item chain drop rate processing (122c491) [*]Item Bind Fixes/Adjustments/Improvements (b9b32ac) (8083dae) [*]Fix of Equip Command (068d42e) [*]Modification of status_calc_ (6f77d07) [*]Introduction to Hercules' Standalone Script Syntax Checker (9700171) [*]Shadow System Fixes (84e4e6e)
Scripting Highlights
[*]Official Item BindOnEquip support (1f5161a) [*]Added deprecation messages for incorrect capitalization in scripts (dd05ae3) [*]Case Sensitivity (857bdc4) [*]Added support for automatic concatenation of adjacent string literals (09dd209) [*]Improved scripting operators precedence rules (ac6ae8c) [*]Added support for ++x / --x operators and changed the x++ / x-- operators to post-increment (9a802b9) [*]Added support for Mercenary/Homun Constants (63d5893) [*]Added support for Monster Constants (0b7b379) [*]Extended Script Constants to support NPC IDs (9f32aa9) [*]Overriding of @command loadings (778facb) [*]Standardized Formatting of NPC Parse error messages (7e68906) [*]Warp Duplicates no longer need a 'face' value (6728c0f)
Build System Highlights
[*]Fixed equip_level_max handling in the db sql converter (1064d8c) [*]Added support for 'make plugin.pluginname' to compile only 'pluginname' (98ad6bc) [*]Added support for case-sensitive jobmasks to the itemdb converter (e249264)  [*]Added item_db2.sql conversion script to new structure (9928044) [*]Updated db2sql plugin parse in server console (091e235) [*]HPM Support for Plugin-implemented (A bot that maintains .sql item dbs in sync with their counterparts) (1be53db) [*]Addition of Visual Studio 2013 (4078436) [*]Added _MSC_VER Checker (d7913a0) [*]Travis no longer builds plugins (fa07bc4)
NPC & Database Highlights
[*]Fixed case mismatches in BG (b1f4be7) [*]Cleaned up Zeny Manipulation (4faa0ec) (94ac9fe) [*]Added constant values for true and false (463cbc9) [*]Replaced hardcoded ItemIDs with constants (385e1e5) [*]BG Queue Update (eaf04b9) [*]Implementation of Correct Refinement Formulas (Above 10+) (6577a59)
FluxCP Branch Highlights
[*]Introduction of known Authors of FluxCP (3af11b7) [*]Compatibilized item module (f3eed0e) [*]Update of equip_locations (a55efb0) [*]Update of equip_location_combinations (822220ae)
November Statistics
[*]During the period there were 162 Commits. [*]Of these 162 commits, 35 included bug-fixes. [*]6 Commits from Pull Requests [*]In this month, there were 231,641 Additions and 67,709 Deletions.


November ended up being a successful month of fixing bugs compared to October, September, and August. The highest score of bug fixes was in June's Digest! Thank you to everyone who contributed to squashing these bugs!

Agradecimento especial ao mkbu95 por traduzir
(Jan 24th 0'13). Editado em (Mar 16th 0'16): corrigido formatação.


Enquanto nós tentamos não tornar o fórum uma prisão federal, há algumas regras que apreciaríamos que fossem seguidas à risca para tornar sua experiência no Hercules a melhor possível. Todos os membros são esperados a seguir estas regras ou punições variando de um alerta verbal, aumento da barra de alerta, restrição moderativa (um moderador terá que aprovar seus posts), suspensão de postar (poderá ver o fórum mas não postar ou criar tópicos) e suspensão do fórum (não pode ver o fórum nem postar) poderão ocorrer.
 
 
Orientações Gerais na Criação de Tópicos Tópicos não devem conter SPAM. Spam são posts de uma palavra, posts sem relação ao tópico, ou posts duplas/triplas sem motivo. Responder na seção incorreta também não será tolerado. Posts na seção Off Topic serão tratadas como exceção. Tópicos duplicados não são permitidos. Crie seu tópico uma única vez, na seção correta. Caso você crie um tópico acidentalmente na seção errada, use o botão Report para denunciar seu próprio tópico, nossos moderadores irão cuidar disto para você. Tópicos nas seções de suporte podem receber posts seguidos com maiores informações não menos do que 24 horas depois do seu último post; se você possuir novas informações em menos de 24 horas, edite seu tópico. Reviver tópicos mortos é proibido ao menos que haja algo construtivo para acrescentar ao tópico. Caso contrário, não o faça, afinal o tópico está morto por um motivo. Se um link estiver quebrado, envie uma Mensagem Pessoal (PM) ao membro que a enviou originalmente, não responda o tópico dizendo que 'o link está quebrado', pois será considerado spam.  
Assinaturas e Avatares
Assinaturas não devem exceder 650 píxeis em largura e 150 píxeis em altura no TOTAL. Isto inclui imagens e textos. Assinaturas não devem conter links para warez, esquemas para ganhar dinheiro, nudez ou qualquer coisa de caráter obsceno. Avatares não devem possuir natureza imprópria, e.x.: nudez ou qualquer coisa de caráter obsceno. Assinaturas e Avatares podem ser removidos por um moderador dependendo de seu conteúdo. Entenda que todas as regras do fórum também se aplicam a sua assinatura, seu avatar e seu título.  
Idiomas
O uso do inglês é obrigatório em qualquer seção em inglês. Caso tenha problemas em se comunicar em inglês, utilize a área internacional dedicada a um idioma de sua compreensão.  
Regras Gerais de Etiqueta do Fórum
Não faça respostas ou tópicos todo em maiusculo, nem use um número excessivo de emoticons, ou qualquer coisa que torne a leitura do tópico ou resposta difícil ou incômoda de ser realizada. Abuso de qualquer tipo não será tolerado. "Trollar" e "Flamear" outros usuários também não é permitido. Criar uma nova conta se a sua atual conta estiver banida não é permitido. Ao fazer isto a sua conta será banida instantaneamente. Links direcionando para pornografia, nudez, warez ou esquemas para ganhar dinheiro não são permitidos. Não faça o trabalho de um moderador se você não for um. Utilize o botão Report (disponível no canto inferior direito de cada resposta). Divulgação de qualquer tipo (exceto na seção de Divulgação e as seções de Divulgação das seções das áreas internacionais) é proibida. Pedir dinheiro (esmolar) via Mensagem Pessoal (PM) ou no fórum não será tolerada. Não edite seu post ou tópico para remover sua dúvida quando seu problema for resolvido.  
Área para Serviços Pagos
Novos tópicos na área Paid Services são invisíveis até que haja aprovação por um administrador.
Membros só poderão possuir assinaturas com serviços pagos ou tópicos e posts feitos no fórum caso o tópico seja aprovado na seção Paid Services. A seção Paid Services é para única e exclusiva divulgação de seus Serviços Pagos. Não faça divulgação de seu servidor (Ragnarok Online). Uma exceção será aberta caso você queira usar um link para um servidor como referência de trabalho (design que você criou, ferramentas, etc). Não se aplica a serviços de modificações na source; apenas use o referido código. Todos os Serviços Pagos sérios devem possuir HTTPS em partes sensíveis da webpage (incluindo, mas não limitado a: formulários que coletam senhas, informações pessoais, e informações de pagamento). Todos os provedores de hospedagem devem possuir um webpage onde os usuários possam requerir serviços de você. Se você estiver oferecendo modificações na source ou em scripts, ou serviços sítio/gráficos, o sítio é opcional.  
Que tipos de serviço são permitidos?
Hospedagem de Servidores (VPS, webhosting) Serviços de Modificações na Source ou em Scripts Serviços Gráficos (mapas, sprites, web design, etc.) Serviços de Programação de Sites  
 
Estas regras estão sujeitas à mudanças.
A quebra de uma regra irá levar a uma infração/alerta. Três infrações resultam em banimento temporário e cinco irão resultar em banimento permanente. Dependendo das circunstâncias, um banimento permanente pode ser dado a qualquer momento. Você pode apelar sobre qualquer ação tomada por um Moderador ou Moderador Global contra você por Mensagem Pessoal (PM). Você dever ter uma razão válida e um link para o que você está apelando. Não envie uma mensagem ao Moderador que realizou a ação contra você, é provável que você se involva em maiores problemas.  
As regras acima são enfasadas pela Equipe Hercules, respeite a Equipe e suas decisões.

Hercules Harmony Patch - 30 MAI
 
 
 
 
Made Possible Thanks to
 
Ind
Xgear
Haruna
 
 
 
 
 
This is a Diff Patch for the Latest Hercules Version ( Cloned for arround 30 Mins) ,   All Harmony Functions are working , and no server crashe etc.
 
I Only Provide a Diff file for the Harmon Version 3.3.12 .
 
This Diff only Contains the Harmony SRC Part .  you will have to add your own .BIN files from your harmony Package.
 
 
I WILL NOT PROVIDE ANY .BIN OR CLIENTSIDE FILES !!!!!!!!
 
 
 
Harmony_Full_3.3.12_V5.patch
 
 
 
 
the diff got tested on Linux / Mac and  WIN7/WIN8 with VS 2010 , no patch error or compiling error.

Implemented in https://github.com/HerculesWS/Hercules/commit/7120b55ce40a6a0c4086da49d57c74baa72609d6

Implemented in https://github.com/HerculesWS/Hercules/commit/7120b55ce40a6a0c4086da49d57c74baa72609d6

The provided converter is to transition from the old to the new format. It's already there.If you need to use the file for any other purpose I'd recommend you to look at the db2sql plugin code, and modify that to suit your needs. All the item db info is available there (including the default values for the missing fields), and you can change the fprintf format strings to suit your needs.
 
I am aware of that. But that's not an excuse for being stuck in the past with unreadable file formats. Tools can be easily edited and/or rewritten. Regular expressions are much harder to use (if not impossible), but that doesn't prevent you from writing a tool to convert the file to whatever format you find more suitable, and back to the libconfig format. The file in the repository is fine as it is, at least when it's updated, diffs are easier to read, and nobody can sneak in nasty, subtle changes that would pass unnoticed.Actually, it's been discussed since May 2013. 
Feel free to release one. I personally won't, as there's no need for it to be in the repository (other than making the Hercules database usable with other server emulators, which is outside our scope.) 
On a side note, the format has now new (optional) fields (see BindOnEquip). Those can't be converted to the "old" format, unless you add another field to it (but then it won't be the same old format anymore - that was one of its biggest weaknesses, it was impossible to add fields in a sane way without rewriting the entire file)
Yep. Hated the comma separated version (for anything other than machine parsing) since I saw it the first time. And as fields got added to it, it became harder and harder. 
 
There's a reason not to do that. We'd be back to a hard to read file format (the import scripts). I personally find it pointless to have the item db in SQL (other than for control panels and such), because, well, it's an info that gets read once on server startup, and cached in any case. SQL is useful if you only need to look up parts of it (like a control panel does), but quite pointless (and an annoyance to keep up to date) if all you need is to SELECT * on server startup.If one of the two formats were to go away, to me it'd be SQL. But it's gonna stay, mostly for Control Panel purposes.
You misunderstood the 'Inherit' point. Please re-read how it works.Inherit can only be used in the item_db2 to inherit the values defined in item_db for *the same item*. You can't have inheritance chains, as it's only a boolean. If your custom Knife[3] has 'Inherit: true' set, and you only define a script (i.e. because you want it to have 100 Atk instead of its standard value), it means it'll be exactly a Knife[3], with all other standard parameters from the item_db, and only the Atk you have overridden will be changed. This means that, if for some reason the official item is updated to have a different weight, you wouldn't need to edit yours, as the change will be propagated (unless you override it.)

Git Troubleshooting
Please, commit your changes or stash them before you can merge.Aborting.Git doesn't update modified files even if they don't conflict unless they're properly "committed" in your local working copy, to do so is simple and advantageous (it will keep a log of your changes for yourself; so you can always go back and check what was changed and when)
- On Unixgit commit -am "your log message, anything at all" - On Windows
1. Right click your folder -> Git Commit -> "master"
2. (optional) type the log message
3. Hit 'OK'

Obtaining Hercules through Git on Linux
CentOS
Step 1: rpm -Uvh http://repo.webtatic.com/yum/centos/5/latest.rpm Step 2: yum install --enablerepo=webtatic git-all Step 3: yum install --enablerepo=webtatic --disableexcludes=main git-all  
Debian/Others
 
Step 1: apt-get install git  
 
 
Obtaining a Working-Copy
Type the following to create a Hercules working copy in your home (~) directory
git clone https://github.com/HerculesWS/Hercules.git ~/Hercules Updating a Working-Copy
Type the following when inside your working copy
git pull

In case eAthena r15263 will be merged and the community has use for it, there's an excess add-on code, that has not and will not be committed to eAthena, due to it's nature of being a custom.
 
The patch allows to optionally reject completely transparent emblems as part of the emblem validation code. Transparent emblems are typically abused during WoE times to draw less attention in castles and were/are considered against the rules on some official and private RO servers.
 
Commented lines are an alternative approach for same effect, and may be removed.
 
patch