Ind

Introducing Hercules' Stress Test Server
Hello~!
 
The "Stress" Part
Over 1.000 IndAI units (equivalent to +1k online players) will be in the server playing 24/7, farming, going to pvp, doing woe, playing battlegrounds, doing anything a player does, this will create a perfect scenario for us to debug and test Hercules.
 
The Development Benefits
We'll be able to keep track of performance usage 24/7, making us able to detect whenever a update increases a server's usage, allowing us to further optimise said update in order to take the processing down. With the AI characters doing stuff non-stop 24/7 we'll be able to identify and fix any crashes existent. Hercules will gain a super stability boost thanks to this. How to connect / Moving in and out
This is the fun part.
No new clients, and no sclient/clientinfo/blablabla edits will be required. get to the test server by typing '@hercules warp', test whatever you like, and go back to your server with '@hercules leave'. This technology *might* also be employed in the future by us to create hercules-hosted inter-server events.
 
Entirely Secure
The only data your server will pass to our test server upon warp is the name of the character (and maybe hairstyle vals).
The test server is unable to modify (or even access) any data on your server, it is entirely secure and damage-free.
 
Unique to Hercules
The ability to connect through your ordinary client will be made possible by our custom server hosted over at herc.ws, the code won't be made public.
 
Coming
I felt inspired to write about this feature, which is why this announce is out before the feature itself.
This is one of the features to be powered by our Hercules Plugin Manager and will be made public once the HPM implementation reaches the level capable of sustaining it.

FAQ
what if i dont want my players to go to the test server?@hercules is a command like any other, you can restrict access by groups.conf (by default only gms will be able to use it) what if i dont have a test server to use as a gateway to the hercules stress test server?we will also provide clients for those who don't have/want to use a server as the gateway

Flux Control Panel for Hercules
 
Flux CP is now officialy available for Hercules!
 
It is fully working with both pre-Renewal and Renewal Hercules servers. We will continue developing it, so it is always up-to-date and compatible with latest Hercules.
 
New theme
Hercules' Flux CP comes with a brand new theme. It's a grey-ish modern and clean HTML5 theme, called Emphaino.
It has a nice dropdown menu located on top of the screen, and a customizable footer area, where you can put some stuff that should be visible all the time (like links to social media, forums etc.).
 
A picture is worth a thousand words:



 
It's a HTML5 theme, so it requires a decent browser, or IE9+ (if you insist on using that).
 
Theme selection
Having two themes is great, but until now it was impossible to make use of them both. That's why theme selector has been added to both themes, so your users can pick whichever theme they like more.
 
Again, preview:

 
Extra credits
Authors of original FluxCP & FluxCP-rA. Authors of Emphaino theme (originally for Wordpress).

 
Download
Hercules' FluxCP Github repository: https://github.com/HerculesWS/FluxCP
 
Issues
Bug reports, questions and suggestions are all welcome directly on GitHub: https://github.com/HerculesWS/FluxCP/issues
 
Enjoy~

Ultimate Item DB Update
 
Overview
A very extensive item db update for renewal mode The Numbers: Over 6500 individual flag updates 212 newly added/enabled items Made Possible Thanks To: Muad_Dib for all the data Yommy for the help on the equip field Haru for the new upper masks and his ultimate parser skills that improved the quality of this update by many fold In the update
db/re/item_db (and thus sql-files/item_db_re.sql) over 6500 flag updates and 212 newly added/enabled items 16: Upper Third jobs (Trans)32: Baby Third jobs The AegisName field was updated in several entries to match the official ones The name field was also updated in several entries to match the client display files 2 New 'Upper' flags were added to accommodate many of the newly added items:Custom items in renewal mode will require to have these new flags if you wish these jobs to make use of such items db/re/item_packages update to match the newly added items db/re/item_groups update to match the newly added items A new error message in the item db parser that will display any duplicate AegisName fields that are conflicting (Thanks to Masao) Special Thanks
once again,
Muad_Dib, this update wouldn't exist if it weren't for all the data he provided us with Yommy, wouldn't have been able to properly update the equip flags if it weren't for the job data he provided me with Haru, for making it possible to polish this update so many times. Haru spent many hours debugging this update and writing tools to further enhance the quality of the update Link~u!
Commit Commit 2 (Follow up)Special Thanks to Yommy for bringing it to our attention and for providing the data for the follow up, and to Haru for help in validating the update

