Some routines can cache either resource tiles or boss monsters.


For example, When gathering, after filling all available march slots, the gathering routine can continue to search for tiles and place them in the cache. When a march returns, instead of wasting time looking for fresh tiles, the gathering routine can simply retrieve one from the cache and go directly to it.


You can also share a Tile Cache between multiple Instances.  To maximise rallying time, it is recommended that any instances joining rallies and gathering at the same time are set to NOT send tiles to the cache. This makes it quicker for the gathering routine to complete and for you to return to joining rallies.  Use a secondary instance (a farm account) to look for tiles and cache them then just use the same cache for each instance.



Tiles will expire after a pre-determined period of your choosing and be removed from the cache. Each cache has its own expiry settings.


It is also possible to share a cache with other users of Ragebot. Simply create a "Live Cache" or a "Fire Cache" and give the Cache ID to the person you would like to share it with.  They will create a new "Linked Live Cache" or a new "Linked Fire Cache" and input the ID. Entries in the cache are synced in real time to all other users of the same cache. If you want to withdraw use of the cache and stop others using it. Just delete it and create a new one with a new ID.


Do not use a shared cache if you are not sharing with other users.  Internet connection issues make them less reliable than local caches.


Live Cache

This is a cache held on a remote server that can be used by multiple people on different computers.


Fire Cache

A Fire Cache is the same as a Live Cache. The difference is the backend service that it is hosted by.  Fire caches are hosted on Google Firestore.



You can view or edit all caches on the Consolidated Caches page.