Details of Component Buying

Revision as of 21:29, 17 April 2009 by 127.0.0.1 (talk) (New page: {{Microsoft Zone | Link = http://classic.zone.msn.com/asheronscall/news/ASHEcompbuying.asp | Date = | Title = Details of Component Buying | Text = left <...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Original Link (now dead) - http://classic.zone.msn.com/asheronscall/news/ASHEcompbuying.asp

Click to return to Microsoft Zone Archive

Details of Component Buying



File:Zone Magic.jpg

With the opening of our June 2001 event, “Chains of Command,” spellcasters will be able to take advantage of the convenient new component buyer feature. Instead of having to make individual spell component purchases, players can set their component buyer to automatically purchase the components they need in the quantity they desire.

How will this feature work?

Setting the Component Buyer
On the screen listing a player's spell components, alongside the current number of components the player has, a red number will denote the amount of that component the player wishes to purchase. This number can be set from 0 to 999.

Filling the Component Buyer
To utilize their component buyer, players simply need to begin a transaction with an appropriate vendor and use any of the new @fillcomps commands:

  • @fillcomps -- fills the buy list with all of the desired components.
  • @fillcomps <component type> -- fills the buy list with all of the components of the given type.
  • @fillcomps <pyreal value> -- fills the buy list with all of the components until the total price of the components exceeds the given value.
  • @fillcomps <component type> <pyreal value> -- fills the buy list with all of the components of the given type until the total price of components exceeds the given value.


A Word of Caution
Please note: error messages will be received if the @fillcomps commands are used in the following incorrect ways:

  • @fillcomps used while a vendor is not open will result in the message: “You need an open vendor.”
  • The specified amount being reached will result in the message: “Buying aborted; max price reached.”
  • The vendor not having enough of the given components will result in the message: “There was not enough: <comp name1>, <comp name2> . . .”