necropola

... quest-like achievement-structure.

With the worst being task collections which have to be completed in order, e. g. Frode's Journal which even forces you to do/repeat the 3 SotO metas in a specific order or it doesn't count,

W T F !

Yep, I'm probably one of those fans. Though I also very much like the team-play aspect that usually comes with (instanced) group content. What I would like are random encounters you'd find in open world (possibly instanced) which would ~~require~~ encourage people to spontaneously group up as a team of max. 5 to beat it.

Similar to Dungeoneering in RuneScape, but with occurances/entrances randomly spread out over the open world, using your current gear scaled to the level of the encounter, difficulty/rewards scaled to the number of people in the group and the overall theme based on the current zone.

My interpretation is that the support team is overwhelmed by the amount of bugs that the content teams are releasing into the world on a now (new release schedule) even more regular basis.

My suggestion (to you) is that you unblock as many of those morons as you can handle by having a thick(er) skin.

I think that GW2 already lost it's way/innocence very early on when ArenaNet listened to a vocal minority of players who wanted WoW-like progression and instanced content ... which lead to Fractals and Ascended Gear with Agony Infusions and later with HoT even to Raids.

I mean, there's nothing wrong with people enjoying this type of content. I hear that WoW is very much alive and -- according to MightyTeapot -- Mythic+ is even better than Fractals. Funny enough, he also says that he is playing WoW as an Instance Simulator (and not as an MMO).

What I fiind kinda sad is that ArenaNet didn't have the balls (or chance?) to stick with their original vision of what an MMO should be like and instead tried to be more like WoW.

➡️ The miller, his son and the donky

I like this/your illustration with colors indicating the expansion releases:

It's very interesting to also look at the quarter after each expansion release which I would read as follows:

• HoT was hyped very much, but wasn't very well received. Many players probably found it too hard (before HoT difficulty nerfs and power creep from later expansions) and told their friends about it.
• PoF wasn't hyped very much, but was very well received. People loved their mounts and spread the word.
• EoD+Steam was ... I don't know.

To me it looks like outbound federation is working again, e. g. posts I create on lemmy.sdf.org are now federated again to the (original) community on lemmy.wtf.

Lemmy 0.19 Breaking Changes

Lemmy 0.19.0-rc.4 and Development Update - 2023-11-03

We are also readying another release candidate 0.19.0-rc.4. As usual it is available for testing on voyager.lemmy.ml and by installing the Docker image on your server. There are no breaking changes this time as we are preparing for the final release. It has been one month since we announced the major breaking changes for 0.19. In that sense we would like to know from developers of Lemmy clients and frontends if their projects are ready for 0.19, as we are planning to release it within the next weeks. There is no specific release date, but we will first update lemmy.ml to a release candidate, and if it works well publish the new release shortly after.

I didn't get the impresssion that frontend and client devs have signaled that they were ready for a backend update to 0.19.X. And consequently lemmy.ml is still on 0.18.5.

Try deleting site data for lemmy.sdf.org in your browser and log in again. I usually do this after lemmy (UI) updates.

Acttually the issue with outbound federation not properly working is from before they upgraded to 0.19.0-rc4, but 0.19.X made it even worse, because it breaks various clients, e. g. Jerboa, due to some breaking API changes it introduces.

Acttually the issue with outbound federation not properly working is from before they upgraded to 0.19.0-rc4, but 0.19.X made it even worse, because it breaks various clients, e. g. Jerboa, due to some breaking API changes it introduces.

Honestly, this unannounced upgrade to 0.19.X is quite a kick in the butt.

Of course I don't know for a fact that LFG actually checks subgroup 1 to figure out whether a squad's map is full, but it seemed pretty plausible.

Also, I didn't say that map full detection is in any way related to the squad size limit. The question is how does LFG determine whether a squad's map is full? Does it actually check the map of the squad's commander (squad might not have one) or does it check the map of the first player in subgroup 1 (which is what I think).