Giter VIP home page Giter VIP logo

apathyrpg's Introduction

apathyrpg's People

Watchers

James Cloos avatar  avatar

apathyrpg's Issues

Text formatting error in section 1.6.1 (Attribute checks)

The actual "rules" text in section 1.6.1 is currently formatted as part of 
example 7, rather than being its own seperate paragraph.

The second paragraph in Example 7, secion 1.6.1 should be removed from 
the "example" indent and made part of the main section.

Original issue reported on code.google.com by [email protected] on 18 Jul 2008 at 4:51

Erroneous formatting in Firearms tables

The Firearms tables have some incorrect formatting.  There seems to be a
"kind" column label added into these tables which shouldn't be there.  The
"kind" label displaces the other labels.

Original issue reported on code.google.com by [email protected] on 7 Jul 2008 at 10:40

Removal of unique equipment and items

Remove unique items/weapons/etc from the document.  Here are those that I
have spotted so far (but may not be all-inclusive)

Ajax's Deadly Grasp (armor, p 78)
Gentleman's Vest (armor, p 79)
Toad Armor (armor, p 80)
Boxing Irons of the Troll (p 88)
Gloves of Anointing.... (p. 88)
Belt of Leaves (p. 101)
Blue ribbon of faggotry (p. 101)
cloak of stealth (p. 102)
Cordelian Belt of the Warrior (p. 102)
Ring of daylight globe (p. 104)
Satan's Stopwatch (p. 104)
sharkskin gloves (p. 104)
Tao Teih Pendant (p. 104)

again, there may be others but these are what I found while proofing.

Original issue reported on code.google.com by [email protected] on 7 Jul 2008 at 10:32

1.0 Milestone

Redesign the Tools/Builder.py to allow for closer control of content. That
is, mark content by time-period and allow for time-period selection, etc.
Redesign the builder to actually use the Table information for
class='category'.

Original issue reported on code.google.com by [email protected] on 12 Jul 2008 at 7:52

Errors in the Ammunitition section (3.1)

1)  Perhaps add a text blurb to explain that this section describes 
projectiles used for Bows, crossbows, blowguns and similar weapons.

2)  There are two entries in the chart for the same thing:  "Bullet Point" 
and "Bullet Point (blunt-target)".  These are the same thing.  How to fix:

Take the text description from "bullet point (blunt target)" and move it 
to Field Point.

Delete the row for "bullet point (blunt target)".

Original issue reported on code.google.com by [email protected] on 18 Jul 2008 at 5:05

Ammunition table errors

The table for Ammunition (pg. #65) is screwed up.  There appear to be extra
"phantom" entires and various errors in the table.  Specifically:

a)  The Row entitled "Bullet Point" contains no data.  However the next row
"Bullet Point (blunt-target)" contains correct data.  These need to be
merged into one row.  The description that is currently listed under
"bullet point blunt target" is actually the description for the Field Point.

b)  similarly, the row entitled "Explosive" contains no data.  However the
following row (Explosive point) does contain correct data.  Again, these
need to be merged into one row.

c)  Same problem for the "fire arrow".

Original issue reported on code.google.com by [email protected] on 7 Jul 2008 at 10:34

Error in "lift" sub-attribute calculation equation

In table 1.3 (Sub attributes) the equation for "lift" is incorrect.

It should be (STR^2 * BLD)/10


Also, this may not be an error per se, but the font sizes for the 
computation equations are not consistent.  for Hit Points and Magic Points 
the fonts are larger than those used in the other equations.

Original issue reported on code.google.com by [email protected] on 18 Jul 2008 at 4:46

Enhancement

What steps will reproduce the problem?
1. Read the manual
2. ??
3. Lose

What is the expected output? What do you see instead?
Awesome

What version of the product are you using? On what operating system?
Fuck me.

Please provide any additional information below.
The point pool section are brok0rz.

-Yo

Original issue reported on code.google.com by noah%[email protected] on 19 Jul 2008 at 11:42

Strange ordering of items in the Equipment section

This is an organizational issue.  The order in which items are listed in 
the equipment chapter is strange.

The current order is:

Ammunition (bows, etc)
Shields
Melee weapons
Misc. (everything from warhorses to rope to skillets)
ranged weapons
shields (again--this is a duplicate table which can be deleted)

I suggest reorganizing this as follows:

Melee weapons
Ranged Weapons
Ammunition
Armor
Shields (the first section, which is correct)
Misc. Equipment


Original issue reported on code.google.com by [email protected] on 18 Jul 2008 at 5:09

Attribute Table

http://docs.google.com/Doc?id=dd2hffsx_119cskffxcq&btr=EmailImport

See the attribute table (around page "6")

Original issue reported on code.google.com by [email protected] on 27 Jun 2008 at 11:35

Add rank and attribute data to the list of academic skill descriptions

Currently the academic skill data is split.  The table at the beginning of 
the skill section (beginning of Chapter 2) contains the skill name, rank, 
attribute, and examples of occupation.

The actual descriptions of the skills which follows that table contains 
the name and description only.  That means one has to flip back and forth 
to get all the data.

I suggest that the rank and attribute appear alongside the name of the 
skill in the list of skill descriptions.

For example, it might go like this:



Acrobatics   Rank 2 DEX

The ability to perform....

Original issue reported on code.google.com by [email protected] on 18 Jul 2008 at 5:01

Missing and disorganized Shield data

Section 4.2.2 contains text describing sheilds.  This text is correct but
it needs to be listed alongside the requisite tables.  Those tables are in
the document (p. 114-115) but they are located nowhere near 4.2.2.  Move
content so that the text in section 4.2.2 is just before said tables.

Also, check the table data against the second page on armor.xls to make
sure all data is present.

Original issue reported on code.google.com by [email protected] on 7 Jul 2008 at 10:36

Attachments:

Formatting in section 1.7.11 for clarity

Formatting in Section 1.7.11 (cover, pg. #41).  The two options a character
has for dealing with a covered target should be marked in bold or in
distinct paragraphs, etc.  One is "Attempt to strike around cover", the
other is "Attempt to strike through cover".  (I have marked this in bold,
you may wish to change it if you don't like that)

It was a bit difficult to read without doing some kind of reformatting.

Original issue reported on code.google.com by [email protected] on 7 Jul 2008 at 10:43

Errors in the Skill list

Several academic skills have their attribute showing up 
as "implementation" rather than their correct attribute.

Examples:

Cash
Diplomacy
Falling
Mysticism

Original issue reported on code.google.com by [email protected] on 18 Jul 2008 at 11:19

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.