IsTradeContextBusy() => Error-Number?

Back to topics list  | 1 2 To post a new topic, please log in or register
angevoyageur 2014.03.10 21:31 #

Thank you but are they still valid?

These err-numbers are now used differently:

e.g. 135 (formally: ERR_PRICE_CHANGED) is now

which I guess - could happen not only at compile-time!!


PS: See all these needless End-Of-Lines :(

You are mixing compilation errors with trade server errors. Read carefully the documentation.

Trade server errors didn't change, only the documentation changed as noted by RaptorUK (in the link given to you by qjol).

Back to topics list   | 1 2  

To add comments, please log in or register