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
Is there a way to implement vendor buy in an enhanced client?
Author Message
darksun84
Sir Spamalot
****

Posts: 1,687
Likes Given: 245
Likes Received: 162 in 151 posts
Joined: Mar 2012
Reputation: 35



Post: #2
RE: Is there a way to implement vendor buy in an enhanced client?
04-07-2017, Nolok
- Fixed: random ranges ( e.g.: {i_dagger 1 i_gold 1} ) sometimes returned a totally random and unexpected value.
If the value was used to create an item, it could either create a random item or not create it at all, without logging any error.
- Fixed: vendors couldn't re-sell the items bought from the players.
- Fixed: with the current User Interface (the blue one, not the orange which is older) of the Enhanced Client, in the buy gump
the paperdoll of the vendor often was missing on the left.

IMPORTANT: with the same UI of the EC the buy gump may not work, because it doesn't show the items in stock.
This occurs with the new UI (blue) and not with the old (orange) because the new one wants the vendor to have
its name inclusive of the title. If the "the" keyword and the following title aren't found, the code of the interface
generates an internal error and halts the execution of the remaining code (which renders the items in the list).
As example: if the vendor name is Greg the items don't show, but if you set the NAME (and not the TITLE property)
to Greg the Butcher ("the" word is mandatory) the items are finally shown.
Since the client retrieves the name with the tooltip data (Cliloc 1042971) the server sends, if you want a workaround
to this requirement, you can leave untouched the NAME property and send a custom name cliloc which contains also the work/trade title:
ADDCLILOC 1042971, <NAME> The <QVAL <ISEMPTY <TITLE>> ? Vendor : <TITLE>>

The change is only on the xperimental version i think
(This post was last modified: 12-20-2018 08:45 PM by darksun84.)
12-20-2018 08:45 PM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Is there a way to implement vendor buy in an enhanced client? - darksun84 - 12-20-2018 08:45 PM

Forum Jump:


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