this post was submitted on 22 Sep 2023
122 points (93.0% liked)

Games

16557 readers
812 users here now

Video game news oriented community. No NanoUFO is not a bot :)

Posts.

  1. News oriented content (general reviews, previews or retrospectives allowed).
  2. Broad discussion posts (preferably not only about a specific game).
  3. No humor/memes etc..
  4. No affiliate links
  5. No advertising.
  6. No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
  7. No self promotion.
  8. No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
  9. No politics.

Comments.

  1. No personal attacks.
  2. Obey instance rules.
  3. No low effort comments(one or two words, emoji etc..)
  4. Please use spoiler tags for spoilers.

My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.

Other communities:

Beehaw.org gaming

Lemmy.ml gaming

lemmy.ca pcgaming

founded 1 year ago
MODERATORS
nanoUFO@sh.itjust.works
122
Unity: An open letter to our community (blog.unity.com)
submitted 1 year ago by nanoUFO@sh.itjust.works to c/games@sh.itjust.works
31 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] conciselyverbose@kbin.social 3 points 1 year ago

It would have been perfectly fine if they did it this way to start. Tie the new licensing costs to a future engine version, give lead time before you start collecting data, and have the number be manageable.

But trust in such an absolutely critical vendor that your entire business relies on, and they told you they're perfectly fine trying to retroactively change contracts. The uncertainty of legal costs to protect your rights is a huge concern.