User talk:Zackokross

Hi Zackokross, 5e poisons are now at 5e Poisons minus the rules copied from the DMG. You can add new poisons with the "add new poison" button. Thanks! Marasmusine (talk) 12:31, 11 February 2015 (MST)

Wait are the new books not SRD and reference-able? @marasmusine

No, they're entirely under copyright. By the way you can sign your posts with four tildes: ~~~~ Marasmusine (talk) 01:36, 12 February 2015 (MST)

Hi Zackokross, when you make new pages with the "add new" buttons, please can you keep the parenthesis in the title? e.g. Antiquarian‎ (5e Background) rather than Antiquarian‎, thanks. Marasmusine (talk) 01:36, 12 February 2015 (MST)

Hey yea! sorry im kind of new to this and i am always happy for new help and im sorry for everytime i make you do something i feel like i keep you really busy fixing my mistakes Zackokross (talk) 01:41, 12 February 2015 (MST)

Handy Reference Guide

Hello Zackokross! Welcome to the dandy- er- D and D Wiki! I saw that you asked for a reference guide for wiki coding on a talk page. So, I'll give you a hand! I'm just a nice guy like that.

(Note that all of this is, though rather indirectly, available via the various reference pages, which direct you to Wikipedia's guides, which are fairly extensive. This is a condensed version of the most basic stuff you'll likely use at this wiki.)

Titles

All you need to do to learn these tricks is hit edit and see how it was done. Most of it is really simple. Notice that text is handled in strings, not lines. Word-wrap, as is encountered in web browsers, allows a string to be multiple lines long. This wiki treats new strings differently than most code. Normally, a line break is irrelevant. It's just treated as another character in a single very long string of text. Thus, it only matters if it would interrupt a command. Normally, to start a new line you'd need to command a line break, but this wiki shortcuts it by simply skipping a line...

Like so.

Text Editing

You're probably going to want to bold and italicize text from time to time, especially with the way 5e formats information in the corebooks. That's simple enough. Simply bracket the text of interest with apostrophes.

Two apostrophes gets you itallic.

Three gets you bold.

Posting

As has been mentioned, you are expected to sign your posts using four tildes ~~~~ or by just pressing the sig button with your cursor in the right place.

It's also courtesy to indent your replies to specific posts by preceding the line with a colon. This gives the impression of nested comments.

Note that starting a new line in any way will interrupt the indent command, or any other preceding line command.

Theoretically, you can continue nesting replies indefinitely.

In practice however, there is a limit imposed by screen resolution.

Eventually comments can become awkwardly squished against the far side of the page, necessitating the process be renewed somehow.

Because everyone has different screen resolutions, there is no way to know when the limit has been hit for someone unless it is stated.

For example, I browse almost exclusively by cell phone. Six colons is about my screen limit before things start to look goofy.

My computer can go up to 15 though!

Lists

Preceding a line with an asterisk (*) gets you an indented line with a bullet.

• Like this.
• Notice how a * in midstream won't be taken as a command.

• You can mix these preceding commands to create indented points.

• • Or pointed points! Though these take up a lot of space.

1. You can also make numbered lists
2. The page will keep track of a numbered list except...

For example...

1. When something's in the way.

I don't know how far you can nest titles...

... But I think they all just show up as bolded text after the 5th level. They will still continue to be nested in the automatically generated menu at the top of the page though.

You can also use html if you know it, but it's considered rather impolite and tends to break stuff unless you're very careful.

To make a link to an article on this wiki, encase the page's full name, not its url, in double [[square brackets]]. This is very specific; even capitalization should be correct. If you want the link to say something else, follow the page name with a bar, then the text you want linked, within your brackets. For example, here is a link to our lovely guide on tables! Tables can look complex and threatening when you're editing a page, but they're actually simpler than html here. You should give that page a browse.

Nice to meet you. Kydo (talk) 08:07, 15 February 2015 (MST)

Hey kydo!

I would like to thank you and tell you exactly how much i appreciate the time you took to show me all of this! A lot of what i learned into going to the edit option for a page and seeing how they did it and mimicking the code they used. but this has been incredibly helpful and i always like to see others opinions on things ... usually i like others opinions more so then my own so at any time feel free to post what ever you feel on any of my stuff if you wish something should change, from what i have seen your an incredibly ingenious writer and i like what you have posted.

The Happy Newb Zackokross (talk) 23:57, 16 February 2015 (MST)

"You can also use html if you know it, but it's considered rather impolite and tends to break stuff unless you're very careful." Exactly what do you mean its considered rather impolite?? Zackokross (talk) 23:59, 16 February 2015 (MST)

Mainly it's because not every one can use it. Also, because html can all be written as a single giant string, many people organize the code differently. It can appear confusing and hard to read. And, because you have the wiki doing its own interpretation on top of the html, you can get some unexpected results from time to time. Finally, by sticking with wiki commands, you ensure your work is in the correct format and style for the wiki.Kydo (talk) 09:24, 17 February 2015 (MST)