Talk:Great Scythe, Variant (5e Equipment)

Balancing issues

First of all, as it is this is an improved version of an already existing weapon, the Greatsword (it has reach and a benefitial special property). This would be fine if this was a magic item but it isn't. That's the main reason why the needsbalance template is there.

So, in order to make this a somewhat balanced weapon option, it can't step on other weapons, and its distinguising features can't be being an improved version of something else (unless the other weapon is a simple one). Some options for that could be:

  • Leaving it as it is but adding a clause to the special property so that you can't attack creatures witin 5 ft. of you. This would make sense with the design of a war scythe (Though scythes are not really designed for war in the first place). This would distinguish it from the Greatsword and the Lance.
  • Decreasing the damage die to 1d8, 2d4 or something similar. This would keep the weapon in line with a Halberd.
  • Making this primarily a tool that so happens to serve as a weapon, justifying a greater die than the 1d4 for improvised weapons.

Draelm (talk) 04:03, 19 November 2020 (MST)

gollark: Rust's wasm_bindgen stuff.
gollark: … yes? Repeatedly?
gollark: The build tool will just spit out some minimal JS to pass in the necessary browser API calls and invoke your WASM.
gollark: It goes via JS, but you don't have to write that so it is irrelevant.
gollark: It's arguably horrible abuse to do this sort of thing for most applications and it produces giant WASM binaries. Although some languages produce less/more idiomatic JS.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.