Intel

• Original Blends are very limited, can't be really stacked, and not very much space for customization except for their gimmick of random values.
• This system introduce a new type of item: ITEM_TYPE_AFFECT
• This new type of item can have multiple bonuses
• You can set up the items in a simple single yaml configuration file:

RED_BLEND:
 vnum: 50821
 affect: 671
 bonuses:
 - type: MAX_HP
   value: 2000
 - type: ATTBONUS_DEVIL
   value: 20   
 duration: 600
ORANGE_BLEND:
 vnum: 50822
 affect: 672
 bonuses:
 - type: ATTBONUS_DEVIL
   value: 8
 - type: ATTBONUS_ISLAND
   value: 8   
 duration: 600
YELLOW_BLEND:
 vnum: 50823
 affect: 673
 bonuses:
 - type: ATTBONUS_ISLAND
   value: 8
 duration: 600
GREEN_BLEND:
 vnum: 50824
 affect: 674
 bonuses:
 - type: ATTBONUS_MILGYO
   value: 8
 duration: 600
BLU_BLEND:
 vnum: 50825
 affect: 675
 bonuses:
 - type: ATT_BONUS_METIN
   value: 8
 duration:

• Unlike blends, no, you cannot choose different times and/or values. They are set, but can be how many you want. You can stack them adding more time (you can set the max time of a single item, if you want to). You can activate and dis-activate them. They differentiate by the value of the affect.
• The system, as indicated before, can coexist with the blends if you want to keep them.
• If you create two items with the same affect but with different bonus types, the system right now can't determine their correct value when being shown in the top left corner (in uiaffectshower, strictly speaking). So if you have in mind to create this sort of gymmick, where you want to create different "levels" of an item, it will work, but right now they will only show the type of bonus. If the bonuses are different (but same affect) then, again, they will be the same (so only one between them can be active at the same time) but in the left top corner, only one or the other bonus type can be shown.
• This system will require a complete refactor of the item/inventory class (server and client side), hence the high price despite being a simple system.
• Video:

• The original shops in metin, are loaded from db first. In those, the price type is always Yang. To accommodate new type of prices, you could use item_shop_ex, which is limited. Only one price type per shop. Can't be multiple type of prices for a shop or even a single item.
• With this system the whole item_shop_ex will be nuked and replaced by a new class that will load all item's prices.
• Everything will be set up from a simple configuration file. Example:

ITEM_WANTED_NOTICE_C:
 item_vnum: 100467
 NPC:
  3001:
   npc_vnum: 3001
   price_index: 0
   prices:
    - price_type: ITEM
      price_cost: 102543
      price_count: 50  
ITEM_HUNTER_RUBY:
 item_vnum: 102543
 NPC:
  3001:
   npc_vnum: 3001
   price_index: 0
   prices:
    - price_type: ITEM
      price_cost: 30014
      price_count: 100
  3001_2:
   npc_vnum: 3001
   price_index: 1
   prices:
    - price_type: ITEM
      price_cost: 30048
      price_count: 100 
  3001_3:
   npc_vnum: 3001
   price_index: 2
   prices:
    - price_type: ITEM
      price_cost: 30049
      price_count: 100 

• For every item you can set:
  • npc_vnum: the npc vnum you set in the database (in the vnum column, not npc_vnum column)
  • price_index: basically a "symbolic" index, in case you want to set up the same item in the shop but with a different price (and you'd set up the index in shop_item to specify the price wanted)
  • prices: here you will set up the list of prices. price_count it's the cost for the ITEM price_type, usually just set it to 1.
• Video of the final result:
• In the video the items stack as soon as you buy them from the shop. That is not a feature of the system (it requires a refactor in the item/inventory class). If wanted, that's an additional 500€