The following warnings occurred:
Warning [2] Use of undefined constant SAPI_NAME - assumed 'SAPI_NAME' (this will throw an Error in a future version of PHP) - Line: 3388 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3388 errorHandler->error
/showthread.php 116 build_archive_link
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/inc/functions.php 3324 build_forum_breadcrumb
/showthread.php 195 build_forum_breadcrumb
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/showthread.php 195 build_forum_breadcrumb






Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Price of items sold by a vendor
Author Message
Khaos
Master
**

Posts: 595
Likes Given: 166
Likes Received: 83 in 51 posts
Joined: Mar 2012
Reputation: 11



Post: #8
RE: Price of items sold by a vendor
Well it is more than that: Okay. Everything Coruja said is exactly right, but what is being left out is that if there is no value set to an item that Sphere will calculate item value based on value of every item in the RESOURCES= Property.

If you want items to sell at a normal price, set your tag.vendormarkup with a value of -15. You can then override this on each vendor and set the tag to those vendors. I keep tossing around editing the source to add in more code handling for the value itself. It used to be value=<1_val>,<2_val> with 1 being for buy value and 2 for sell value. Which is what I think should truly be done, because even EA, sell values are 50% of item cost and they increment/decreases prices based on sales that day on that vendor. It is actually interesting how they handled their commerce. Another thought was to avoid two values per item and just edit tag.vendormarkup into two tags. Tag.vendorbuymarkup and tag.vendorsellmarkup. This would give more control over buy/sell prices.

Personally I like both ends of it. Like you could charge 100,000 gp for an item and have it only sell back for 1gp. Which is the most precise control. But the tag idea would be more for a mass control versus individual. Maybe both would be ideal.
(This post was last modified: 02-19-2016 12:03 AM by Khaos.)
02-19-2016 12:00 AM
Find all posts by this user Like Post Quote this message in a reply
[+] 1 user Likes Khaos's post
Post Reply 


Messages In This Thread
Price of items sold by a vendor - karma - 02-07-2016, 10:09 PM
RE: Price of items sold by a vendor - Khaos - 02-19-2016 12:00 AM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)