Discussion
I am sure this is just my bad code design, but often times when I use signals to let two systems communicate, the signal emits with a reference to self so that whenever the receiver gets it, they have a direct reference to the class to call potential helper functions from.
Cause passing potentially "everything" a receiver may need via the signal I rarely find practical.
@Cheeseness This is now my philosophy. So far I always tried to reach "clean code", which due to my (lack of) skills has just become a massive time sink.
Now I do what I must to get where I want to be.
Let alone the interaction system between player and items is so complex that I have a set of signals JUST so I can give visual/HUD feedback to player and somehow even those have enough edge cases that a cross reference between systems becomes just easier...
@memoriesin8bit I figure that if something is a hurdle for Future You or anybody else that you want to work on the codebase in the future, then that's worth thinking about and improving on, but other than that, any other ideas of what good/bad code is are just dogmatic noise to appease the tastes of someone who isn't working on the project. Do what works for you \o/
@Cheeseness Luckily I don't plan on changing my solodev path so nobody has to suffer through my mess.
But yeah, I often sit there wondering "what's this for again" - hence my want for refactoring. But often I just don't know how else to solve this problem aside from adding a ton of comments. I... I do my best.
@memoriesin8bit I don't do it often, but there are definitely cases where I think it makes sense/is reasonable to do. IMO the only bad design is design that gets in your way/prevents you from achieving what you want to achieve.