OGC:Misalignment (5e Variant Rule)
Misalignment
Barrel chain rifles and harmonica guns suffer a special kind of misfire. When the bullet is not properly aligned, whether due to forgetting to lock in a barrel or misaligning the slide, then the creature risks damaging the gun and itself. When it rolls a 1 on its attack roll, the barrel is considered cracked (as per the disadvantaged misfire rule) and the creature takes 1d4 damage from powder and shrapnel released by the explosion.
Back to Open Game Content → Variant Rules
Back to Main Page → Publication List → Publishers → EN World → EN Publishing
 | Misalignment from EN Publishing, © 2017, EN World; Author Various Authors, based on original material by EN Publishing. It is covered by the Open Game License v1.0a, rather than the GNU Free Documentation License 1.3. To distinguish it, these items will have this notice. If you see any page that contains Open Game License v1.0a material and does not show this license statement, please contact an admin so that this license statement can be added. It is our intent to work within this license in good faith. | |
gollark: Oh, and it's not a special case as much as just annoying, but it's a compile error to not use a variable or import. Which I would find reasonable as a linter rule, but it makes quickly editing and testing bits of code more annoying.
gollark: As well as having special casing for stuff, it often is just pointlessly hostile to abstracting anything:- lol no generics- you literally cannot define a well-typed `min`/`max` function (like Lua has). Unless you do something weird like... implement an interface for that on all the builtin number types, and I don't know if it would let you do that.- no map/filter/reduce stuff- `if err != nil { return err }`- the recommended way to map over an array in parallel, if I remember right, is to run a goroutine for every element which does whatever task you want then adds the result to a shared "output" array, and use a WaitGroup thingy to wait for all the goroutines. This is a lot of boilerplate.
gollark: It also does have the whole "anything which implements the right functions implements an interface" thing, which seems very horrible to me as a random change somewhere could cause compile errors with no good explanation.
gollark: - `make`/`new` are basically magic- `range` is magic too - what it does depends on the number of return values you use, or something. Also, IIRC user-defined types can't implement it- Generics are available for all of, what, three builtin types? Maps, slices and channels, if I remember right.- `select` also only works with the built-in channels- Constants: they can only be something like four types, and what even is `iota` doing- The multiple return values can't be used as tuples or anything. You can, as far as I'm aware, only return two (or, well, more than one) things at once, or bind two returns to two variables, nothing else.- no operator overloading- it *kind of* has exceptions (panic/recover), presumably because they realized not having any would be very annoying, but they're not very usable- whether reading from a channel is blocking also depends how many return values you use because of course
gollark: What, you mean no it doesn't have weird special cases everywhere?
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.