Welcome!

MaxiCooker updated to v2.11.1.

• Fixed a bug with the break handler. Disabling breaks while a break is running will no longer result in the login handler staying disabled.

MaxiCooker updated to v2.11.0.

• Added logout option to breaks - The current behaviour is to always log out. This option will allow you to afk during a break instead of logging out (If it times out it will stay logged out until the break ends),
• Added remaining break time to the break tile,
• Added time to next break to the break tile

• Moved Pitta dough and Pitta bread to the Bread category,
• Added Hunter meat (NOTE: You must ensure you have completed the required number of rumours. The requirement is displayed in the UI)
  • Cooked wild kebbit,
  • Cooked larupia,
  • Cooked barb-tailed kebbit,
  • Cooked graahk,
  • Cooked kyatt,
  • Cooked pyre fox,
  • Cooked sunlight antelope,
  • Cooked dashing kebbit,
  • Cooked moonlight kebbit,
  ,
• Added meats
  • Cooked meat (Beef, bear, boar, rat and yak supported),
  • Cooked chicken,
  • Sinew (Beef, bear, boar supported),
  • Ugthanki meat,
  • Cooked rabbit,
  • Roast bird meat,
  • Thin snail meat,
  • Roast rabbit,
  • Lean snail meat,
  • Cooked crab meat,
  • Fat snail meat,
  • Roast beast meat,
  • Cooked chompy

MaxiCooker updated to v2.10.7.

MaxiCooker updated to v2.10.6.

• Most camera turning is now handled by the mouse instead of the keyboard. This greatly increases turning speed and accuracy
  • Misclicking due to the camera turning at the same time as interaction should no longer be a problem
• Failed interaction will now be retried 3 times before turning the camera. Previously it would turn the camera as soon as the interaction failed which wasted time if interaction didn't fail due to the camera position
• Fixed some path building issues
• Added support for logging out of Deadman mode (DMM) worlds. The logout timer wasn't being accounted for which meant the bots would continually reset the timer trying to log out

MaxiCooker updated to v2.10.5.

• Fixed a bug caused by using stop after x with logout after all activities are complete resulting in the session failing to stop

MaxiCooker updated to v2.10.4.

• Fixed a bug where applying settings after switching profiles or removing the active activity didn’t cancel it
• Fixed a bug where advanced settings weren’t applied to the active activity unless the activity itself was modified
• Added a new scheduled shutdown trigger if your bank is full and we need to deposit items
• When new settings are applied the changes should now be more immediate. Some bots would previously finish out the current action before the settings would appear to take effect
• No longer showing a client info message every time an activity ends. The existing message will still be added to the logs and the final activities reason for ending will still be shown in the scheduled shutdown info message

MaxiCooker updated to v2.10.3.

Temporarily disabled the position change trigger for the stuck detection system recently implemented
If you've been experiencing issues with bots scheduling a shutdown because the position hadn't changed even though the bot was working correctly feel free to request a refund.

MaxiCooker updated to v2.10.2.

• Fixed a bug with scheduled shutdowns not stopping the bot if the bot is paused and "Logout when all tasks are completed" is enabled
• Fixed resetting shutdown triggers when walking
• Potential fix for items in the bank being registered as items gained when opening the bank for the first time
• Fixed a bug where multiple activities with the same item used in an amount goal would only track progress for the first activity with that goal item

MaxiCooker updated to v2.10.1.

Wines should no longer trigger a shutdown due to no xp gained in a certain time

MaxiCooker updated to v2.10.0.

Improved Bot Shutdown Handling
- Any condition that would previously stop the bot immediately will now schedule a shutdown for 2 minutes before the next billing hour.
- This ensures users have time to adjust settings and reduces partial-hour charges due to early shutdowns.

New Shutdown Triggers
The bot will schedule a shutdown if any of the following conditions are met:
- No XP gained within a set time (bot-specific)
- No item changes within a set time (bot-specific)
- Incomplete setup for 5+ minutes
- Bot paused for 10+ minutes

Changes to Existing Triggers
The following conditions previously stopped the bot immediately but will now follow the scheduled shutdown process:
- Out of activities
- Pathing failure

Cancellation & Continuation Improvements
- Shutdowns are cancelled if settings are re-applied before the scheduled time.
- When settings are re-applied, any prematurely ended activity (goal not met) will resume where it left off.
- Manually cancelled activities due to user setting changes will not restart.[/B]

If you experience any issues with this system please report it through my discord server