Ultimate Item DB Update
 
Overview
A very extensive item db update for renewal mode The Numbers: Over 6500 individual flag updates 212 newly added/enabled items Made Possible Thanks To: Muad_Dib for all the data Yommy for the help on the equip field Haru for the new upper masks and his ultimate parser skills that improved the quality of this update by many fold In the update
db/re/item_db (and thus sql-files/item_db_re.sql) over 6500 flag updates and 212 newly added/enabled items 16: Upper Third jobs (Trans)32: Baby Third jobs The AegisName field was updated in several entries to match the official ones The name field was also updated in several entries to match the client display files 2 New 'Upper' flags were added to accommodate many of the newly added items:Custom items in renewal mode will require to have these new flags if you wish these jobs to make use of such items db/re/item_packages update to match the newly added items db/re/item_groups update to match the newly added items A new error message in the item db parser that will display any duplicate AegisName fields that are conflicting (Thanks to Masao) Special Thanks
once again,
Muad_Dib, this update wouldn't exist if it weren't for all the data he provided us with Yommy, wouldn't have been able to properly update the equip flags if it weren't for the job data he provided me with Haru, for making it possible to polish this update so many times. Haru spent many hours debugging this update and writing tools to further enhance the quality of the update Link~u!
Commit Commit 2 (Follow up)Special Thanks to Yommy for bringing it to our attention and for providing the data for the follow up, and to Haru for help in validating the update

Ultimate Item DB Update
 
Overview
A very extensive item db update for renewal mode The Numbers: Over 6500 individual flag updates 212 newly added/enabled items Made Possible Thanks To: Muad_Dib for all the data Yommy for the help on the equip field Haru for the new upper masks and his ultimate parser skills that improved the quality of this update by many fold In the update
db/re/item_db (and thus sql-files/item_db_re.sql) over 6500 flag updates and 212 newly added/enabled items 16: Upper Third jobs (Trans)32: Baby Third jobs The AegisName field was updated in several entries to match the official ones The name field was also updated in several entries to match the client display files 2 New 'Upper' flags were added to accommodate many of the newly added items:Custom items in renewal mode will require to have these new flags if you wish these jobs to make use of such items db/re/item_packages update to match the newly added items db/re/item_groups update to match the newly added items A new error message in the item db parser that will display any duplicate AegisName fields that are conflicting (Thanks to Masao) Special Thanks
once again,
Muad_Dib, this update wouldn't exist if it weren't for all the data he provided us with Yommy, wouldn't have been able to properly update the equip flags if it weren't for the job data he provided me with Haru, for making it possible to polish this update so many times. Haru spent many hours debugging this update and writing tools to further enhance the quality of the update Link~u!
Commit Commit 2 (Follow up)Special Thanks to Yommy for bringing it to our attention and for providing the data for the follow up, and to Haru for help in validating the update

Ultimate Item DB Update
 
Overview
A very extensive item db update for renewal mode The Numbers: Over 6500 individual flag updates 212 newly added/enabled items Made Possible Thanks To: Muad_Dib for all the data Yommy for the help on the equip field Haru for the new upper masks and his ultimate parser skills that improved the quality of this update by many fold In the update
db/re/item_db (and thus sql-files/item_db_re.sql) over 6500 flag updates and 212 newly added/enabled items 16: Upper Third jobs (Trans)32: Baby Third jobs The AegisName field was updated in several entries to match the official ones The name field was also updated in several entries to match the client display files 2 New 'Upper' flags were added to accommodate many of the newly added items:Custom items in renewal mode will require to have these new flags if you wish these jobs to make use of such items db/re/item_packages update to match the newly added items db/re/item_groups update to match the newly added items A new error message in the item db parser that will display any duplicate AegisName fields that are conflicting (Thanks to Masao) Special Thanks
once again,
Muad_Dib, this update wouldn't exist if it weren't for all the data he provided us with Yommy, wouldn't have been able to properly update the equip flags if it weren't for the job data he provided me with Haru, for making it possible to polish this update so many times. Haru spent many hours debugging this update and writing tools to further enhance the quality of the update Link~u!
Commit Commit 2 (Follow up)Special Thanks to Yommy for bringing it to our attention and for providing the data for the follow up, and to Haru for help in validating the update

