I'm trying to use continuous mule because of the queue, but even if I use only one mul

Too high cpu usage when using continuous mule about kolbot HOT 5 CLOSED

diafree commented on July 28, 2024

Too high cpu usage when using continuous mule

from kolbot.

Comments (5)

theBGuy commented on July 28, 2024

Not sure what to tell you, cpu usage of the mule profile I just started isn't any higher than normal

from kolbot.

diafree commented on July 28, 2024

My AutoMule.js file configuration is as below and Diablo 2 running with that profile, CPU usage exceeds 40%

If 'continuous mule' is not used, the cpu usage is not abnormally high. But because of the queue I want to use this function

Is it a problem to use the Korean version of Diablo to use the function?

		// Trigger muling at the end of a game if used space in stash and inventory is equal to or more than given percent.
		usedStashTrigger: 90,
		usedInventoryTrigger: 80,

		// Mule items that have been stashed at some point but are no longer in pickit.
		muleOrphans: true,
		// Continuous Mule settings
		continuousMule:	true, // Mule stays in game for continuous muling. muleProfile must be dedicated and started manually.
		skipMuleResponse: false, // Skip mule response check and attempt to join mule game. Useful if mule is shared and/or ran on different system.
		onlyLogWhenFull: false // Only log character when full, solves an issue with droppers attempting to use characters who are already in game

from kolbot.

theBGuy commented on July 28, 2024

https://github.com/blizzhackers/kolbot/tree/mule-fixes try this branch and let me know if it lowers it

from kolbot.

diafree commented on July 28, 2024

I tested it, but the cpu usage is still high.

from kolbot.

theBGuy commented on July 28, 2024

The current version for the mule-fixes branch should fix this.

from kolbot.

Recommend Projects