Open weberdaniel opened 2 years ago
I guess it would be better to show/present a simple reactive design pattern for now. Something like an actor, which catches an exception from a std::bad_alloc and then terminates the actor and restarts it.
maybe something with the ant algorithm? https://en.wikipedia.org/wiki/Ant_colony_optimization_algorithms
The first scope should be very limited and one way only:
There will be a main server The main server will serve as a single source of truth Clients will be able to connect to the server and receive data from the server Clients will not be able to send data to the server The main server will create a map with walls and zombies The main server will use a QGraphicsScene for calculus of collisions and demo scene Each zombie will be represented by both a C++ Actor and a QGraphicsObject Each zombie will perform a simple random walk