SRD:Boots of Swiftness

Boots of Swiftness

These shoes grant their wearer a +6 enhancement bonus to Dexterity. The wearer’s speed doubles (this does not stack with any magical or supernatural enhancement to speed), he or she gains the evasion ability (as the rogue class feature), and the wearer’s jumping distance is not limited by his or her height. The wearer gains a +20 competence bonus on Balance, Climb, Jump, and Tumble checks. Three times per day, the wearer can utter a command word to activate the boots’ haste power (as the haste spell, lasts 20 rounds).

Caster Level: 20th; Prerequisites: Craft Wondrous Item, Craft Epic Wondrous Item, cat’s grace, expeditious retreat, haste, jump; Market Price: 256,000 gp; Weight: 1 lb.

Back to Main Page → 3.5e Open Game Content → System Reference Document → Magic Items

**Open Game Content** (place problems on the discussion page).
	This is part of the (3.5e) Revised System Reference Document. 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 SRD 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: Also also, "convention over configuration" being stupid. Yes, the choice of four spaces vs two isn't too significant, but being able to choose means you'll have code you can possibly read a bit more easily, and also public/privateness via *capitalization* just (in my opinion) looks ugly and is annoying if you want to change privacy.

gollark: i.e. generic slices/maps/channels but not actual generics, == being ***maaaaagic*** (admittedly like in most languages, I think), and `make`/`new`.

gollark: Also, as well as that, how it just special-cases stuff instead of implementing reusable solutions.

gollark: e.g. no map function existing or even being possible means that you have *readable* code with a for loop, but it's harder to understand *why that's there* and *what it's for*.

gollark: The main problem I have with it is that it conflates readability (you can see what the code is doing at a low level) with comprehensibility (you know what and why it's doing at a higher one).

This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.