Kayana

Actually, I wouldn't be surprised if screenshots are disabled in that app considering the rest, to "stop leaking sensitive information".

Danke für den Tipp, muss ich mir mal gerade einen Bericht mit Namen "niemand" erstellen und Maimais pfostieren, damit er in Betracht gezogen wird...

Huh, TIL.

Regarding your edit, that amount wasn't the cumulated cost of whatever Limewire were distributing, that would be idiotic indeed; rather the RIAA tried to call for a ruling that somehow those guys were causing $150,000 in damages - per instance. Now the article unfortunately doesn't state how they possibly tried to justify that number, and I can't be bothered to research that myself. Another thing that would interest me is how the plaintiff expected them to pay with almost every dollar on Earth.

So while I don't think this had anything to do with "lost sales", I do agree with the possible fines and damage calculations not being fit for any sort of realistic purpose at all.

Because I didn't know absurdism, I read the second one differently at first:

[The] nothing matters.

And I immediately had to think of this gem:

"But it doesn't do anything!" - "No, it does nothing."

I don't think I understand what you mean, might be because we're both ESL.

Are you saying you want a histogram or something about how points can be spent, instead of how players do spend them?

Hmm, you'd probably have to have access to something like DndBeyond's data to compile such a chart (or use one they compiled). Problem is, there doesn't seem to be anything like that. The only published data visualisations are about races, classes and names.

So I don't think you can just search for it, the only other option I see is gathering that data (if from a smaller sample) yourself, by creating a poll asking for their ability spreads if they used point buy. You could try and advertise it in appropriate communities, and once you feel like your sample size is big enough, you can calculate the percentages.

I wish there was an easier way (and maybe there is and I just didn't look far enough), but from my chair, that's the only option.

Point buy is completely deterministic, so I'm not sure what you mean by probabilities... Are you referring to statistics, like which stat is a certain value most of the time?

Well, one way to easily replicate point buy's range per stat (if not its distribution limit over all stats) would be 7 + 1d8. You could also do: Start every stat from 12, and if you want to increase one, you can do so by rolling a d4 as a bonus (rerolling on a 4). However, to do that you'll have to decrease a different one by another / the same d4. So you'll still have the same range, but like with point buy there's an element of control and choice to it.

Regarding bigger ranges, one way could be using that same method, only with bigger dice (and possibly other starting points). E.g. you could start from 11 and roll a d8, rerolling an 8 if you're adding it as a bonus. That example would give you values anywhere from 3 to 18, and it's much more swingy than 4d6dl. Of course, if the high variance is an issue, you can experiment with dropping highest or lowest on 2d8.

For example, if you're dropping lowest on bonus rolls and penalty rolls, you'll get characters with high highs and low lows, or if you're doing it the other way around, you'll get characters where each stat is fairly equal, without much variance to speak of.

There isn't much more I can say without knowing how much variance and player choice you want to include.

Sollen das Temperaturen sein? Erinnert mich an diesen Edelstein.

Mein Straßenverkehrsamt tendiert dazu, bei Leuten mit nur einem Namen in ihrem (bspw. indischen) Pass einfach den Namen als Vor- und Nachnamen zu nehmen, sodass bei ihnen dann auf dem Führerschein steht... Nur, weil die deutsche Bürokratie nicht mit nur einem Namen klarkommt.

Wow, writing the same paragraphs three times... What an abomination of an article.

Late reply, but for me personally, I started doing it because my Keepass database is already accessed using two factors (password and key file). Therefore, I'd gain very little by keeping the second factor of those sites external - essentially, those second factors are compounded into the second factor for the database.