The Gaming Den

Titles would probably be best.

The marshal still has the "iterative" attack error in its BAB.

Also, do you think adding this other paladin is feasible?

And thanks a lot again.

I have a great number of edits that I would like to share, but an email might be better.

Also, I could just edit the source and recompile and upload to you again... I started learning LaTeX just for this project.

One thing I would say is this: have the page numbers be on the outside edges along the bottom. After printing, it's much easier to flip to a desired page with the numbers along the outside edges (rather than centered). Even numbers go on the left side and odd numbers go on the right side.

In addition, I'm thinking about setting up a version that looks nice in print, IE, removing the hyperlinks to stop them from greying when printed B&W, etc.

If you're going to do a version suitable for printing, maybe you should break it down into the original Tomes, for easier and less wading through all of Frank and K's huge amount of output.

If you want the dissertation about dungeon designs and the insanity of Gygaxian traps in a dungeon, you can just turn to the Dungeonomicon.

The same applies to the Morality section in the Tome of Fiends.

Or whatever.

I disagree. It seems to me that having the feats and classes chopped is an out-and-out disadvantage, and that "Dungeonomicon", IIRC, is a chapter, duly included in the bookmarks. But whatever, certainly one edition can be made from those who disagree with me if there's interest.

*snip*

Nevermind. I had the scatter-brained expectation of...


I dunno what I was thinking. I've been up for about 17 hours straight. Thinking must be happening somewhere.

When I say this, I was thinking, "Oh they crapped it up." but when I actually looked at it, you guys only made it better. I thank you for that to those who did this. I'm excited for this new stuff!!!!

I've been pretty busy lately, sorry. You can go ahead and email me your edits if you want aktariel (morgon dot kanter at gmail dot com), or just do them. Whatever.

When showing people the Tomes for the first time, I usually link them to the board posts to have them read them as they were written. I use the PDF for reference.

I will email you my edits, as LaTeX is a pain to work on on a Mac - hell, LaTeX is a pain period. Oh well. One more markup language to learn.

Expect something hopefully sometime this week (college just got busy near midterms) from aktariel at gmail dot com.

Cheers.

I was wondering were the new classes/ideas for the tome were posted that you guys put in it?

the_unthinkable wrote:I was wondering were the new classes/ideas for the tome were posted that you guys put in it?

Seriously, where did these ideas come from?

what do you mean? Where did the suggestions come from? Where did the classes come from or where did the individual ideas come from?

The suggestions were basically just the creators plugging their stuff, or people who thought highly of it doing so, on this thread.

The classes and such mostly came from the other threads around here, though they can be hard to find.

Ideas came from, far as I can tell, the creator seeing something and saying "That needs to be in D&D" or "That could be done better".

Like when I made the suggestion to include my hellrider class, I suggested it on here, because I liked it and several other people seemed to like it enough to help me refine it. I created it because I had just seen Ghost Rider and thought it would fit very well into D&D(minus the motorcycle, unless gnomes are just that hardcore in your games).

They came from stuff around here that I liked enough and thought well advanced enough to include.

Aktariel, ping! Haven't gotten your email yet.

The contact information should be updated to the new page.

-Username17

Ai'ei. I know, Surgo, my apologies.

I'm working on it, and it's a lot - some of which you may have caught already; I don't know. Nor am I sure of the easiest way to send you the edits.

Life keeps getting in the way.

But that's no excuse, and I will do my best to crank on it and have something to you as soon as I can.

If you're on a linux/mac system, you can use diff, after running a "make clean":

diff -uNr original_source_directory new_source_directory > changes.diff

And email that file to me.

Urrgh.

How do I run a "make clean"? Still feeling out LaTeX... I don't like code.

Just type it at the command line. Literally "make clean".

May be slightly different with Windows.

Using a Mac... by command line, you mean terminal? I've cd'd into the directory with all the files (just straight editing of the source), and I noticed the makefile, but typing "make clean" gets me "-bash: make: command not found."

I'm using MacTex, for the record. Dunno if there's a way to run a compile from there?

Terminal is a unix shell. So... Yes. ^-^

-Crissa

Oh. You might want to install Make, then. I think it's a part of XCode tools.

Yes, I mean terminal.

Alright, I ran a "make clean"... what exactly does this do? I get the output
"rm -f entire.aux entire.log entire.out entire.pdf entire.toc"

...but there are no files called that anywhere on my system that I or Spotlight can find.

Also, running the command you specified (diff) with all of the options you listed, gets me a really big file with lots of extraneous data (about programs in the same root folder, etc.)


Scratch that, never mind. Went into the makefile and looked. Simply commented out the code that removed the files so I can look at the created text.

Still not having much luck with "diff", though.

make clean removes all the compiled files created by running a normal make, leaving only the source files. If the program you used to make the pdf makes different files, you'll want to remove them before calling diff. The reason we were running it was because it would clog up the diff file with all sorts of changes we don't care about (the entire pdf).

The diff problem is more interesting...
diff -uNr: the options for diff on my system are:
-u makes it a unified type of diff
-N means that if there's a new file in one of the directories, create it in the diff (instead of ignoring it)
-r means recursive, descend into subdirectories of the directories given and compare them too.

Make sure those options are the same for your own version of diff (type "man diff" at the command line to see). Also make sure the source files and modified source files are not subdirectories of the other, in either way. So while your current working directory (type "pwd" at the bash shell, terminal, command line, whatever you call it) is directly above the two directories of the source files you want to run:
diff -uNr original_directory modified_directory > changes.diff

All the output we care about should go to changes.diff.


Actually, something I just realized while typing this post -- why don't you just zip up your sources and email them to me. I can run diff myself

Alright. I figured out what the problem was (I think), so I'll send you the diff file later tonight. No worries. Few more small corrections to make, so it might be a little while (after midnight or so).

Plus, if I learn to do all this stuff on my own, then I can be more help to you in the later editions (any plans, by the way? It seems as though most of the bugs have been ironed out, with perhaps a couple more community classes to add, and then periodic updates as new material is created?).

Props to you for being able and having the patience to use LaTeX. Quite the markup language.

ADDENDUM: I can also just rezip my changed source files and send them to you if you want to compile from there, instead of wading through the diff file and making changes manually again. (I only modified two or three TeX files). Probably not, but hey. Just throwing it out there.

The point of a diff file these days isn't just to be able to read what the changes are, but also to automatically reapply them. There's a second program, called "patch", that applies the changes in a diff file to a source tree. So no need to send me the zipped sources -- I can bring mine up to your changes just by running patch.