Tag: ip

“Stolen Game”?!?! Upper Deck Sues Ravensburger and Miller #UpperDeck #Ravensburger #TCG #game #gaming #law #iplaw #lawsuit @UpperDeckEnt @RavensburgerNA

FrylockLeave a comment

If you enjoy this post, please retweet it and/or boost it.

Upper Deck (“UD”) sued a former employee, Ryan Miller (“Miller”) and a competitor, Ravensburger North America, Inc. (“Ravensburger”) over a “stolen game.” If you’ve ever read this blog, you know that game rules can’t be copyrighted. They can be patented, so UD’s claim that their game was “stolen” may prove correct. I’m going to try to answer the questions that people have addressed to me.

Facts

Briefly, UD employs Miller to design a trading card game (“TCG”). Miller sings an employment contract that contains a nondisclosure provision. Miller leaves UD, joins Ravensburger, and designs a similar game there. UD’s game hasn’t been released, but Ravensburger has publicly shared their ruleset for playtesting at conventions and has sold packs of cards for it (or so the complaint alleges).

I’m just going to deal with the intellectual property law issues because the question that everyone seems to be asking (me) is one related to IP: Is this a valid basis complaint in the first place? That’s a question I can answer without knowing both sides of the story. That is, I can’t say who’s right and wrong, but I can opine as to whether or not the philosophical basis of the suit is valid.

Trade Secrets: The Forgotten IP

Part of this case falls under trade secret law, which I address in this post covering all forms of IP. The defendant’s employment contract had a non-disclosure/secrecy provision, and that’s the basis of the suit. Game mechanics can be protected under trade secret law, which basically says, “Don’t tell anyone what we’re doing,” or “Don’t tell anyone how we do what we do.” This is very much unlike copyrights because copyrights often have little to no value unless they’re made publicly available. Trade secrets are valuable because they’re kept secret. One of the most valuable trade secrets in the world is the formula for Coca-Cola. If it were patented, it would be published, and thus have at most 17 years of protection. Instead, they keep it secret, so it has value for as long as it remains so. That’s an important point: Once a trade secret is made public, it can no longer be a trade secret. You can sue someone for publishing it, but you can’t put the genie back in the bottle. Once it’s out there, it’s no longer protectable. Ever.

So, the defendant in this case was (allegedly) bound by contract not to share the mechanics until after they were released by UD. It’s reasonable to infer that Miller must have shared those trade secrets when designing a game that was remarkably similar to what he did with UD. Miller and Ravensburger could argue that the similarities are ones shared by all card games, and so none of them are trade secrets. The complaint details the game mechanics, but I haven’t really read through them, so I can’t evaluate that defense.

Of course, even if those mechanics are identical to other games, this may not get the defendants off the hook. Games have several elements, so the difference between most games is essentially which specific combination of known elements you’ve chosen for your game. That combination may be unique. Even if not patentable, it may be marketable, and thus have value. If, for the reasons stated above, the sharing of that combination hurt UD’s market for the game, there’s still a lawsuit to be had.

You might ask, “How would it hurt the market?” Well, think about it. Games have limited shelf lives. Their first push in the market is often where they make their most money. If someone learns of your game system and publishes a quick-and-dirty version of it first, they’ll grab most, if not all, the market before your more well-designed version even gets there. Maybe you’ll enjoy a secondary push in a few years, but you’ll still have lost that first market. Also, the first game company to get their game to market can always accuse the other company of plagiarism. As for patent infringement, depending on the timing, a game company could actually lose their ability to patent a mechanic because the mechanic was published long before the application was filed. There are time limits on these things, so it’s best to keep your designs secret.

Patents

Of course, as I mentioned above, UD filed for a patent in April, 2023. I have no opinion as to whether that will be granted. Even after I eventually read through the game mechanics, there’s a lot of “prior art” (i.e., existing games) I’d have to analyze to form an opinion, and I’m not going to do that. I don’t play TCGs. Even if I did form an opinion, patent law is a tricky thing. There are very few obviously good or bad patents. My opinion wouldn’t mean squat; we’d have to wait for a judge’s decision, and then an appellate court’s opinion before we get a real answer. Either way, claiming that the game was stolen is at best premature. That’s not to say I don’t understand why UD is saying it. I’m simply acknowledging the basis for your confusion by that claim.

There’s far more to consider here than I could possibly address. I lack information and the desire to dig any deeper at the moment. The takeaway here, though, is that game mechanics can absolutely be protected by trade secret until they’re published. If the trade secrets are deemed valid, their publication by Miller and Ravensburger would constitute a legitimate cause of action for UD. We’ll just have to wait and see whether it sticks.

I’ll continue to go through the complaint and provide more information as I learn it (if it’s interesting). For now, back to work I go.

Follow me on Twitter @gsllc
Follow me on Mastodon @gsllc
Follow Upper Deck Entertainment @UpperDeckEnt
Follow Ravensburger North America @RavensburgerNA

WotC’s New Stat Block Format @Erik_Nowak @Wizards_DnD #copyright #DnD #RPG #5e

Frylock2 Comments

If you enjoy this post, please retweet it.