Ultimate Item DB Update
 
Overview
A very extensive item db update for renewal mode The Numbers: Over 6500 individual flag updates 212 newly added/enabled items Made Possible Thanks To: Muad_Dib for all the data Yommy for the help on the equip field Haru for the new upper masks and his ultimate parser skills that improved the quality of this update by many fold In the update
db/re/item_db (and thus sql-files/item_db_re.sql) over 6500 flag updates and 212 newly added/enabled items 16: Upper Third jobs (Trans)32: Baby Third jobs The AegisName field was updated in several entries to match the official ones The name field was also updated in several entries to match the client display files 2 New 'Upper' flags were added to accommodate many of the newly added items:Custom items in renewal mode will require to have these new flags if you wish these jobs to make use of such items db/re/item_packages update to match the newly added items db/re/item_groups update to match the newly added items A new error message in the item db parser that will display any duplicate AegisName fields that are conflicting (Thanks to Masao) Special Thanks
once again,
Muad_Dib, this update wouldn't exist if it weren't for all the data he provided us with Yommy, wouldn't have been able to properly update the equip flags if it weren't for the job data he provided me with Haru, for making it possible to polish this update so many times. Haru spent many hours debugging this update and writing tools to further enhance the quality of the update Link~u!
Commit Commit 2 (Follow up)Special Thanks to Yommy for bringing it to our attention and for providing the data for the follow up, and to Haru for help in validating the update

Ultimate Item DB Update
 
Overview
A very extensive item db update for renewal mode The Numbers: Over 6500 individual flag updates 212 newly added/enabled items Made Possible Thanks To: Muad_Dib for all the data Yommy for the help on the equip field Haru for the new upper masks and his ultimate parser skills that improved the quality of this update by many fold In the update
db/re/item_db (and thus sql-files/item_db_re.sql) over 6500 flag updates and 212 newly added/enabled items 16: Upper Third jobs (Trans)32: Baby Third jobs The AegisName field was updated in several entries to match the official ones The name field was also updated in several entries to match the client display files 2 New 'Upper' flags were added to accommodate many of the newly added items:Custom items in renewal mode will require to have these new flags if you wish these jobs to make use of such items db/re/item_packages update to match the newly added items db/re/item_groups update to match the newly added items A new error message in the item db parser that will display any duplicate AegisName fields that are conflicting (Thanks to Masao) Special Thanks
once again,
Muad_Dib, this update wouldn't exist if it weren't for all the data he provided us with Yommy, wouldn't have been able to properly update the equip flags if it weren't for the job data he provided me with Haru, for making it possible to polish this update so many times. Haru spent many hours debugging this update and writing tools to further enhance the quality of the update Link~u!
Commit Commit 2 (Follow up)Special Thanks to Yommy for bringing it to our attention and for providing the data for the follow up, and to Haru for help in validating the update

Ultimate Item DB Update
 
Overview
A very extensive item db update for renewal mode The Numbers: Over 6500 individual flag updates 212 newly added/enabled items Made Possible Thanks To: Muad_Dib for all the data Yommy for the help on the equip field Haru for the new upper masks and his ultimate parser skills that improved the quality of this update by many fold In the update
db/re/item_db (and thus sql-files/item_db_re.sql) over 6500 flag updates and 212 newly added/enabled items 16: Upper Third jobs (Trans)32: Baby Third jobs The AegisName field was updated in several entries to match the official ones The name field was also updated in several entries to match the client display files 2 New 'Upper' flags were added to accommodate many of the newly added items:Custom items in renewal mode will require to have these new flags if you wish these jobs to make use of such items db/re/item_packages update to match the newly added items db/re/item_groups update to match the newly added items A new error message in the item db parser that will display any duplicate AegisName fields that are conflicting (Thanks to Masao) Special Thanks
once again,
Muad_Dib, this update wouldn't exist if it weren't for all the data he provided us with Yommy, wouldn't have been able to properly update the equip flags if it weren't for the job data he provided me with Haru, for making it possible to polish this update so many times. Haru spent many hours debugging this update and writing tools to further enhance the quality of the update Link~u!
Commit Commit 2 (Follow up)Special Thanks to Yommy for bringing it to our attention and for providing the data for the follow up, and to Haru for help in validating the update

