Auto Turret (D20 Modern Equipment)

Auto Turret

When this is activated (a standard action), it transforms into a turret that floats about three feet from the ground and fills one 5 ft. square. The Auto Turret cannot move and cannot be used by any creature or character. The Auto Turret automatically fires one shot each round at all creatures and characters that are not allied to the creature or character that activated it within 80 ft. of the turret. The auto turret has an attack bonus of +5, deals 2d8 damage, and has a range increment of 30ft. The auto turret can be destroyed: it has a hardness of 8, 30 hit points, and an AC of 10. The turret can be deactivated by the creature or character that activated it, or by one of his allies. In this case, it folds up to original size and can be reactivated as normal.

An auto turret has a purchase DC of 40, with a restriction of Mil (+3), and weighs 10lbs.

Back to Main Page → D20 Modern → Equipment
Back to Main Page → D20 Modern → Campaign Settings → Halo → Equipment → Items.

This page may resemble content endorsed by, sponsored by, and/or affiliated with the Halo franchise, and/or include content directly affiliated with and/or owned by Microsoft Studios. D&D Wiki neither claims nor implies any rights to Halo copyrights, trademarks, or logos, nor any owned by Microsoft Studios. This site is for non profit use only. Furthermore, the following content is a derivative work that falls under, and the use of which is protected by, the Fair Use designation of US Copyright and Trademark Law. We ask you to please add the {{needsadmin}} template if there is a violation to this disclaimer within this page.
gollark: Nope. It runs over TCP.
gollark: Better than what? For what?
gollark: I don't see why you would want to stuff your entire request body in headers when there's a perfectly good request body system.
gollark: Primarily that some things won't be happy with it because nobody does it. Other than that:- servers may allocate limited-sized buffers for incoming request headers so you can't put too much in them (this is somewhat problematic for cookies)- headers have character set limits while bodies can be arbitrary bytes- request bodies are generated by forms and all sane clients so stuff is mostly designed to deal with those- request bodies can probably be handled more performantly because of stuff like the length field on them
gollark: In HTTP, you mean?
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.