I had a discussion during Winter Vantasy: The Return with Erik with respect to Wizards of the Coast’s (“WotC”) new stat block format. The new stat block has some rearranging of material, but that wasn’t the subject matter of the conversation. We were discussing the removal of spells and spell-like abilities from the new WotC stat block. Erik doesn’t like it and referenced my concerns about the complexity within the current stat block format. Erik referred to my position as “ridiculous,” but WotC’s switch proves that Erik’s view is the minority one. I didn’t have a large enough internet footprint to prove it on my own. More importantly, however, Erik understandably mischaracterized my position. I wasn’t saying that the Monster Manual got it wrong. In fact, quite the opposite. I’ve mentioned before that I think it’s the best RPG bestiary I’ve ever read. My concern is that WotC didn’t supplement it properly, then attempted to shut me down when I did.

Important Note: I’m not 100% certain that WotC’s stat blocks have been changed in the way we’re all assuming they were. I’ve seen a sample of the new format (below), but it was for a low level creature whose stat block would be simple anyway. Thus, this discussion comes from a place of partial ignorance, and I may get some things wrong. Take this all with a grain of salt.

When you look at a complex stat block (e.g., Mummy Lord), unless you have a truly eidetic or nearly eidetic memory, there’s no way you can effectively run that stat block as written, especially if the encounter is a combat encounter. There’s too much going on, and what we’ve all seen (and I actually got Erik to admit to an extent!) is that every DM just gives up and resorts to using the common spells they all know: Magic Missile, Hold Person, Fireball, Counterspell, etc., even for higher spell slots. Why? Well, first you must figure out which sourcebook contains the spell in order to look it up. If it isn’t a Player’s Handbook spell, you may not know, so you wind up searching through a couple of books before finding the correct one. Second, you must read the spell, which could take a while if it’s not one like Fly. If it were a spell like Fly, you may not have to look it up at all, which is why Fly is one of the spells to which DMs eventually resort. Something like Control Weather has far too much going on for most people to memorize. Erik is sometimes willing to do that, but there are very few players whose eyes don’t glaze over with boredom during that long process. Moreover, if you’re playing with a real-world time limit (e.g., convention play), that’s certainly not time you have to waste. At the table, the spell’s details should be right in front of your face. I don’t understand why anyone would disagree, and those with eidetic memories shouldn’t care one way or the other.

That said, in theory these stat blocks provide a framework for the culture of that creature. (In my second stat block/copyright post, I mathematically proved that WotC fails to do so, but that’s not relevant here.) So, the Monster Manual itself shouldn’t eliminate that complexity (I know; WotC can’t win with me), but rather use it as a framework for creating specific monsters within that cultural framework but suited to the encounter at hand. That last sentence is a tough read, so here’s an example. (I’m going from my memory, which is not eidetic.) The Couatl has both offensive and divination spells. If your encounter involved the Couatl using Detect Thoughts to aid in an interrogation, then you wouldn’t need the Couatl to have Shield. On the other hand, that position would be reversed if the Couatl were to engage in combat against the PCs (i.e., it would need Shield but I don’t think, from memory, Detect Thoughts would have value). The Monster Manual stat block provides you the spells a Couatl needs for all situations, but not every Couatl will appear in all situations. In fact, I doubt any will unless the Couatl is a PC, but a Couatl PC is clearly not what I’m talking about. For NPCs at the table, you need only the spells that that specific NPC will need in that specific encounter. Everything else muddies the water. However, it’s good that all situations are covered by the general stat block in the Monster Manual, because that’s what you use to build such table-based stat blocks.

So, in my ideal world, this is how WotC (or any game designer with sufficient resources) should approach their stat blocks. Make them as complex as WotC did in the Monster Manual, using only spell names as shorthand to make the stat block printable, but modify their online tools with check boxes allowing DMs to pick which spells and spell-like abilities appear on a final stat block at the table (whether in hard or soft copy). For that final stat block at the table, make sure that the spell descriptions are presented fully so that there’s no need to resort to multiple hardcopy resources to know details that are relevant to the combat, but at the same time make sure that the stat block isn’t cluttered with irrelevant details. If there are no online tools, provide one-stop stat blocks for all NPCs (as I did) as a PDF. They could also provide PDFs containing generic spell entries with coded placeholders such as, “Magic Missile, Atk: [L]+3+IntMod, . . . .” (or whatever it is), so that DMs could copy and paste them into their own stat blocks as needed. All my project did was the one part of that process that I could, which is something WotC didn’t do.

I fully appreciate that some (most?) game designers can’t do this. Online tools are a huge investment of time and resources they may not have, but some in the gaming community do. Game designers simply need to stay out of the way and allow the community to do that heavy lifting for them. On the other hand, WotC has both the time and resources to create this ideal that appeals to the most people, but they’re still getting it wrong, probably because there’s more profit in selling a new hardcopy (which I suspect will be very good nonetheless).

So yeah, WotC can’t win with me, but only because they’re choosing to lose. We’ll see how the final product shakes out.

Follow me on Twitter at @gsllc
Follow Dungeons & Dragons @Wizards_DnD
Follow Erik Nowak @Erik_Nowak

Dungeons & Dragons is a trademark of Wizards of the Coast, LLC, who neither contributed to nor endorsed the contents of this post. (Okay, jackasses?)