Ultimate Item DB Update
 
Overview
A very extensive item db update for renewal mode The Numbers: Over 6500 individual flag updates 212 newly added/enabled items Made Possible Thanks To: Muad_Dib for all the data Yommy for the help on the equip field Haru for the new upper masks and his ultimate parser skills that improved the quality of this update by many fold In the update
db/re/item_db (and thus sql-files/item_db_re.sql) over 6500 flag updates and 212 newly added/enabled items 16: Upper Third jobs (Trans)32: Baby Third jobs The AegisName field was updated in several entries to match the official ones The name field was also updated in several entries to match the client display files 2 New 'Upper' flags were added to accommodate many of the newly added items:Custom items in renewal mode will require to have these new flags if you wish these jobs to make use of such items db/re/item_packages update to match the newly added items db/re/item_groups update to match the newly added items A new error message in the item db parser that will display any duplicate AegisName fields that are conflicting (Thanks to Masao) Special Thanks
once again,
Muad_Dib, this update wouldn't exist if it weren't for all the data he provided us with Yommy, wouldn't have been able to properly update the equip flags if it weren't for the job data he provided me with Haru, for making it possible to polish this update so many times. Haru spent many hours debugging this update and writing tools to further enhance the quality of the update Link~u!
Commit Commit 2 (Follow up)Special Thanks to Yommy for bringing it to our attention and for providing the data for the follow up, and to Haru for help in validating the update

Ultimate Item DB Update
 
Overview
A very extensive item db update for renewal mode The Numbers: Over 6500 individual flag updates 212 newly added/enabled items Made Possible Thanks To: Muad_Dib for all the data Yommy for the help on the equip field Haru for the new upper masks and his ultimate parser skills that improved the quality of this update by many fold In the update
db/re/item_db (and thus sql-files/item_db_re.sql) over 6500 flag updates and 212 newly added/enabled items 16: Upper Third jobs (Trans)32: Baby Third jobs The AegisName field was updated in several entries to match the official ones The name field was also updated in several entries to match the client display files 2 New 'Upper' flags were added to accommodate many of the newly added items:Custom items in renewal mode will require to have these new flags if you wish these jobs to make use of such items db/re/item_packages update to match the newly added items db/re/item_groups update to match the newly added items A new error message in the item db parser that will display any duplicate AegisName fields that are conflicting (Thanks to Masao) Special Thanks
once again,
Muad_Dib, this update wouldn't exist if it weren't for all the data he provided us with Yommy, wouldn't have been able to properly update the equip flags if it weren't for the job data he provided me with Haru, for making it possible to polish this update so many times. Haru spent many hours debugging this update and writing tools to further enhance the quality of the update Link~u!
Commit Commit 2 (Follow up)Special Thanks to Yommy for bringing it to our attention and for providing the data for the follow up, and to Haru for help in validating the update

Ultimate Item DB Update
 
Overview
A very extensive item db update for renewal mode The Numbers: Over 6500 individual flag updates 212 newly added/enabled items Made Possible Thanks To: Muad_Dib for all the data Yommy for the help on the equip field Haru for the new upper masks and his ultimate parser skills that improved the quality of this update by many fold In the update
db/re/item_db (and thus sql-files/item_db_re.sql) over 6500 flag updates and 212 newly added/enabled items 16: Upper Third jobs (Trans)32: Baby Third jobs The AegisName field was updated in several entries to match the official ones The name field was also updated in several entries to match the client display files 2 New 'Upper' flags were added to accommodate many of the newly added items:Custom items in renewal mode will require to have these new flags if you wish these jobs to make use of such items db/re/item_packages update to match the newly added items db/re/item_groups update to match the newly added items A new error message in the item db parser that will display any duplicate AegisName fields that are conflicting (Thanks to Masao) Special Thanks
once again,
Muad_Dib, this update wouldn't exist if it weren't for all the data he provided us with Yommy, wouldn't have been able to properly update the equip flags if it weren't for the job data he provided me with Haru, for making it possible to polish this update so many times. Haru spent many hours debugging this update and writing tools to further enhance the quality of the update Link~u!
Commit Commit 2 (Follow up)Special Thanks to Yommy for bringing it to our attention and for providing the data for the follow up, and to Haru for help in validating the update

We're going to hold back the HPM update a bit, we have reached some stuff we wanted to discuss further, however I'll not delay the script.c interface update: https://github.com/HerculesWS/Hercules/commit/583272234fc96da7911029cd3cad13a7fb386e9e
Thank you again.

the upcoming update for the HPM is about (days away) to rollout, I'll make sure to include this in it

I am working on some changes on my endless tower files and I need a few lines translated properly.
 
http://pastebin.com/azgadpkC

Rough translation from a friend:
 
In the secondary version taming any monster doesn't count as defeating them
in any abnormal situation where you defeats monster, you can't advance to the next level
Broadcast mode

Official Item Group/Package/Chain
 
Overview
Implementation of the official 'Item Packages', 'Item Group' redesign, 'Item Chain' implementation. item_group.conf : Overview / Sample
The file was redesigned to make it attend the official equivalent's and to be more flexible, there are no more limitations on the number of groups or on how many items a group may contain, these limitations were lifted. Old_Card_Album: ( // <= <Container_Item_Name>     ("Poring_Card",8), // <= entries can be either ( "<Item_Name>", <Repeat_Count> )     "Sting_Card" // <= or "<Item_Name>" (no repeat) ) item_packages.conf : Overview / Sample
The file was created to meet the requirements of the official 'Package Item' feature, there are no limitations on how many packages you may add either. Gift_Bundle: { // <= <Container_Item_Name>     White_Slim_Potion: {// <= <Entry_Item_Name>         Random: false //May be omit when not false, signs whether a item is random or should be given whenever the packageis consumed.         Count: 30 //May be omit when not higher than 1, stands for how many <White_Slim_Potion>     }     Muffler_: {         Expire: 2 //May be omit when none, signs how many hours this item will last (makes a rental item)         Announce: True //May be omit when false, signs whether to relay a special item obtain announce when this item comes out of the package.         Rate: 50 //May be omit when 'Random' is false, from 1 to 10000 (0.01% - 100%)         Named: True //May be omit when false, signs whether the item should have the owner's name in it.     } } item_chain.conf : Overview
Officially this thing is called groups too but I found it'd be confuse to have 2 group files with entirely different functionality, named chains because the items in it are chained to each other, this file fixes quite a few stuff, for example before this patch having BS_FINDINGORE drop something was almost twice as rare than on official servers, also fixes Jewel_Sword, Gaia_Sword, Blazzer_Card, Tengu_Card and Bogy_Horn. New
'packageitem' script command, it has only 1 param which is optional, for the package item id, when not provided it'll try to use the item id from the item it is being used from (if called from an item script), it runs a item package and grants the items accordingly to the attached player. Changes
'#define MAX_RANDITEM' and '#define MAX_ITEMGROUP' were dropped, these limitations no longer exist and the server may support an unlimited number of item groups. 'item_findingore.txt' was dropped, its contents moved into 'item_chain.conf' 'item_bluebox.txt', 'item_cardalbum.txt', 'item_giftbox.txt', 'item_misc.txt', 'item_violetbox.txt' and 'item_group_db.txt' were dropped, its contents moved were updated and moved into 'item_group.conf' 'bonus2 bAddItemHealRate' changed; as group ids no longer exist. 'bAddMonsterDropItemGroup' was renamed to 'bAddMonsterDropChainItem' and changed from bonus 2/3 to bonus (0)/2 as the rate param was dropped because item chains have their own individual rates. Item names are now automatically made constants, so they may be used in any scripts throughout the server e.g. 'getitem Apple,1;', this works for all items except those having ' in their names (e.g. doesn't work for 'Monster's_Feed'). 'getrandgroupitem' and 'grouprandomitem' were modified since group ids no longer exist, item ids should be used instead (or constants as the item above mentions), e.g. 'getrandgroupitem Old_Blue_Box,1;' or 'getrandgroupitem 603,1;' Dropped conf/battle/drops.conf 'finding_ore_rate' for it has no place in the official formula (if you'd like to modify finding ore rates, edit them via item_chain.conf) Special Thanks
Beret and hemagx for bringing this change up to discussion, and the data they contributed into it Yommy and Muad_Dib for all the new item data implemented in this commit (a hell of stuff! THANK YOU BOTH <3) Streusel for all the over 100 new items he converted Gepard for the group item repeat info Masao for his debugging of the monster spawn issue Mysterious for updating the documentation Link~u!
Commit

