Show Posts
Don't worry about multithreading too much, it'll honestly make your game slower if you don't get it perfect, not to mention that 2D starter game probably doesn't require too much optimization anyways.
UML diagrams are ok, but usually I just envision/draw my class architecture. Everything falls in place after that.
If you're a cs student, I'm kind of curious as to why you don't know which classes to make, but I would start with a main class (SoccerGame or something), a Player class (could have both same-team and opposing team classes), a Team class with a list/array of players, a Ball class, and maybe a custom swing component extending JFrame or JPanel.
UML diagrams are ok, but usually I just envision/draw my class architecture. Everything falls in place after that.
If you're a cs student, I'm kind of curious as to why you don't know which classes to make, but I would start with a main class (SoccerGame or something), a Player class (could have both same-team and opposing team classes), a Team class with a list/array of players, a Ball class, and maybe a custom swing component extending JFrame or JPanel.
You're right I'll start doing classes you just montionner then I'll show you the evolution of my work in a few days so you can tell me what to change
