Shosuko Posted January 29 Share Posted January 29 (edited) 1 hour ago, Guille6785 said: why You can document that a bug is happening, but the code causing the bug defies documentation b/c it is doing something it is not supposed to. This hinders maintenance and development. Buggy code isn't just doing something unintended, its code that isn't working properly. The old AG is a great example - there was a bug in the code that sometimes gave you a moment for a few extra hits between charges. If they wanted to increase the time it might stand still between charges, where do they do that? They don't even know where its happening. There is no "if xyz then pause" line, there is no tuning "EXTRA_DELAY_BEFORE_CHARGE = 100" They would first have to fix that bug so that its behaving as coded, then add new behavior for when to pause and how long. Lavae pathing around walls and getting stuck on lava ponds is another example. Perhaps its unintended they get caught on lava ponds, but the code that leads to this interaction is working as it is designed to - ie the lavae picks its target and stays locked to them, pathing around walls. If they wanted to change its behavior they could, because its behavior is all according to its code. Edited January 29 by Shosuko 9 2 Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now