The functions of the HCache_check contains a typo, most likely as a result of Ctrl+C & Ctrl+V:
 
fstat(fileno(first), &bufa);fstat(fileno(first), &bufb);   

likely entry should be this:
 
fstat(fileno(first), &bufa);fstat(fileno(second), &bufb); 

ran it on cygwin a couple times, fixed in https://github.com/HerculesWS/Hercules/commit/4f69a9ea0f80e78da61482b2d1143a6e58859fd1
Thank you very much

Hercules Herunterladen
 
 
 
 
Zuerst benötigen wir die 2 Git  Programme , Diese könnt ihr ganz einfach mit den untenstehenden Links herunterladen.
 
Downloads
[*] Download and Install MSysGit [*]Download the latest TortoiseGit

 
 
 
 
Installation
 
Schritt 1
 
Installiert MySysGit   das programm dient als grundlage für TortoiseGit .  Braucht ihr also nicht weiter zu beachten nach der Installation.
 
 
Schrit 2
 
Nun Installiert einfach TortoiseGit
 
 

 
Das nächste fenster ist "Choose SSH Client", wählt dort  "TortoisePLink", und drückt  Next.
 

 
 
Das nächste Fenster ist das "Custom Setup", Fenster,  Wenn ihr nicht wisst was man hier einstellen muss einfach auf NEXT drücken
 

 
Tjoah das wars auch schon mit der installation von Git
 

 
 
 
 Hercules Herunterladen mit Git auf Windows
 
 
 
Schritt 1 
 
Erstellt euch einen Ordner wo eurer Hercules Server reinkopiert werden soll.
 
Sobald ihr das habt kann es auch schon losgehen .  Macht nen Rechtsklick auf den Ordner und klickt auf  und klickt auf GIT Clone

 
 
 
Schritt 2
 
Es popt ein Fenster auf wo ihr diverse sachen eingeben könnt . Hier müsst ihr eigentlich nur die "Git URL" eingeben 
 
 
 
Habt ihr die URL eingegeben klickt ihr einfach auf OK und er wird nun Hercules herunterladen.
 

 
 
 

 
 
 
 
Das wars auch schon , nun könnt ihr mit eurem Server arbeiten

Thank you
Fixed in https://github.com/HerculesWS/Hercules/commit/f409afc22eb2d561e9eedcb238aa624ad7e80f4e

