GilesSmith
New Member
- Joined
- Jun 2, 2012
- Messages
- 1,564
- Reaction score
- 34
Edit/Update: These requests were both implemented for Db .242+, thanks 
-- original post below --
The built in DB unstucker is causing some issues (and freezes) - is it possible to make it something we can replace with our own functions, or at minimum be able to edit some values in it (like edit the "lastchecked" value to make it not check again after we do something).
DB unstucker atm kicks in at 2 seconds and clears the entire navigation path. It is hard-coded into the navigation function with no way to disable or remove it, and it can cause mini-freezes and actually cause stucks because of how quickly it activates and yet how primitive it is in function - and because there's no way to over-ride it, it can actually interfere with other unstucker plugins.
Please can we have a way to disable it, or even replace it entirely?
Thanks
(also - related to navigation and stucks - barricade kicking is currently also hard-coded into DB's navigation function - this should also be a function that is separate, with which we can replace - we should be able to replace it just like the "attack breakable" functions, or even disable it altogether)
-- original post below --
The built in DB unstucker is causing some issues (and freezes) - is it possible to make it something we can replace with our own functions, or at minimum be able to edit some values in it (like edit the "lastchecked" value to make it not check again after we do something).
DB unstucker atm kicks in at 2 seconds and clears the entire navigation path. It is hard-coded into the navigation function with no way to disable or remove it, and it can cause mini-freezes and actually cause stucks because of how quickly it activates and yet how primitive it is in function - and because there's no way to over-ride it, it can actually interfere with other unstucker plugins.
Please can we have a way to disable it, or even replace it entirely?
Thanks
(also - related to navigation and stucks - barricade kicking is currently also hard-coded into DB's navigation function - this should also be a function that is separate, with which we can replace - we should be able to replace it just like the "attack breakable" functions, or even disable it altogether)
Last edited:






