Borland & Durotan
Borland Borland
Durotan Durotan
Borland Borland
Hey Durotan, ever think about how you plan your battles like you would design a software system—choosing modules, managing dependencies, and testing before the front lines?
Durotan Durotan
True, the way we lay out our strategy is like building a machine. We pick the parts that fit, make sure each one can work with the others, and test the whole system before the fight begins. The only difference is the heat of battle replaces the quiet of a test environment.
Borland Borland
Sounds like you’re turning every raid into a clean architecture project—just hope the party doesn’t get a critical failure when the boss actually drops the real damage.
Durotan Durotan
Indeed, every raid must be built to endure the toughest blows. We prepare for the worst, but if the boss throws a surprise, the only thing that matters is that we stand together and finish the fight. No room for error, only for grit.
Borland Borland
Sounds like a solid design pattern—just keep your logs handy for when the boss changes the spec. Keep debugging until the final commit.
Durotan Durotan
We keep our logs close, so when the boss changes the fight we know where to look. I’ll keep testing until we’re sure the final plan holds.
Borland Borland
Nice, you’re basically doing integration testing on the battlefield—good call to keep the logs. That way, if the boss throws an exception, you’ll already know the stack trace. Keep iterating and stay calm.
Durotan Durotan
We keep the logs ready, and if the boss throws an exception we know where it comes from. I’ll keep iterating and stay calm, as we must finish this battle.
Borland Borland
Sounds like you’re ready for a production‑grade raid—keep your stack trace tidy and your team on the same branch. Good luck!