jepler/fruitjam-doom
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

PHILOSOPHY: Minor formatting fixes

Browse source
This commit is contained in:
Simon Howard 2016-11-26 21:35:08 -05:00 committed by GitHub
parent d9fa2c3a16
commit 37d108a5ab
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
PHILOSOPHY.md
View file

@ -49,7 +49,7 @@ different ways. Examples are:
Chocolate Doom as a faithful substitute. Chocolate Doom as a faithful substitute.
* Demo compatibility: Doom was one of the first games to develop a * Demo compatibility: Doom was one of the first games to develop a
‘speedrunning’ community, and thousands of recordings of Doom ‘speedrunning’ community, and thousands of recordings of Doom
gameplay (.lmp demo files) exist in the Compet-N archive. Chocolate gameplay (`.lmp` demo files) exist in the Compet-N archive. Chocolate
Doom aims for the highest standard of demo compatibility with Doom aims for the highest standard of demo compatibility with
Vanilla Doom, a goal that is often complicated by obscure behavior Vanilla Doom, a goal that is often complicated by obscure behavior
that can be difficult to reproduce. that can be difficult to reproduce.
@ -70,7 +70,7 @@ These are considered part of the Vanilla experience and ought to be
treated as such. Some examples are: treated as such. Some examples are:
* The novert setting, which reproduces the functionality of * The novert setting, which reproduces the functionality of
novert.exe. `novert.exe`.
* The `-deh` parameter, which loads Dehacked patches like dehacked.exe * The `-deh` parameter, which loads Dehacked patches like dehacked.exe
does under DOS. Chocolate Doom imposes the same limitations that does under DOS. Chocolate Doom imposes the same limitations that
Vanilla Dehacked does. Vanilla Dehacked does.
@ -100,8 +100,8 @@ situations where changes are considered acceptable:
3. Supporting obsolete technology is not a goal: it’s considered 3. Supporting obsolete technology is not a goal: it’s considered
acceptable that Chocolate Doom does not support every type of acceptable that Chocolate Doom does not support every type of
hardware from 1993. However, Chocolate Doom should aim to recreate hardware from 1993. However, Chocolate Doom should aim to recreate
the functionality in a modern way. Examples of technology that the functionality in a modern way. Examples of technologies that
isn’t supported are: aren’t supported are:
- No support for IPX networks, but TCP/IP is supported instead. - No support for IPX networks, but TCP/IP is supported instead.
- No support for dial-up/serial connections; modern operating - No support for dial-up/serial connections; modern operating
@ -114,9 +114,9 @@ situations where changes are considered acceptable:
- There are new key bindings for actions that can’t be rebound with - There are new key bindings for actions that can’t be rebound with
Vanilla Doom, because it’s useful for portability to machines Vanilla Doom, because it’s useful for portability to machines
that don’t have a full keyboard. that don’t have a full keyboard.
- There are additional mouse and joystick key bindings that let you - There are additional mouse and joystick button bindings that let
perform actions with them that can only be done with the keyboard you perform actions with them that can only be done with the
in Vanilla Doom. keyboard in Vanilla Doom.
- Chocolate Doom includes some hacks to support the Doom 3: BFG - Chocolate Doom includes some hacks to support the Doom 3: BFG
Edition IWAD files. The assumption is that being able to at least Edition IWAD files. The assumption is that being able to at least
play is better than nothing, even if it’s not Vanilla behavior. play is better than nothing, even if it’s not Vanilla behavior.