Leunsel Some people may wonder why it takes me so long to release new Cheat Tables, or why I do not put out more small tables for random games in between. The answer is actually pretty simple, but it has more than one layer.
The first reason is time. My studies take up the biggest portion of my free time, and that naturally limits how much energy I can put into table creation. That part alone already slows things down a lot. But while that is the largest practical factor, it is not the real core of the issue.
The main reason is that I am rarely satisfied with my own results. I have a very specific standard in mind for what a release should feel like before I am willing to put it out publicly. If a table does not feel substantial enough, polished enough, or technically justified enough, I usually keep working on it rather than releasing it half-heartedly.
I do not really like the idea of releasing something large in file size, structure, and framework overhead if the actual feature set behind it feels too small to justify it.
That matters even more because my Cheat Tables are built on top of my own Lua framework. That framework gives me a lot of power and flexibility, but it also means the baseline size and complexity of my tables are already much higher than what people may expect from a very small release. So when I package a table, I do not just see two scripts and a few records. I see the full technical weight behind it.
And that is exactly where the internal conflict starts. Imagine releasing a Cheat Table that weighs around 300 KB, yet in practice it only offers two very simple scripts. Even if those scripts technically work, the release would still feel disproportionate to me. It would feel unfinished, underwhelming, or simply not in line with the level of quality I want my work to represent.
A release for me is not only about whether something functions. It is also about whether the end result feels coherent, worthwhile, and worthy of the framework and structure behind it.
That is why I do not tend to push out "just something" for the sake of activity. I would rather release less often and feel confident in what I put out than publish something that immediately feels too small, too thin, or too compromised. From the outside, that can look like inactivity. From my side, it is mostly a matter of standards.
So in short, yes, my studies take away a lot of the available time. But the bigger reason why releases take so long is that I am extremely critical of my own output, especially when it comes to balancing scope, effort, and presentation. I want a table to feel like it deserves to exist in the form it ships in.
That mindset definitely slows me down. But at the same time, it is also the reason I would rather release something late than release something I cannot really stand behind.
So if a new table takes longer than expected, or if there is a long silence between releases, it is usually not because nothing is happening. More often than not, it is because I am still trying to get it to a point where it actually feels right.