bam13302
“Oathbreakers” are evil, by definition, “oathbreakers” are not. A oath of conquest paladin that broke their oath for good reasons, would be more suited for a oath of redemption.
Could be worse, could be this https://scp-wiki.wdfiles.com/local--files/scp-4971/biphi2.png
IRL letal damage is rarely immediately lethal, which is a fact not translated well into the game. The fact he went to the ER is a good sign that it very easily could have lead to death for someone without medical aid.
Also by biting the arm instead of say, the neck, is pretty clear it was a declared non-lethal attack
Wish is an easy one, since it can be used to cast most of the other spells talked about here
Clone, immortality without any of the normal downsides (I can choose to die still and don’t need souls or any bs like that)
Identify and go pawn shop hunting and the like
Really most divination spells would be solid for stock market manipulation
Enchantment spells for manipulating the corporate ladder, or getting into politics or something (mass suggestion in the really any political nexus, geus for more targeted things, modify memory, etc).
Healing and revivification spells and sell my services to the elite, bring back the dead, speak to loved ones, etc. Clone works well here too, especially since it has age manipulation.
How the hell did you find that 4th picture. Who would even do that?!?
The problem is really that space is an argument separator, so to safely handle filenames with spaces you need to handle them special, either by escaping them, quoting the entire thing. This means that the filename with spaces can’t be just copy pasted wherever you want, you have handle them special. It adds complications that are resolved by just using a separator that isnt used for other things, like underscore, or dash. Dot I also don’t like as much as it’s used as a separator for extensions, but that’s a far easier problem to handle by just ignoring all but the last dot, leaving only one really bad edge case (a file that does not have an extension, that uses dot separator in its filename having the filesystem imply a wrong extension.
for f in *.txt; do cat $f; done
Will error for example. It works fine for filenames without space, but if the filename has space in it, it will be interpreted wrong. But if your testing batch doesn’t have spaces in the filename, you won’t see the issue until it’s used on a file that does. Note ‘cat’ is a placeholder, any function/script that can be used on a file here will have the same issue.
Something similar to that caught me last week while I was unzipping multiple mods in bulk for a game.