Closed ntpeters closed 11 years ago
belak
commented
11 years ago Not sure this is as realistic as we originally thought. I like the idea, but how would this transfer over to the server? Also, each Entity class currently has a constructor that requires different values to be passed in. If we even wanted to THINK about doing this, we'd have to make entities a lot more consistent.
ejrinkus
commented
11 years ago Yeah, we decided to hold off on implementing the .bro packages for this semester. We are thinking that if we want to keep going with this project beyond this class, we need to overhaul the code anyway, so we can do those implementations then.
On Sun, Nov 11, 2012 at 6:05 PM, Kaleb Elwert notifications@github.comwrote:
Not sure this is as realistic as we originally thought. I like the idea, but how would this transfer over to the server? Also, each Entity class currently has a constructor that requires different values to be passed in. If we even wanted to THINK about doing this, we'd have to make entities a lot more consistent.
— Reply to this email directly or view it on GitHubhttps://github.com/stryderinnovations/Broids/issues/77#issuecomment-10273730.
Eric Rinkus 810-394-6039 Michigan Technological University Undergraduate Computer Science Snowboard Instructor Mont Ripley Quidditch Club at Michigan Tech - Vice President/Captain Computer Science Learning Center Coach Triangle Fraternity - Alumni Relations
/ \ /_\ / | \ /_|___\
Use .bro packages (zip files) containing a text file describing the ship and the sprites it uses. This way we could just create packages for new ship/bullet/asteroid types and have the game read them in, instead of having to go edit enum code everytime we want to implement a new type.
What do you guys think? @krgauthi @ejrinkus