IsTradeContextBusy() => Error-Number? - page 2 12 New comment Alain Verleyen 2014.03.10 20:31 #11 gooly: 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!! Gooly 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). 12 New comment
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!!
Gooly
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).