Initially I was irked by Skibidi Toilet and considered it to be peak of brainrot content. Though at one party we decided to do an ironic Skibidi marathon and I genuinely had a fun time watching the shorts, it was quite fun trying to piece together was was going on in the series, we even started to root for some of the characters. When GMod/TF2 videos were just starting to appear on YT, I recall watching/making a lot of very similar videos, I'd say it was even worse and with more brainrot. Skibidi Toilet is exactly the same, except with higher production quality, and I no longer think it's a bad thing after the marathon, just more of the same.
This looks awesome! I've been struggling fine tuning using Discord messages from my server (for memes), issues with CUDA mostly. Will defo try this out!
On a side note, has anyone tried something similar? I have 100K messages and want to make a "dumb persona" which reflects the general Discord server vibe. I don't really care if it's accurate. What models would be most suitable for this task? My setup is not that powerful: 4070S, 32GB of RAM for training, Lenovo M715q for running with, Ryzen 5 PRO 2400GE, 16GB of memory.
I'd also recommend checking out Sprint Vector if you have a decent PC for PCVR (via Steam Link) - I was fully drenched in sweat after a 30 min gameplay session. Gorilla Tag is also nice for workouts while being fun, no PC needed.
I have not worked on an MMO before, but recently I had the chance to try out my own custom event system on a small multiplayer game (Unity, PUN2). I had most issues with differentiating which events came from which client. Additionally, I had lots of issues differentiating which events were issued locally. In the end, the code ended up being quite messy. If I were to redo the game, I'd use direct method calls where possible with regular callbacks.
Generally, I found that when using event systems you have to be really careful not to over-use it, even small/single player games. Its super hard to debug when everything is an event - if you go this route, you essentially end up in a situation where everything is "global" and can be reached from anywhere (might as well just go full singleton mode at that point). Additionally, I found it difficult having to deal with event handlers which raise other events, or worse, async events, as then it becomes really hard to ensure the correct order of invocations.
If you plan to use an event system, my advice would be (in Unity):
- Reference and raise events only on root Game Object scripts (e.g., have a root "Actor" script which subscribes/publishes events and communicates with its children via properties/C# events)
- Never subscribe or publish events in regular "child" components
- Use DI/service locator to fetch systems/global things and call them directly when possible from your "Actors"