#reference tables

[stone-cold-groove]

Reference tables. My First Picture Dictionary - 1962.

[jazminetoad]

One Piece Isekai Adventure

Created by Tekking101

Grab your D&D dice as you'll be rolling for results.

Now, the Isekai fairy (which looks like whatever your type is) appears to bring you into the One Piece world. You are allowed to bring-

Two sets of outfits

One item of your choice

And whatever you're wearing on you right now

You will be given-

1 million beris

A backpack

Unfashionable winter clothing (optional)

And a random item (roll a D100, the number you get is the item you will receive)

The time you appear in the One Piece world is the exact time Luffy sets sail to begin his adventure

Now roll a D6 to see what sea you end up in

If you end up in any of the blues, roll the appropriate die for which island you end up on

If you ended up in Paradise or the New World, roll a D20 for which island you end up on

The following table is your object and you must complete it if you wish to return home (of course even if you do complete it you can stay, you just now have an escape route) Roll a D8

If you wish to take your chances for an extra benefit, you can roll on the risk table but it is optional (Roll a D8)

And now you're ready and in the One Piece world!

With these reference tables you could end up in any situation, sometimes you can choose your path, other times the path chooses you

[moredungeonsforyourdragons]

Reference Tables (1)

Buenos! In this post, I’m going to link two pages of reference tables that I use almost every time I run a campaign. 

These are the tables. Many of them are taken from the Dungeon Master’s Guide or Player’s Handbook (page numbers are listed for many), but some are edited with some of my own flavor and homebrew, such as the concussion on the lingering injuries table. 

As for rules, I refer to the System Shock table whenever a creature has been dealt half of their maximum hit points in damage in one turn and they fail their subsequent Constitution saving throw. I refer to the Lingering Injuries chart if someone has taken a severe amount of damage (perhaps knocking them unconscious), but not enough to go into System Shock. Or, if some event leads someone to lose a limb or similar, I use the chart to denote what precisely they can and cannot do.

Happy D&D playing!

[cletusthurstonbeauregard]

[marcinkula-blog]

Code & Reference Tables

--------------------------------------------

Just because it is an entity on the logical data model...

- Does not always have to be a separate physical table

- Nor does it always require a physical RI relationship

"Not coded" information - store in base table anyway, forget code tables (Physical Database Implementation)

- Sometimes used for short lived data as a as permanent

- Where code description misspellings cannot occur

Code & Reference Tables - One option

--------------------------------------------

Combine code and reference tables into common groups

- Segmented tablespaces by characteristics

- Code "tables of tables" (See the diagram)

+ Do not cluster on primary index (spread data around)

+ Put index in separate buffer pool

Bottom Line

- Reduce number of objects ion memory

- Use segmented tablespace based on like characteristics

- Use tables of tables where applicable

- Less tablespace and indexes to manage

- Less backup and recovery issues

- Less Maintenance issues

Code & Reference Tables - Placement/Access

--------------------------------------------

Load small code tables into memory tables (application)

- Faster than buffer pool for null values needed to be displayed

- Buffer pool access at 0.1ms to 0.4ms

- I/O to fill the buffer pools at 10ms+for I/O index and data