Ind

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

I think in the part of the code you didn't show there is some variable called 'script', it usually isnt a problem when not making use of the script interface but script_getnum uses the interface so it is conflicting, rename your 'script' variable to anything else and it should work.

I've taken a pass on it, I believe the delay and global_delay_var settings are now being properly employed, fixed the leave/kick bg thing keeping people in queue (HQO was off), the match will now end when either team ends up with no opponent due to kick/logout (still need to code the grant win to whoever left part), logging in/out now properly removes player from queue (again HQO was off), the "cancel" thing should now be working as well.
Thank you very much,
https://github.com/HerculesWS/Hercules/commit/449a41af45d448e18006ef9c105c393592239de1

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

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

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

Hercules most active month to date! give yourselves a hand, thank you all!

Do not forget to Beret and their 1000 mp for ind. xD

Yommy was just awesome this month (as usual)
<3

Indeed it has been! Lets recap shall we?
 
 
May:
 
April:
 
March:

June Digest 2013
The following digest covers the month of June 1st - June 30th 2013.
 
Team Changes
[*] M45T3R has joined as a International Moderator.

Development Highlights
[*]Initial Release of Monster Transformation Scrolls ( 6fd4403e) [*]Memory Slasher [2] !!" - 17MB Down! (5e90c5f) [*]Introducing Hercules Renewal Challenge (0395610) [*]2013 kRO Updates [*]RE Physical ATK System [*]RE Magical ATK System [*]RE Casting System [*]RE ASPD System
[*]Skill Tree Redesign (2de1910) [*]Official Item Group/Package/Chain (fcba8a2) [*]Hercules Renewal Phase One: PC, Party, Map, Timer (0ea143c)


Scripts
[*]Hall of Abyss ( 94358d9) [*]Hazy Forest (8878ceb) [*]Mora Enchantments (8ec1942) [*]Eden Tutorial (37610e6) [*]Script commands [*]Added: packageitem, bg_create_team, bg_join_team, bg_match_over ( Topic) [*]Modified: getrandgroupitem, grouprandomitem (Topic)



Client Support
[*] Hercules WPE Free (5a94299, 5321d32)

Plugin Support
[*] Staff Plugins [*]DB2SQL (5321d32)

Community Contributor additions
[*]Susu, for his awesome pull requests [*]Via, for his outstanding wiki contributions [*]Xgear, for his continues help and pointing out issues

Statistics
[*]During the period there were 223 Commits. [*]Of these 223 commits, 114 included bug-fixes. [*]15 Commits from Pull Requests [*]In this month, there were 112,569 Additions and 91,374 Deletions.

Hercules CC Program
Hello~! - What?!
We're changing how the CC Badge works, making it a position that actually makes sense with it's name: a position given to community members who've contributed to Hercules.
 
Badge Requirement
Any of the following will make you elegible to receive the title, be aware the position is not automatically-granted, the staff who oversees the section in question will appoint you to receive the title.
Outstanding presence in the bug report section Outstanding presence in the wiki Outstanding presence in the support sections (helping others) Outstanding presence in the downloads sections (sharing your stuff) Help the development by providing key information Any other outstanding effort to contribute to Hercules not necessarily listed here (we'll add more items as we see fit)  
Position Benefits
We have plans/intentions to implement specific benefits depending on why each title was given (e.g. if its because you're active in the bug reports section you may receive pseudo-moderation-powers on that section), however at this point in time the title is only a title -- there are no benefits to it yet.

barely announced it and already heard some stuff, nevermind them -- I'll clear this point tho
The "Community Participation Badges" (they didn't even mind to rename it) was introduced by me to them while I was in their staff last year.
 
Yeah, such a surprise! (not)

barely announced it and already heard some stuff, nevermind them -- I'll clear this point tho
The "Community Participation Badges" (they didn't even mind to rename it) was introduced by me to them while I was in their staff last year.
 
Yeah, such a surprise! (not)

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

Fixed in https://github.com/HerculesWS/Hercules/commit/5d467dd19d1756e42d3c95f553054177be6b5290 (Thanks to Yommy!)

Fixed in https://github.com/HerculesWS/Hercules/commit/5d467dd19d1756e42d3c95f553054177be6b5290 (Thanks to Yommy!)

There we go, (didnt find the first 2 by the way): https://github.com/HerculesWS/Hercules/commit/02bb58d320f16ddc30ac3d1e6508cf08997f583a
Thank you again.

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

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

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

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

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

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

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