m (1 revision: SRD upload) |
(I am using Visual Studio 2010 and MVC2. I created a MySql daabtase with a sql script in MySql Workbench. I have Connector/Net 6.3.3 beta 2. I added a new item to create an ADO.Net Entity Model from the for the MySql daabtase. The resulting mod...) |
||
Line 40: | Line 40: | ||
For purposes of [[SRD:Weapon Proficiency|weapon proficiency]] and [[Category:Chosen Weapon Feat|similar feats]] , a composite longbow is treated as if it were a [[SRD:Longbow|longbow]]. |
For purposes of [[SRD:Weapon Proficiency|weapon proficiency]] and [[Category:Chosen Weapon Feat|similar feats]] , a composite longbow is treated as if it were a [[SRD:Longbow|longbow]]. |
||
+ | I am using Visual Studio 2010 and MVC2. I created a MySql daabtase with a sql script in MySql Workbench. I have Connector/Net 6.3.3 beta 2. I added a new item to create an ADO.Net Entity Model from the for the MySql daabtase. The resulting model had lower case names for all of the tables in the diagram. I looked an saw that this probably comes from the fact that the Table names in the MySql daabtase are also lower case. Note from my previous comments I am generating with the MySql tt file from Visual studio all use upper case names also. Somewhere in the process, the table names which begin with an upper case first letter are going to all lower case names. This is more a pain in the neck than anything else since I have to modify the names in the edmx diagram in oder for compatability with existing code. However, I am reporting this as a problem because it might make it hard for some people to migrate from Sql server to MySql. I'd think that is one of your goals. |
||
− | ===Enhancements=== |
||
− | |||
− | {{Weapon Material Enhancements |
||
− | |weap=Composite Longbow |
||
− | |material=Wood |
||
− | |cost=100 gp |
||
− | |mwkcost=400 gp |
||
− | |hard=5 |
||
− | |hp=5 |
||
− | |dwcost=430 gp |
||
− | |dwhard=5 |
||
− | |dwhp=5 |
||
− | |dccost=1,100 gp |
||
− | |dchard=10 |
||
− | |dchp=15 |
||
− | |mchard=8 |
||
− | |mchp=12 |
||
− | }} |
||
− | |||
− | {{Magical/Psionic Weapon Enhancements}}<noinclude> |
||
===See Also=== |
===See Also=== |
Revision as of 11:44, 20 November 2012
This material is published under the OGL |
| |||||||||||
Size | Cost1 | Damage | Weight1 | hp | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Fine | * | 1d2 | * | 1 | |||||||
Diminutive | * | 1d3 | * | 1 | |||||||
Tiny | * | 1d4 | * | 1 | |||||||
Small | 100 gp | 1d6 | 1-1/2 lb. | 2 | |||||||
Medium | 100 gp | 1d8 | 3 lb. | 5 | |||||||
Large | 200 gp | 2d6 | 6 lb. | 10 | |||||||
Huge | * | 3d6 | * | 20 | |||||||
Gargantuan | * | 4d6 | * | 40 | |||||||
Colossal | * | 6d6 | * | 80 | |||||||
|
Description
You need at least two hands to use a bow, regardless of its size. You can use a composite longbow while mounted. All composite bows are made with a particular strength rating (that is, each requires a minimum Strength modifier to use with proficiency). If your Strength bonus is less than the strength rating of the composite bow, you can’t effectively use it, so you take a –2 penalty on attacks with it. The default composite longbow requires a Strength modifier of +0 or higher to use with proficiency. A composite longbow can be made with a high strength rating to take advantage of an above-average Strength score; this feature allows you to add your Strength bonus to damage, up to the maximum bonus indicated for the bow. Each point of Strength bonus granted by the bow adds 100 gp to its cost.
For purposes of weapon proficiency and , a composite longbow is treated as if it were a longbow.
I am using Visual Studio 2010 and MVC2. I created a MySql daabtase with a sql script in MySql Workbench. I have Connector/Net 6.3.3 beta 2. I added a new item to create an ADO.Net Entity Model from the for the MySql daabtase. The resulting model had lower case names for all of the tables in the diagram. I looked an saw that this probably comes from the fact that the Table names in the MySql daabtase are also lower case. Note from my previous comments I am generating with the MySql tt file from Visual studio all use upper case names also. Somewhere in the process, the table names which begin with an upper case first letter are going to all lower case names. This is more a pain in the neck than anything else since I have to modify the names in the edmx diagram in oder for compatability with existing code. However, I am reporting this as a problem because it might make it hard for some people to migrate from Sql server to MySql. I'd think that is one of your goals.
See Also
- SRD:Weapon Qualities
- Magic Items: Weapons (SRD Rules)
- Wikipedia: Longbow
- Wikipedia: English Longbow
- Wikipedia: Bow
Back to Main Page → System Reference Document → Weapons