Item Packages: Update
In this commit we've modified the 'Random' field so that it can be used to define a group id to that item, as to allow packages to have more than one random group of items as its official equivalents do.
The updated documentation is as follows, note that random field is no longer optional, and for "Must" types it should be 0, this commit has updated package_items.conf in both pre-re and re, the remaining fields remain optional when their value isn't necessary, e.g. you don't need to specify Count if it is 1, Expire if it is 0, Announce/Named if it is false.
<Container_Item_Name>: {     <Entry_Item_Name>: {         Random: 0 - Signs what group type this item belongs to, 0 is "Must", a group of items that come out whenever the package is open (doesn't use rate), anything above 0 is considered "random_group_<value>", a package with 2 random groups for example gets 2 items whenever open, one from each group         Count: 30 - Stands for how much <Entry_Item_Name> will be obtained.         Expire: 2 - Signs how many hours this item will last (makes a rental item).         Announce: True/False - Signs whether to relay a special item obtain announcement when this item comes out of the package.         Rate: 50 - If 'Random' is not 0, a rate from 1 to 10000 (0.01% - 100%) will be given.         Named: True/False - Signs whether the item should have the owner's name in it.     } } HCache
Reading these new files takes more processing time than the previous as the format is more flexible (or complex), and as we are always trying to improve we couldn't let this stand, we've designed a caching method to make this processing time overhead happen only when the files are modified.
 
Smart
The feature checks when a file has been last modified, and if it hasn't been modified since the cache was made it relies on the cache instead of reading the file over. This feature also is capable of realizing when the server been recompiled and re-writes the caches when it happens so the data in them is always up to date with the latest source code.
 
The Future
As we have a number of other planned things we'll be slowly extending this to the other files that would benefit from it.
This feature can be employed in any files and used to store any data we like, we have intent to boost NPC parsing/reload with it in the near future, our estimates expect NPC parse time to drop by over 80%, reload time will drop just as much.
 
Special Thanks to
Beret and hemagx, its thanks to them we became aware of the missing feature in item packages. Muad_Dib for all the data he provided to this update mkbu95 for his help in the development of HCache Link~u
Commit

Hello Hercules, 
 
So here it is The Updated & Released Castle City of Invek, or just Invek for short. Sorry for any delay in the release of the map but I hope it has been worth the wait. I have struggled with all of the bugs and issues when using BrowEdit, and I believe it has finally paid off! Here is my first public map release and I hope you all enjoy it ! I plan to Release many more maps, and even take requests from time to time. I would GREATLY appreciate any opinions, or general enthusiasm's, after all I could just keep my maps to myself but they are intended to benefit the Hercules Community ! If you download my free map release please offer me your input ! 
 

-Updated Screen Caps- July 14, 2013 

I have included the invek.extra file incase you wish to make a change to the map. You may use this map as you wish, however please do not redistribute as your own work or offer my work at any other location. I do not require being credited for this map. This is intended to be used with sky background, if you have trouble changing the background, installing the map, or making a fix then drop me a PM and I will gladly help support you.
 
DOWNLOAD: 
 

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.

Item Packages: Update
In this commit we've modified the 'Random' field so that it can be used to define a group id to that item, as to allow packages to have more than one random group of items as its official equivalents do.
The updated documentation is as follows, note that random field is no longer optional, and for "Must" types it should be 0, this commit has updated package_items.conf in both pre-re and re, the remaining fields remain optional when their value isn't necessary, e.g. you don't need to specify Count if it is 1, Expire if it is 0, Announce/Named if it is false.
<Container_Item_Name>: {     <Entry_Item_Name>: {         Random: 0 - Signs what group type this item belongs to, 0 is "Must", a group of items that come out whenever the package is open (doesn't use rate), anything above 0 is considered "random_group_<value>", a package with 2 random groups for example gets 2 items whenever open, one from each group         Count: 30 - Stands for how much <Entry_Item_Name> will be obtained.         Expire: 2 - Signs how many hours this item will last (makes a rental item).         Announce: True/False - Signs whether to relay a special item obtain announcement when this item comes out of the package.         Rate: 50 - If 'Random' is not 0, a rate from 1 to 10000 (0.01% - 100%) will be given.         Named: True/False - Signs whether the item should have the owner's name in it.     } } HCache
Reading these new files takes more processing time than the previous as the format is more flexible (or complex), and as we are always trying to improve we couldn't let this stand, we've designed a caching method to make this processing time overhead happen only when the files are modified.
 
Smart
The feature checks when a file has been last modified, and if it hasn't been modified since the cache was made it relies on the cache instead of reading the file over. This feature also is capable of realizing when the server been recompiled and re-writes the caches when it happens so the data in them is always up to date with the latest source code.
 
The Future
As we have a number of other planned things we'll be slowly extending this to the other files that would benefit from it.
This feature can be employed in any files and used to store any data we like, we have intent to boost NPC parsing/reload with it in the near future, our estimates expect NPC parse time to drop by over 80%, reload time will drop just as much.
 
Special Thanks to
Beret and hemagx, its thanks to them we became aware of the missing feature in item packages. Muad_Dib for all the data he provided to this update mkbu95 for his help in the development of HCache Link~u
Commit