Chat
Discord
03-16-2015, 01:21 PM
I really cannot tell what you are doing wrong, as I have not got the slightest idea of what your code looks like, how it evolves over time etc. If you want you can send me some of your code, and I'll try to review it; other than that the only advice I can give is based on my own experiences, which may be completely different from yours.
One of the most useful things I've learned is to not try to write something that is perfect (or even good) the first time, but instead just try things out, and then fix things later on. In your case you are working on a 2D brawler game and as a result a lot of things do not even have to particularly well optimized, so do not fall into the trap of trying to optimize everything, as you will certainly fail to do so and just end up unproductive.
One of the most useful things I've learned is to not try to write something that is perfect (or even good) the first time, but instead just try things out, and then fix things later on. In your case you are working on a 2D brawler game and as a result a lot of things do not even have to particularly well optimized, so do not fall into the trap of trying to optimize everything, as you will certainly fail to do so and just end up unproductive.
Age ratings for movies and games (and similar) have never been a good idea.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.