|
True Sansha wrecks and spawns not identified. 4 г., 6 мес. назад
|
Репутация: 0
|
|
The BOT falsely identifies normal "Centus Dark Lord" NPC and their wrecks as faction spawns and misses True sansha spawns.
Logs and a screenshot sent.
|
|
|
|
|
|
|
Re: True Sansha wrecks and spawns not identified. 4 г., 6 мес. назад
|
Репутация: 841
|
Nope, bot sets faction ship flag one time per locaction to check for wrecks when mission is over. Then bot uses cached value and current respawn may not have any of faction ships. From your log bot added faction ship/wreck present flag checking this respawn:
 Предупреждение: Помехи!| Код: |
15:31:33: StopOperationHunter(430)
15:31:34 (20978) Finish. Code 1, Func : SetupCargoManager
15:31:34 (20978) Window opened (cargohold). Code 1, Func : OpenWindow
15:31:34 (20979) Capships not confirmed. NPC list:, Func : StopOperationHunter
Name: Centatis Behemoth, ID: 24023, Dist: 61000, Bounty: 153750, Hull: 4, Locked: 1, A: 1, inAtk: True, inLk:True
Name: Centatis Devil, ID: 24021, Dist: 62000, Bounty: 142500, Hull: 4, Locked: 1, A: 1, inAtk: True, inLk:True
Name: Centatis Daemon, ID: 24022, Dist: 64000, Bounty: 146250, Hull: 4, Locked: 1, A: 1, inAtk: True, inLk:True
Name: Sentient Alvus Controller, ID: 27723, Dist: 85000, Bounty: 13875000, Hull: 6, Locked: 0, A: 1, inAtk: True, inLk:True
Name: True Sansha's Supercarrier{5}, ID: 40671, Dist: 85000, Hull: 11, Locked: 0, A: 1, inAtk: True, inLk:True
Name: Centii Loyal Ravener, ID: 17061, Dist: 85000, Bounty: 21375, Hull: 2, Locked: 0, S, W, A: 2, inAtk: True, inLk:True
Name: Centii Loyal Servant, ID: 17069, Dist: 85000, Bounty: 18000, Hull: 2, Locked: 0, S, W, A: 2, inAtk: True, inLk:True
Name: Centus Dread Lord, ID: 24159, Dist: 85000, Bounty: 1162500, Hull: 6, Locked: 0, A: 1, inAtk: True, inLk:True
Name: Centus Dread Lord, ID: 24159, Dist: 86000, Bounty: 1162500, Hull: 6, Locked: 0, A: 1, inAtk: True, inLk:True
Name: Centus Dread Lord, ID: 24159, Dist: 86000, Bounty: 1162500, Hull: 6, Locked: 0, A: 1, inAtk: True, inLk:True
Name: Centii Loyal Servant, ID: 17069, Dist: 87000, Bounty: 18000, Hull: 2, Locked: 0, S, W, A: 2, inAtk: True, inLk:True
|
|
|
Slav2
Администратор
Постов: 17023
|
|
|
|
|
Re: True Sansha wrecks and spawns not identified. 4 г., 6 мес. назад
|
Репутация: 841
|
|
Bot may miss faction wreck in case of overview scrolling error. If you see this send me log and screens (from errorhandler folder, zip its content). Scrolling to locate wreck may be not so reliable if you use speed tank. I spent quite a lot of time to polish this code (about a month) and seems not made it 100% working. I recommend to use looter to loot and salvage all wrecks.
|
|
Slav2
Администратор
Постов: 17023
|
|
Последнее редактирование: 02.05.2021 10:46 Редактировал Slav2.
|
|
|
Re: True Sansha wrecks and spawns not identified. 4 г., 6 мес. назад
|
Репутация: 0
|
|
Thanks. Maybe I read the code wrong. But, if I turn ON "Loot faction wrecks" the bot will loot a random Dread lord wreck every time, so it does think they are faction.
I will turn it on again and get logs.
And missing a faction wreck is not that big of a deal, but when it loots the non faction wrecks it wastes allot of time ..
|
|
|
|
|
|
|
Re: True Sansha wrecks and spawns not identified. 4 г., 6 мес. назад
|
Репутация: 841
|
|
Send me screen when this happens. In fact bot does not save name of a faction npc and use keywords one more time to loot wrecks. Need to compare NPC name and list of keywords
|
|
Slav2
Администратор
Постов: 17023
|
|
|
|
|
Re: True Sansha wrecks and spawns not identified. 4 г., 6 мес. назад
|
Репутация: 0
|
|
Sent logs over email. Thanks.
|
|
|
|
|
|
|
Форум
