3e SRD:Creatures by Environment

By Terrain

Aquatic

B

C

D

E

G

H

K

L

M

N

O

P

S

T

W

Desert

A

B

C

D

E

F

G

H

I

L

M

N

O

P

R

S

T

V

W

X

Y

Z

Forest

A

B

C

D

E

F

G

H

I

K

L

M

N

O

P

R

S

T

U

V

W

X

Y

Z

Hill

A

B

C

D

E

F

G

H

I

L

M

N

O

P

R

S

T

V

W

X

Y

Z

Marsh

A

B

C

D

E

F

G

H

I

L

M

N

O

P

R

S

T

V

W

X

Y

Z

Mountains

A

B

C

D

E

F

G

H

I

L

M

N

O

P

R

S

T

V

W

X

Y

Z

Plains

A

B

C

D

E

F

G

H

I

K

L

M

N

O

P

R

S

T

V

W

X

Y

Z

Underground

A

B

C

D

E

F

G

H

I

K

L

M

N

O

P

R

S

T

U

V

W

X

Y

Z

By Temperature

Temperate

A

B

C

D

E

F

G

H

I

K

L

M

N

O

P

R

S

T

U

V

W

X

Y

Z

Warm

A

B

C

D

E

F

G

H

I

K

L

M

N

O

P

R

S

T

U

V

W

X

Y

Z

Cold

A

B

C

D

E

F

G

H

I

K

L

M

N

O

P

R

S

T

V

W

X

Y

Z


Back to Main Page → 3e Open Game Content → System Reference Document → Creatures


This page is protected from editing because it is an integral part of D&D Wiki. Please discuss possible problems on the talk page.

Open Game Content (place problems on the discussion page).
This is part of the 3e System Reference Document. It is covered by the Open Game License v1.0a, rather than the GNU Free Documentation License 1.3. To distinguish it, these items will have this notice. If you see any page that contains SRD material and does not show this license statement, please contact an admin so that this license statement can be added. It is our intent to work within this license in good faith.
gollark: > what's convoluted about that? that's IPHow is it IP? The internet is packet-switched, not circuit-switched.
gollark: Also, potato.
gollark: You have to `bind` and `connect` still, and there seem to be separate "receive from" and "send to" things anyway, and there's a special "join_multicast_v6" thing, and with multicast stuff you have to worry about different interfaces and somehow binding to different addresses than the one you actually want to listen on and it returns useless errors and is generally aææææææææææa.
gollark: UDP is not a stream-oriented protocol and yet you have to muck with sockets in convoluted ways.
gollark: As I said, the socket APIs map *terribly* onto this.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.