Ranking ALL Design Patterns for Games under 30min 

Thanks! Happy you enjoyed it :D

Thanks! Oh, that’s true! 🤯😅

Thanks! I am happy you like it :D

🙏 thanks a lot :D

Thanks! Happy you like it!

Thanks! I agree, lots of the patterns can cover more complex use cases.

The main advantage of the Visitor pattern seems to be “adding new operations to an existing system without modifying the original codebase” which is not 100% since you need to add the accept method. So, as an alternative I would modify the codebase to fit whatever feature I am adding. Using simpler patterns like Strategy, Bridge,… For example each item could have an associated “LootConfig” directly. It’s more obvious.

@This is GameDev yea composition, seems better here, aka loot table. Though I think most games want to change the loot tables after release so usually it's an api request, so a completely separate service would be best. Each entity could have a loot table Id.

@This is GameDev I think we missed an important detail of the visitor pattern. There should be more than one implementation of the visitor. I'm not sure that the loot example fits with this idea, I haven't come up with an abstract example yet. But maybe there is a loot visitor, a hard-core loot visitor, a gold loot visitor, ect. However, this starts to feel like just options that could be set directly on the loot visitor. Maybe the idea should be a killable entity visitor and loot visitor derives from that, maybe an experience visitor would also derive from killable entity visitor.

Awesome! Thank you!

Trees or graphs in general are very useful for lots of stuff :D

Factories don't always need to Instantiate something. An Object Pool is a kind of Factory that supplies either a new instance of something, or one that was pooled. Also, Factories are good when you are Deserializing state from a previous Save session. You can Factory-create by an ID for that object and then use the Serialized data to restore their state. I think Factory is a good pattern.

An object pool is not a factory, it is an object pool. The factory pattern deals with the steps it takes to create an object whereas an object pool deals with what piece of memory that object takes up. I guarantee you can have all that serialization/deserialization logic in a "Persistence" class which has nothing to do with the factory pattern.

@@evanhowlett9873 "Use the Factory Method when you want to save system resources by reusing existing objects instead of rebuilding them each time." "Probably the most obvious and convenient place where this code could be placed is the constructor of the class whose objects we’re trying to reuse. However, a constructor must always return new objects by definition. It can’t return existing instances. Therefore, you need to have a regular method capable of creating new objects as well as reusing existing ones. That sounds very much like a factory method." "Check list If you have an inheritance hierarchy that exercises polymorphism, consider adding a polymorphic creation capability by defining a static factory method in the base class. Design the arguments to the factory method. What qualities or characteristics are necessary and sufficient to identify the correct derived class to instantiate? Consider designing an internal "object pool" that will allow objects to be reused instead of created from scratch. Consider making all constructors private or protected. " Sources: Multiple Design Pattern websites, including the one posted as a link in this video.