Speeding up the development process: (Patreon)
Content
Hello everyone! Just wanted to pass this along for those of you that maybe get a little impatient waiting for updates to active projects.
A lot of people assume that writing scripts is mostly about, well… writing code. In reality, that’s only a small part of the process.
Most of the time is spent figuring out what the game is doing internally, when certain things happen, and where new logic can safely be added. That often means digging through game data, dumping tables, tracing call stacks, and identifying the right moments to run custom routines. Before a single line of new functionality is written, a significant amount of investigation has already taken place.
Once those entry points are found, the next major hurdle is testing.
Testing isn’t as simple as loading the game and seeing if something works. It involves simulating a wide range of in-game scenarios to catch edge cases and unintended behavior. As the number of projects and features grows, setting up and running all of those tests becomes increasingly time-consuming.
This is where the community plays a much bigger role than most people realize.
When you’re actively playing and using these scripts, you naturally encounter scenarios that I would otherwise have to spend hours recreating. When you report where and when something breaks, you’re effectively helping narrow down the problem space and saving a tremendous amount of development time.
To make that process as efficient as possible, there are a few things that matter most when reporting issues:
Disable other mods and test again.This helps rule out mod conflicts early and removes a large number of possible causes right away.
Avoid assuming the cause of the issue.Instead, focus on describing exactly what you were doing and what happened. In the vast majority of cases, what seems like the obvious cause isn’t actually the problem. Clear, detailed descriptions are far more useful than guesses.
Logs are critical.Logs are the single most important tool for tracking down bugs. Even when there are no obvious errors, background messages often provide clues about what went wrong. Always save and include the log from the session where the issue occurred.
Issues can be reported through the Discord support channels, bug report forums, or by creating a support ticket. Before posting, it’s also worth checking the FAQ and doing a quick search to see if the issue has already been addressed.
When questions go unanswered or receive shorter responses, it’s usually for one of two reasons: the question has already been answered many times, or the report assumes a cause without providing the information needed to identify the real issue. Both situations slow development down considerably, as time gets spent re-explaining the same answers or debating incorrect assumptions instead of working on updates and fixes.
All of this work is custom and built from scratch. Writing the actual scripts is only a small percentage of the total time involved. A significant portion is spent researching, testing, answering questions, managing support channels, and communicating updates like this one.
If you’re comfortable with the current pace, there’s nothing you need to do. But if you’ve ever wondered why things take as long as they do, this is a big part of the reason.
Taking a few minutes to report issues properly, point out where something went wrong, or help redirect repeated questions goes a long way toward speeding things up for everyone.
Just wanted to pass that along. Hope that makes sense. Have a good one!