Some long running bugs are just never getting fixed despite being well know issues
All the OM Team Ups have this UI issue where it keeps showing the ghost of a player who was part of the team.
While it became really rare in Cosmics, The MC are just getting plagued by them!
They are spreaded around all over, and they won't dissapear until the next servers maintenance or the Instance where OM is, simply collapses
Yes yes, you can manually chage team, but doesn't excuse this issue
Pair it with the horrible Memory leak with those darn event which always take place in MC and the fact Team Up resets everyone's models and auras for some weird issue
Comments
My super cool CC build and how to use it.
team-up groups are implemented as stacks of entities. Similar to how power stacks work, a team-up is actually just a set of buffs on an invisible critter that doesn't exist on the game's plane of existence (i.e. it's just in the source code, this is also where loot critters dwell until they are needed to show up after the end of a successful open mission because hell if we know how to spawn rewards with just like a function or something instead of spawning 50 copies of an invisible npc and making all player models within 100 feet turn into mud). Due to the way that stacks work in general terms, they are a LIFO set, meaning that in order to remove any given item in the stack or group, you must remove all other items that were added to that set after the target item. Or in other words, the first person to join a teamup group cannot automatically be removed from the teamup team until every other team member who joined after them leaves the teamup. This means this bug pops up very often. To this day there is no other known method of constructing a set of data entities that can add or remove a character from a teamup while still preserving their order or abstract index, as the Cryptic Engine was not made to support Dictionary or Hash Table structures or proper compilation of code. The entire game is coded entirely through a series of boolean JSONs just encoded through a 64-bit rng hash, which is what a hogg file actually is, because this is the most performant way to represent all data in C, the coding language of game developer monkeys who must make everything much more difficult for themselves than necessary so that they can code up an inventory window that reduces their game to 5fps and still convince themselves they are doing a good job because it took a lot of time and they totally didn't deserve that c- in discrete mathematics back at San Luis Obispo. We like star-trek, we implemented a quantum physics engine in our game, as it simulates how the code would compile in different fucking universes explaining why everything in our stupid games break every single time we change a single thing and also why random stuff is so nonperformant as we calculate every concievable outcome of an action 300 years in advance within 38287 ms, each frame. Dave hurry up and take out all the pizza boxes from last week, i still don't know why we don't hire interns to do this, we're a team of highly-skilled game developers here and this is why our foundry is totally still running and xmpp was removed because of its widespread usage by gold-selling bots and also how one nerd on twitter can ddos our servers over the span of 3 weeks while making a bunch of neverwinter players angry, we are such a great company aw3eor;h'elksmdfgdffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
My super cool CC build and how to use it.
Teammates in a team with ghost(s) don't get ally auras
even in a team of 2 people and 1 ghost, while standing literally next to each other
i.e. if you have group 1, 2, 3...7, anyone in 7 isn't going to get auras until groups 4, 5 and 6 exist