Hi, first post on this forum ^^
I was watching the course on Unity Design Patterns and came upon the lesson that describes why singleton patterns are not always the best thing to use in code, and I want to try and phase them out of my programming. Problem is, I seem to have dug myself into a mental hole with how to get around it.
I mainly use monobehavior singletons to keep track of things that a lot of scripts may have a use for. Like, say, AudioController.Instance.PlaySound() or telling UI to update without needing a bunch of scripts to have access to the text object. I know I just need to think outside the box, but I may need some help cutting a hole in said box. Any advice?