|
|
 |
 | | |
|
Сообщения темы: Auto Trader
|
|
Auto Trader 7 г., 10 мес. назад
|
Репутация: 2
|
|
This might be a random question, but....
Sometimes I run autotrader on a VM if I want to use my computer for something else at the same time. However, most of the time my toon spends trading is done with autotrader running on my actual host OS whilst I’m asleep. If I switch from one to the other, will this affect the bots ability to manage sell order prices? i.e. if the bot purchases an item whilst running on the VM, if I run the bot later on my actual OS does it still know how much it bought the item for originally and how much it can change the price for it to still be profitable, etc.
Sorry if this is a stupid question, I only ask as I used to try and run the courier the same way (sometimes on VM and sometimes on host OS) but it obviously didn’t know what missions had been done from one to the other so used to crap out.
|
|
|
|
|
|
|
Re: Auto Trader 7 г., 10 мес. назад
|
Репутация: 6
|
|
Best answer is no, there is no issue with managing sell orders, but sometime sone bot might decide an item is not worth holding onto, so best bet, leave him on the VN OR the OS.
|
|
|
|
|
|
|
Re: Auto Trader 7 г., 10 мес. назад
|
Репутация: 33
|
|
It won't remember the buy prices, and would reduce the sell costs far below the buy prices
|
|
|
|
|
|
|
Re: Auto Trader 7 г., 10 мес. назад
|
Репутация: 33
|
|
It won't remember the buy prices, and would reduce the sell costs far below the buy prices
|
|
|
|
|
|
|
Re: Auto Trader 7 г., 10 мес. назад
|
Репутация: 2
|
|
Thank you for the replies guys.
|
|
|
|
|
|
|
Re: Auto Trader 1 г., 2 мес. назад
|
Репутация: 2
|
|
Autotrader has the capability to collect statistics on buy-resell transactions and temporarily block items that have shown poor performance. When a good item for trading is identified, the bot will use reduced profit margins and competitor count requirements to place a new buy order, thereby increasing the frequency of use for recommended items. Through continuous learning, the bot will evolve to make more strategic trades over time. To activate this functionality, simply check the 'Enable Statistics' box.
To maintain statistical data, the system utilizes Firebird Database 3. Users have the option of installing Firebird as a local service or opting for remote server installation, which is particularly beneficial for multiple traders who can leverage a shared database to learn from each other. Alternatively, users can employ the 'Firebird embedded' database, eliminating the need for a separate server installation as the bot will create and connect to a local file. However, further testing is required to identify potential drawbacks of using an embedded database, such as potential file size growth without corresponding data shrinking post-deletion.
The 'Order Maintenance' feature allows users to cancel buy orders and flag items as problematic if they remain unfinished within a reasonable timeframe.
In scenarios involving a bot farm, the 'Tier' setting dictates how traders interact. Traders with the same tier will not outbid each other based on order age; rather, a trader with a lower tier may outbid a higher-tiered counterpart. This hierarchical structure does not override the general principle of the 'first come first serve rule' when the bot awaits completion of a competitor's older order.
For users handling bot farms, the 'ESI API Cache Service' proves invaluable as it eliminates redundant data downloads by sharing recent price information among traders' machines, thereby optimizing data retrieval during order processing and update phases. Users can also leverage this service for single-trader setups to pre-download necessary data during order management stages, providing a performance boost. To implement this service on a remote Windows server with Firebird database for multiple traders, users can contact Slav2 for assistance.
The configuration settings such as IP, PORT, Login, and Pass are essential for establishing connections with the server, with the default system admin account (SYSDBA/masterkey) being the recommended choice.
In the event of a database corruption or the need to start afresh, users can use the 'Recreate database' option to initiate the process.
The 'Delete Statistics' option will remove raw data saved on the server from the current machine.
'Trade Recommendations' provides a detailed view of how the bot perceives the current statistics. The table will display buy order statistics only. If you have no buy orders installed (using bulk seller mode), the bot will not recommend buying anything.
'Test Connection' checks if the bot can successfully connect to your server.
'Record Log' and 'Open Log' are intended for development purposes.
|
|
|
|
Последнее редактирование: 15.12.2024 03:51 Редактировал turringtest.Причина: edit
|
|
|
 | | |
|
|