@thebiscuit said in Need Help With A Complex BAS Project (Paid Well):
@sergerdn Unfortunately I have quite literally done this exact approach, but it is not as simple of a solution as this, and it still is not working.
Fair enough.
BAS lets people build large projects without much programming experience. That’s where things like KISS, SOLID, separating responsibilities, and documenting how everything works can get overlooked. Eventually, even a small change becomes hard to make without breaking something else.
For example, I’d split this into at least two separate programs:
- Warm-up tool: runs the preparation logic and saves the profiles and their data.
- Main tool: loads that saved data and does the actual work.
Each has its own job, and you can test them separately. That makes it easier to narrow down where things go wrong.
If everything is mixed into one huge BAS script and nothing is documented, someone first has to work out what it does, how the pieces depend on each other, and what a change might break. At that point, “fix my bot” can turn into reverse-engineering the whole project before you can even start fixing it.
I haven’t seen your project, so I don’t know if this applies to yours. I’m just talking about how BAS projects often end up being put together — one big mess, lol.
