https://zdoom.org/w/api.php?action=feedcontributions&feedformat=atom&user=Lexus+Alyus 2026-08-15T19:33:11Z User contributions MediaWiki 1.43.9 https://zdoom.org/w/index.php?title=Classes&diff=856 2004-01-23T11:47:41Z

<p>Lexus Alyus: Added all of the classes and quickley sorted them. This page needs an hell of a lot of work, but it&#039;s not a bad start... I think a lot of things will be in the wrong place cus I don&#039;t have a clue :-D.</p> <hr /> <div>This page lists all of the classes in Doom (1 and 2), Heretic, Hexen and Strife. This is useful for creating mods that cross a few games (see hellspawn, wolfen, TNT3, etc...). The following is a list of all of the classes and what they are:<br /> <br /> ==Classes==<br /> <br /> These are the classes as of .60 cab.<br /> <br /> ===Doom (1 and 2)===<br /> <br /> Arachnotron // Arachnotron<br /> StealthArachnotron // Stealth Arachnotron<br /> ArachnotronPlasma // Arachnotron Projectile<br /> Archvile // Archville<br /> StealthArchvile // Stealth Archville<br /> ArchvileFire<br /> BossBrain<br /> BossEye<br /> BossTarget<br /> SpawnShot<br /> SpawnFire<br /> BrainState<br /> BaronOfHell<br /> StealthBaron<br /> BaronBall<br /> HellKnight<br /> StealthHellKnight<br /> Cacodemon<br /> StealthCacodemon<br /> CacodemonBall<br /> DeadCacodemon<br /> Cyberdemon<br /> Demon<br /> StealthDemon<br /> Spectre<br /> DeadDemon<br /> ArmorBonus<br /> GreenArmor<br /> BlueArmor<br /> InvulnerabilitySphere<br /> Soulsphere<br /> Megasphere<br /> Berserk<br /> BlurSphere<br /> RadSuit<br /> Infrared<br /> Allmap<br /> Backpack<br /> TechLamp<br /> TechLamp2<br /> Column<br /> TallGreenColumn<br /> ShortGreenColumn<br /> TallRedColumn<br /> ShortRedColumn<br /> SkullColumn<br /> HeartColumn<br /> EvilEye<br /> FloatingSkull<br /> TorchTree<br /> BlueTorch<br /> GreenTorch<br /> RedTorch<br /> ShortBlueTorch<br /> ShortGreenTorch<br /> ShortRedTorch<br /> Stalagtite<br /> TechPillar<br /> Candlestick<br /> Candelabra<br /> BloodyTwitch<br /> Meat2<br /> Meat3<br /> Meat4<br /> Meat5<br /> NonsolidMeat2<br /> NonsolidMeat3<br /> NonsolidMeat4<br /> NonsolidMeat5<br /> NonsolidTwitch<br /> HeadOnAStick<br /> HeadsOnAStick<br /> HeadCandles<br /> DeadStick<br /> LiveStick<br /> BigTree<br /> BurningBarrel<br /> HangNoGuts<br /> HangBNoBrain<br /> HangTLookingDown<br /> HangTLookingUp<br /> HangTSkull<br /> HangTNoBrain<br /> ColonGibs<br /> SmallBloodPool<br /> BrainStem<br /> HealthBonus<br /> Stimpack<br /> Medikit<br /> DoomImp<br /> StealthDoomImp<br /> DoomImpBall<br /> DeadDoomImp<br /> BlueCard<br /> YellowCard<br /> RedCard<br /> BlueSkull<br /> YellowSkull<br /> RedSkull<br /> ExplosiveBarrel<br /> BulletPuff<br /> DoomUnusedStates<br /> DoomPlayer<br /> DeadMarine<br /> GibbedMarine<br /> GibbedMarineExtra<br /> Clip<br /> ClipBox<br /> RocketAmmo<br /> RocketBox<br /> Cell<br /> CellPack<br /> Shell<br /> ShellBox<br /> Fist<br /> Pistol<br /> Chainsaw<br /> Shotgun<br /> SuperShotgun<br /> Chaingun<br /> RocketLauncher<br /> Rocket<br /> PlasmaRifle<br /> PlasmaBall<br /> BFG9000<br /> BFGBall<br /> BFGExtra<br /> Fatso<br /> StealthFatso<br /> FatShot<br /> CommanderKeen<br /> LostSoul<br /> DeadLostSoul<br /> PainElemental<br /> ZombieMan<br /> StealthZombieMan<br /> DeadZombieMan<br /> ShotgunGuy<br /> StealthShotgunGuy<br /> DeadShotgunGuy<br /> ChaingunGuy<br /> StealthChaingunGuy<br /> WolfensteinSS<br /> Revenant<br /> StealthRevenant<br /> RevenantTracer<br /> RevenantTracerSmoke<br /> ScriptedMarine<br /> MarineFist<br /> MarineBerserk<br /> MarineChainsaw<br /> MarinePistol<br /> MarineShotgun<br /> MarineSSG<br /> MarineChaingun<br /> MarineRocket<br /> MarinePlasma<br /> MarineRailgun<br /> MarineBFG<br /> SpiderMastermind<br /> <br /> ===Heretic===<br /> <br /> EggFX<br /> ArtiEgg<br /> SoundWind<br /> SoundWaterfall<br /> ArtiHealth<br /> ArtiSuperHealth<br /> ArtiFly<br /> ArtiInvulnerability<br /> ArtiTorch<br /> CrystalVial<br /> Beast<br /> BeastBall<br /> Puffy<br /> BeakPuff<br /> Beak<br /> ChickenPlayer<br /> Chicken<br /> Feather<br /> Clink<br /> BossSpot<br /> Sorcerer1<br /> SorcererFX1<br /> Sorcerer2<br /> Sorcerer2FX1<br /> Sorcerer2FXSpark<br /> Sorcerer2FX2<br /> Sorcerer2Telefade<br /> ScriptedAmbientMaster<br /> ScriptedAmbient<br /> ScriptedAmbient1<br /> ScriptedAmbient2<br /> ScriptedAmbient3<br /> ScriptedAmbient4<br /> ScriptedAmbient5<br /> ScriptedAmbient6<br /> ScriptedAmbient7<br /> ScriptedAmbient8<br /> ScriptedAmbient9<br /> ScriptedAmbient10<br /> SilverShield<br /> EnchantedShield<br /> ArtiInvisibility<br /> ArtiTomeOfPower<br /> ActivatedTimeBomb<br /> ArtiTimeBomb<br /> SkullHang70<br /> SkullHang60<br /> SkullHang45<br /> SkullHang35<br /> Chandelier<br /> SerpentTorch<br /> SmallPillar<br /> StalagmiteSmall<br /> StalagmiteLarge<br /> StalactiteSmall<br /> StalactiteLarge<br /> FireBrazier<br /> Barrel<br /> BrownPillar<br /> Moss1<br /> Moss2<br /> WallTorch<br /> HangingCorpse<br /> HereticImp<br /> HereticImpLeader<br /> HereticImpChunk1<br /> HereticImpChunk2<br /> HereticImpBall<br /> KeyGreen<br /> KeyBlue<br /> KeyYellow<br /> KeyGizmo<br /> KeyGizmoFloat<br /> KeyGizmoBlue<br /> KeyGizmoGreen<br /> KeyGizmoYellow<br /> Pod<br /> PodGoo<br /> PodGenerator<br /> TeleGlitterGenerator1<br /> TeleGlitterGenerator2<br /> TeleGlitter1<br /> TeleGlitter2<br /> SuperMap<br /> Volcano<br /> VolcanoBlast<br /> VolcanoTBlast<br /> HereticPlayer<br /> BloodySkull<br /> HereticWeapon<br /> Staff<br /> StaffPuff<br /> StaffPuff2<br /> GoldWandAmmo<br /> GoldWandHefty<br /> GoldWand<br /> GoldWandFX1<br /> GoldWandFX2<br /> GoldWandPuff1<br /> GoldWandPuff2<br /> CrossbowAmmo<br /> CrossbowHefty<br /> Crossbow<br /> CrossbowFX1<br /> CrossbowFX2<br /> CrossbowFX3<br /> CrossbowFX4<br /> MaceAmmo<br /> MaceHefty<br /> Mace<br /> MaceFX1<br /> MaceFX2<br /> MaceFX3<br /> MaceFX4<br /> MaceSpawner<br /> Gauntlets<br /> GauntletPuff1<br /> GauntletPuff2<br /> BlasterAmmo<br /> BlasterHefty<br /> Blaster<br /> BlasterFX1<br /> BlasterSmoke<br /> Ripper<br /> BlasterPuff1<br /> BlasterPuff2<br /> SkullRodAmmo<br /> SkullRodHefty<br /> SkullRod<br /> HornRodFX1<br /> HornRodFX2<br /> RainPillar<br /> PhoenixRodAmmo<br /> PhoenixRodHefty<br /> PhoenixRod<br /> PhoenixFX1<br /> PhoenixPuff<br /> PhoenixFX2<br /> BagOfHolding<br /> Ironlich<br /> HeadFX1<br /> HeadFX2<br /> HeadFX3<br /> Whirlwind<br /> Knight<br /> KnightGhost<br /> KnightAxe<br /> RedAxe<br /> Mummy<br /> MummyLeader<br /> MummyGhost<br /> MummyLeaderGhost<br /> MummySoul<br /> MummyFX1<br /> Snake<br /> SnakeProjA<br /> SnakeProjB<br /> Wizard<br /> WizardFX1<br /> BatSpawner<br /> Bat<br /> Bishop<br /> BishopPuff<br /> BishopBlur<br /> BishopPainBlur<br /> BishopFX<br /> <br /> ===Hexen===<br /> <br /> PorkFX<br /> ArtiPork<br /> ArtiTeleport<br /> Minotaur<br /> MinotaurFriend<br /> MinotaurFX1<br /> MinotaurFX2<br /> MinotaurFX3<br /> MinotaurSmokeExit<br /> ArtiBlastRadius<br /> BlastEffect<br /> ArtiBoostArmor<br /> ArtiBoostMana<br /> Centaur<br /> CentaurLeader<br /> CentaurMash<br /> CentaurFX<br /> CentaurShield<br /> CentaurSword<br /> ClericBoss<br /> CWeapFlame<br /> CFlameFloor<br /> FlamePuff<br /> FlamePuff2<br /> CircleFlame<br /> CFlameMissile<br /> ClericWeaponPiece<br /> CWeaponPiece1<br /> CWeaponPiece2<br /> CWeaponPiece3<br /> WraithvergeDrop<br /> CWeapWraithverge<br /> HolyMissile<br /> HolyMissilePuff<br /> HolyPuff<br /> HolySpirit<br /> HolyTail<br /> HolyTailTrail<br /> CWeapMace<br /> ClericPlayer<br /> ClericWeapon<br /> CWeapStaff<br /> CStaffMissile<br /> CStaffPuff<br /> Demon1<br /> Demon1Mash<br /> DemonChunk<br /> Demon1Chunk1<br /> Demon1Chunk2<br /> Demon1Chunk3<br /> Demon1Chunk4<br /> Demon1Chunk5<br /> Demon1FX1<br /> Demon2<br /> Demon2Mash<br /> Demon2Chunk1<br /> Demon2Chunk2<br /> Demon2Chunk3<br /> Demon2Chunk4<br /> Demon2Chunk5<br /> Demon2FX1<br /> Dragon<br /> DragonFireball<br /> DragonExplosion<br /> Ettin<br /> EttinMace<br /> EttinMash<br /> FWeapAxe<br /> AxePuff<br /> AxePuffGlow<br /> AxeBlood<br /> FighterBoss<br /> FWeapHammer<br /> HammerMissile<br /> HammerPuff<br /> FighterPlayer<br /> FWeapFist<br /> PunchPuff<br /> FighterWeapon<br /> FighterWeaponPiece<br /> FWeaponPiece1<br /> FWeaponPiece2<br /> FWeaponPiece3<br /> QuietusDrop<br /> FWeapQuietus<br /> FSwordMissile<br /> FSwordFlame<br /> FireDemon<br /> FireDemonSplotch1<br /> FireDemonSplotch2<br /> FireDemonRock1<br /> FireDemonRock2<br /> FireDemonRock3<br /> FireDemonRock4<br /> FireDemonRock5<br /> FireDemonMissile<br /> FlameSmallTemp<br /> FlameLargeTemp<br /> FlameSmall<br /> FlameLarge<br /> PoisonBag<br /> FireBomb<br /> ThrowingBomb<br /> ArtiPoisonBag<br /> PoisonCloud<br /> FogSpawner<br /> FogPatchSmall<br /> FogPatchMedium<br /> FogPatchLarge<br /> ArtiHealingRadius<br /> Heresiarch<br /> SorcBall<br /> SorcBall1<br /> SorcBall2<br /> SorcBall3<br /> SorcFX1<br /> SorcFX2<br /> SorcFX2T1<br /> SorcFX3<br /> SorcFX3Explosion<br /> SorcFX4<br /> SorcSpark1<br /> MeshArmor<br /> FalconShield<br /> PlatinumHelm<br /> AmuletOfWarding<br /> ZWingedStatue<br /> ZRock1<br /> ZRock2<br /> ZRock3<br /> ZRock4<br /> ZChandelier<br /> ZChandelierUnlit<br /> ZTreeDead<br /> ZTree<br /> ZTreeSwamp150<br /> ZTreeSwamp120<br /> ZStumpBurned<br /> ZStumpBare<br /> ZStumpSwamp1<br /> ZStumpSwamp2<br /> ZShroomLarge1<br /> ZShroomLarge2<br /> ZShroomLarge3<br /> ZShroomSmall1<br /> ZShroomSmall2<br /> ZShroomSmall3<br /> ZShroomSmall4<br /> ZShroomSmall5<br /> ZStalagmitePillar<br /> ZStalagmiteLarge<br /> ZStalagmiteMedium<br /> ZStalagmiteSmall<br /> ZStalactiteLarge<br /> ZStalactiteMedium<br /> ZStalactiteSmall<br /> ZMossCeiling1<br /> ZMossCeiling2<br /> ZSwampVine<br /> ZCorpseKabob<br /> ZCorpseSleeping<br /> ZTombstoneRIP<br /> ZTombstoneShane<br /> ZTombstoneBigCross<br /> ZTombstoneBrianR<br /> ZTombstoneCrossCircle<br /> ZTombstoneSmallCross<br /> ZTombstoneBrianP<br /> ZCorpseHanging<br /> ZStatueGargoyleGreenTall<br /> ZStatueGargoyleBlueTall<br /> ZStatueGargoyleGreenShort<br /> ZStatueGargoyleBlueShort<br /> ZStatueGargoyleStripeTall<br /> ZStatueGargoyleDarkRedTall<br /> ZStatueGargoyleRedTall<br /> ZStatueGargoyleTanTall<br /> ZStatueGargoyleRustTall<br /> ZStatueGargoyleDarkRedShort<br /> ZStatueGargoyleRedShort<br /> ZStatueGargoyleTanShort<br /> ZStatueGargoyleRustShort<br /> ZBannerTattered<br /> ZTreeLarge1<br /> ZTreeLarge2<br /> ZTreeGnarled1<br /> ZTreeGnarled2<br /> ZLog<br /> ZStalactiteIceLarge<br /> ZStalactiteIceMedium<br /> ZStalactiteIceSmall<br /> ZStalactiteIceTiny<br /> ZStalagmiteIceLarge<br /> ZStalagmiteIceMedium<br /> ZStalagmiteIceSmall<br /> ZStalagmiteIceTiny<br /> ZRockBrown1<br /> ZRockBrown2<br /> ZRockBlack<br /> ZRubble1<br /> ZRubble2<br /> ZRubble3<br /> ZVasePillar<br /> ZCorpseLynched<br /> ZCandle<br /> ZBarrel<br /> ZBucket<br /> FireThing<br /> BrassTorch<br /> ZBlueCandle<br /> ZIronMaiden<br /> ZChainBit32<br /> ZChainBit64<br /> ZChainEndHeart<br /> ZChainEndHook1<br /> ZChainEndHook2<br /> ZChainEndSpike<br /> ZChainEndSkull<br /> TableShit1<br /> TableShit2<br /> TableShit3<br /> TableShit4<br /> TableShit5<br /> TableShit6<br /> TableShit7<br /> TableShit8<br /> TableShit9<br /> TableShit10<br /> TeleSmoke<br /> HexenKey<br /> KeySteel<br /> KeyCave<br /> KeyAxe<br /> KeyFire<br /> KeyEmerald<br /> KeyDungeon<br /> KeySilver<br /> KeyRusted<br /> KeyHorn<br /> KeySwamp<br /> KeyCastle<br /> SwitchableDecoration<br /> SwitchingDecoration<br /> ZWingedStatueNoSkull<br /> ZGemPedestal<br /> TreeDestructible<br /> Pottery1<br /> Pottery2<br /> Pottery3<br /> PotteryBit<br /> BloodPool<br /> ZCorpseLynchedNoHeart<br /> CorpseBloodDrip<br /> CorpseBit<br /> ZCorpseSitting<br /> LeafSpawner<br /> Leaf1<br /> Leaf2<br /> ZTwinedTorch<br /> ZTwinedTorchUnlit<br /> ZWallTorch<br /> ZWallTorchUnlit<br /> ZShrub1<br /> ZShrub2<br /> ZPoisonShroom<br /> ZFireBull<br /> ZFireBullUnlit<br /> ZSuitOfArmor<br /> ZArmorChunk<br /> ZBell<br /> ZXmasTree<br /> ZCauldron<br /> ZCauldronUnlit<br /> IceGuy<br /> IceGuyFX<br /> IceFXPuff<br /> IceGuyFX2<br /> IceGuyBit<br /> IceGuyWisp1<br /> IceGuyWisp2<br /> Korax<br /> KoraxSpirit<br /> KoraxBolt<br /> MageBoss<br /> MWeapFrost<br /> FrostMissile<br /> IceShard<br /> MWeapLightning<br /> Lightning<br /> LightningCeiling<br /> LightningFloor<br /> LightningZap<br /> MagePlayer<br /> MageWeapon<br /> MageWeaponPiece<br /> MWeaponPiece1<br /> MWeaponPiece2<br /> MWeaponPiece3<br /> BloodscourgeDrop<br /> MWeapBloodscourge<br /> MageStaffFX2<br /> MWeapWand<br /> MageWandSmoke<br /> MageWandMissile<br /> Mana1<br /> Mana2<br /> Mana3<br /> SnoutPuff<br /> Snout<br /> PigPlayer<br /> Pig<br /> PuzzleItem<br /> PuzzSkull<br /> PuzzGemBig<br /> PuzzGemRed<br /> PuzzGemGreen1<br /> PuzzGemGreen2<br /> PuzzGemBlue1<br /> PuzzGemBlue2<br /> PuzzBook1<br /> PuzzBook2<br /> PuzzFlameMask<br /> PuzzFWeapon<br /> PuzzCWeapon<br /> PuzzMWeapon<br /> PuzzGear1<br /> PuzzGear2<br /> PuzzGear3<br /> PuzzGear4<br /> FireBall<br /> Arrow<br /> Dart<br /> PoisonDart<br /> RipperBall<br /> ProjectileBlade<br /> Serpent<br /> SerpentLeader<br /> SerpentFX<br /> SerpentHead<br /> SerpentGib1<br /> SerpentGib2<br /> SerpentGib3<br /> ArtiSpeedBoots<br /> DirtClump<br /> ThrustFloor<br /> ThrustFloorUp<br /> ThrustFloorDown<br /> ArtiDarkServant<br /> SummoningDoll<br /> MinotaurSmoke<br /> ArtiTeleportOther<br /> TelOtherFX1<br /> TelOtherFX2<br /> TelOtherFX3<br /> TelOtherFX4<br /> TelOtherFX5<br /> FourthWeaponPiece<br /> Wraith<br /> WraithBuried<br /> WraithFX1<br /> WraithFX2<br /> WraithFX3<br /> WraithFX4<br /> WraithFX5<br /> <br /> ===Strife===<br /> <br /> Acolyte<br /> AcolyteTan<br /> AcolyteRed<br /> AcolyteRust<br /> AcolyteGray<br /> AcolyteDGreen<br /> AcolyteGold<br /> AcolyteLGreen<br /> AcolyteBlue<br /> AcolyteShadow<br /> AcolyteToBe<br /> Beggar<br /> Beggar1<br /> Beggar2<br /> Beggar3<br /> Beggar4<br /> Beggar5<br /> Merchant<br /> WeaponSmith<br /> BarKeep<br /> Armorer<br /> Medic<br /> Peasant<br /> Peasant1<br /> Peasant2<br /> Peasant3<br /> Peasant4<br /> Peasant5<br /> Peasant6<br /> Peasant7<br /> Peasant8<br /> Peasant9<br /> Peasant10<br /> Peasant11<br /> Peasant12<br /> Peasant13<br /> Peasant14<br /> Peasant15<br /> Peasant16<br /> Peasant17<br /> Peasant18<br /> Peasant19<br /> Peasant20<br /> Peasant21<br /> Peasant22<br /> Rebel<br /> Rebel1<br /> Rebel2<br /> Rebel3<br /> Rebel4<br /> Rebel5<br /> Rebel6<br /> HEGrenadeRounds<br /> PhosphorusGrenadeRounds<br /> ClipOfBullets<br /> BoxOfBullets<br /> MiniMissiles<br /> CrateOfMissiles<br /> EnergyPod<br /> EnergyPack<br /> PoisonBolts<br /> ElectricBolts<br /> AmmoSatchel<br /> StrifePlayer<br /> Tank1<br /> Tank2<br /> Tank3<br /> Tank4<br /> Tank5<br /> Tank6<br /> KneelingGuy<br /> Reaver<br /> Crusader<br /> FastFlameMissile<br /> CrusaderMissile<br /> StrifeBishop<br /> BishopMissile<br /> Sentinel<br /> SentinelFX1<br /> SentinelFX2<br /> EntityNest<br /> EntityPod<br /> Zap6<br /> Zap5<br /> KlaxonWarningLight<br /> Computer<br /> Bang4Cloud<br /> WaterBottle<br /> Mug<br /> PowerCrystal<br /> WoodenBarrel<br /> ExplosiveBarrel2<br /> TargetPractice<br /> LightSilverFluorescent<br /> LightBrownFluorescent<br /> LightGoldFluorescent<br /> LightGlobe<br /> PillarTechno<br /> PillarAztec<br /> PillarAztecDamaged<br /> PillarAztecRuined<br /> PillarHugeTech<br /> PillarAlienPower<br /> SStalactiteBig<br /> SStalactiteSmall<br /> SStalagmiteBig<br /> CavePillarTop<br /> CavePillarBottom<br /> SStalagmiteSmall<br /> Candle<br /> StrifeCandelabra<br /> WaterDropOnFloor<br /> WaterfallSplash<br /> WaterDrip<br /> WaterFountain<br /> HeartsInTank<br /> TeleportSwirl<br /> DeadCrusader<br /> DeadStrifePlayer<br /> DeadPeasant<br /> DeadAcolyte<br /> DeadReaver<br /> DeadRebel<br /> SacrificedGuy<br /> PileOfGuts<br /> StrifeBurningBarrel<br /> BurningBowl<br /> BurningBrazier<br /> SmallTorchLit<br /> SmallTorchUnlit<br /> CeilingChain<br /> CageLight<br /> Statue<br /> StatueRuined<br /> MediumTorch<br /> OutsideLamp<br /> PoleLantern<br /> SRock1<br /> SRock2<br /> SRock3<br /> SRock4<br /> StickInWater<br /> Rubble1<br /> Rubble2<br /> Rubble3<br /> Rubble4<br /> Rubble5<br /> Rubble6<br /> Rubble7<br /> Rubble8<br /> SurgeryCrab<br /> LargeTorch<br /> HugeTorch<br /> PalmTree<br /> BigTree2<br /> PottedTree<br /> TreeStub<br /> ShortBush<br /> TallBush<br /> ChimneyStack<br /> BarricadeColumn<br /> Pot<br /> Pitcher<br /> Stool<br /> MetalPot<br /> Tub<br /> Anvil<br /> TechLampSilver<br /> TechLampBrass<br /> Tray<br /> AmmoFiller<br /> SigilBanner<br /> RebelBoots<br /> RebelHelmet<br /> RebelShirt<br /> PowerCoupling<br /> AlienBubbleColumn<br /> AlienFloorBubble<br /> AlienCeilingBubble<br /> AlienAspClimber<br /> AlienSpiderLight<br /> Meat<br /> Junk<br /> StrifeWeapon<br /> StrifeSpark<br /> StrifePuff<br /> PunchDagger<br /> StrifeZap1<br /> ElectricBolt<br /> PoisonBolt<br /> StrifeCrossbow<br /> StrifeCrossbow2<br /> AssaultGun<br /> AssaultGunStanding<br /> MiniMissileLauncher<br /> RocketTrail<br /> MiniMissile<br /> FlameThrower<br /> FlameMissile<br /> Mauler<br /> Mauler2<br /> MaulerPuff<br /> MaulerTorpedo<br /> MaulerTorpedoWave<br /> HEGrenade<br /> PhosphorousGrenade<br /> PhosphorousFire<br /> StrifeGrenadeLauncher<br /> StrifeGrenadeLauncher2<br /> Zombie<br /> ZombieSpawner<br /> <br /> ===Zdoom spacific===<br /> <br /> CajunMaster<br /> CajunBodyNode<br /> CajunTrace<br /> WaitingCommand<br /> StoredCommand<br /> DehackedPickup<br /> DecalThinker<br /> DecalFader<br /> DecalStretcher<br /> DecalSlider<br /> DecalColorer<br /> Decoration<br /> BreakableDecoration<br /> SimpleProjectile<br /> FakeInventory<br /> SectorEffect<br /> Mover<br /> MovingFloor<br /> MovingCeiling<br /> Thinker<br /> Autosaver<br /> Args<br /> BoundingBox<br /> PlaneWatcher<br /> ACSThinker<br /> LevelScript<br /> CustomSprite<br /> Ceiling<br /> Door<br /> Floor<br /> Elevator<br /> WaggleBase<br /> FloorWaggle<br /> CeilingWaggle<br /> Lighting<br /> FireFlicker<br /> Flicker<br /> LightFlash<br /> Strobe<br /> Glow<br /> Glow2<br /> Phased<br /> Actor<br /> BloodSplatter<br /> Pillar<br /> Plat<br /> Scroller<br /> Pusher<br /> LightTransfer<br /> PointPusher<br /> PointPuller<br /> ActiveButton<br /> TeleportFog<br /> TeleportDest<br /> TeleportDest2<br /> TeleportDest3<br /> PlayerPawn<br /> PlayerChunk<br /> PlayerSpeedTrail<br /> PolyAction<br /> RotatePoly<br /> MovePoly<br /> PolyDoor<br /> AmbientSound<br /> SeqNode<br /> SeqActorNode<br /> SeqPolyNode<br /> SeqSectorNode<br /> Canvas<br /> FrameBuffer<br /> SimpleCanvas<br /> IceChunk<br /> IceChunkHead<br /> CorpsePointer<br /> CorpseQueue<br /> Powerup<br /> BridgeBall<br /> Bridge<br /> InvisibleBridge<br /> InvisibleBridge32<br /> InvisibleBridge16<br /> InvisibleBridge8<br /> SecurityCamera<br /> AimingCamera<br /> Rock1<br /> Rock2<br /> Rock3<br /> Dirt1<br /> Dirt2<br /> Dirt3<br /> Dirt4<br /> Dirt5<br /> Dirt6<br /> GlassShard<br /> SGShard1<br /> SGShard2<br /> SGShard3<br /> SGShard4<br /> SGShard5<br /> SGShard6<br /> SGShard7<br /> SGShard8<br /> SGShard9<br /> SGShard0<br /> Decal<br /> ImpactDecal<br /> FlashFader<br /> ParticleFountain<br /> RedParticleFountain<br /> GreenParticleFountain<br /> BlueParticleFountain<br /> YellowParticleFountain<br /> PurpleParticleFountain<br /> BlackParticleFountain<br /> WhiteParticleFountain<br /> HateTarget<br /> LightningThinker<br /> InterpolationPoint<br /> InterpolationSpecial<br /> PathFollower<br /> ActorMover<br /> MovingCamera<br /> Health<br /> Armor<br /> Ammo<br /> ItemFog<br /> Inventory<br /> Artifact<br /> Key<br /> Earthquake<br /> SecretTrigger<br /> SectorAction<br /> SecActEnter<br /> SecActExit<br /> SecActHitFloor<br /> SecActHitCeil<br /> SecActUse<br /> SecActUseWall<br /> SecActEyesDive<br /> SecActEyesSurface<br /> SecActEyesBelowC<br /> SecActEyesAboveC<br /> SecActHitFakeFloor<br /> Unknown<br /> PatrolPoint<br /> PatrolSpecial<br /> Blood<br /> MapSpot<br /> MapSpotGravity<br /> RealGibs<br /> Gibs<br /> SkyViewpoint<br /> SkyPicker<br /> SectorSilencer<br /> SoundEnvironment<br /> Spark<br /> WaterSplash<br /> WaterSplashBase<br /> LavaSplash<br /> LavaSmoke<br /> SludgeChunk<br /> SludgeSplash<br /> BloodSplash<br /> BloodSplashBase<br /> SlimeChunk<br /> SlimeSplash<br /> WaterZone<br /> Weapon<br /> HUDMessage<br /> HUDMessageFadeOut<br /> HUDMessageTypeOnFadeOut</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Main_Page&diff=896 2004-01-23T11:31:43Z

<p>Lexus Alyus: </p> <hr /> <div>== Welcome to the ZDoom Wiki ==<br /> <br /> The software currently running the [[ZDoom]] [[Wiki]] is [[MediaWiki]]. Its installation procedure assumes that it will be installed by a user with root access to the server, so I had to make some changes to the installation script to install it on [[zdoom.org]]. For this reason, it is currently considered experimental. I think everything is working, but please test it by writing some pages. If something should work but doesn't, write about it on the [[ZDoom:Bug reports|Bug reports]] page. <br /> <br /> Here's a list of topics: <br /> <br /> * [[ACS]]<br /> * [[Classes]]<br /> * [[Console Commands]]<br /> * [[Level Editing]]<br /> * [[Special Lumps]]<br /> * [[WADs created for ZDoom]]<br /> * [[ZDoom documentation project]]<br /> * [[ZDoom WADs In Progress]]<br /> <br /> Note: This is here for the sole purpose of helping out fellow ZDoomers and has no benefit to [[Randy Heit|Randy]], therefore it is the community's responsibility to keep it relevant and accurate. The whole purpose of this is so that Randy doesn't have to think about the documentation and hence can spend more time perfecting ZDoom. This Wiki is for our benefit and it is our responsibility to prevent people from defacing it. We have been given this responsibility, we should respect this, and help protect this Wiki.<br /> <br /> Happy ZDooming.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=DeHackEd&diff=529 2004-01-06T11:49:06Z

<p>Lexus Alyus: We need to know all the special bits that Zdoom uses...</p> <hr /> <div>This is referred to from [[Special Lumps]], however, it is its own topic as well. First, I will explain it as a special lump for those of you who are on this page for that purpose. ZDoom allows you to import a DeHacked patch into a WAD so that a whole mod can be packaged neatly into one file. (Name the lump DEHACKED, if you haven't caught on yet.) Simple DeHacked (text, not code patches -- DeHacked version 3.0 or later) or .BEX patches may be used. WinTex will require you to use a certain amount of trickery to insert a lump as DEHACKED, so use XWE or something.<br /> <br /> ----<br /> <br /> &quot;DeHacked&quot; is an editor originally created for vanilla Doom that allows you to change the executable file. Hit points, sounds, frame sequences, text strings and a few other miscellaneous values can be changed. The most common patches have been making super-fast monsters, super-fast weapons, player-seeking-self-detonating barrels, and so on, however more balanced and artistic modifications can and have been made. Even though many great effects can be achieved with DeHacked, the flexibility is not complete. Things like monster AI and [[armor class]] are still fixed or don't budge much.<br /> <br /> Older DeHacked patches contained only illegible code that was to be applied to an executable file by the DeHacked patching utility. Later versions of DeHacked saved their patches in a human-readable plain text format that could be used the same way, but you could edit them with any text editor, mostly only feasible for small edits. When [[BOOM]] came around, it was able to load these plain-text patches and affect changes to the game upon startup without any crude hacking such as what DeHacked did to executables -- no patching of the executable. Other source-ports followed suit, and now we have command-line loadable DeHacked support with most modern source-ports. BOOM also provided certain extensions for DeHacked support, so if you see a file ending in .BEX, for Boom Extended, that is a file that uses said extensions. BEX allows greater flexibility in string editing (such as being able to do it AT ALL outside of [[vanilla Doom]], because the prior format relied on replacing text based on offsets, which were useless unless used in conjunction with the original executable file the patch was created for.) BEX also allows application of codepointers to any frame.<br /> <br /> ZDoom did the same, and now has its own [[ZDoom codepointer extensions]] in addition to [[BOOM]]'s, which allow using effects such as the ones in Hexen and more in Doom. These are ZDoom-specific and not backward-compatible with [[vanilla Doom]] or with any other source-ports.<br /> <br /> A great place to learn to use DeHacked from the ground up is at Enjay's reference: http://www.btinternet.com/~Enjay001/<br /> <br /> [[Zdooms Spacific Bits]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=DeHackEd&diff=518 2004-01-06T11:46:56Z

<p>Lexus Alyus: </p> <hr /> <div>This is referred to from [[Special Lumps]], however, it is its own topic as well. First, I will explain it as a special lump for those of you who are on this page for that purpose. ZDoom allows you to import a DeHacked patch into a WAD so that a whole mod can be packaged neatly into one file. (Name the lump DEHACKED, if you haven't caught on yet.) Simple DeHacked (text, not code patches -- DeHacked version 3.0 or later) or .BEX patches may be used. WinTex will require you to use a certain amount of trickery to insert a lump as DEHACKED, so use XWE or something.<br /> <br /> ----<br /> <br /> &quot;DeHacked&quot; is an editor originally created for vanilla Doom that allows you to change the executable file. Hit points, sounds, frame sequences, text strings and a few other miscellaneous values can be changed. The most common patches have been making super-fast monsters, super-fast weapons, player-seeking-self-detonating barrels, and so on, however more balanced and artistic modifications can and have been made. Even though many great effects can be achieved with DeHacked, the flexibility is not complete. Things like monster AI and [[armor class]] are still fixed or don't budge much.<br /> <br /> Older DeHacked patches contained only illegible code that was to be applied to an executable file by the DeHacked patching utility. Later versions of DeHacked saved their patches in a human-readable plain text format that could be used the same way, but you could edit them with any text editor, mostly only feasible for small edits. When [[BOOM]] came around, it was able to load these plain-text patches and affect changes to the game upon startup without any crude hacking such as what DeHacked did to executables -- no patching of the executable. Other source-ports followed suit, and now we have command-line loadable DeHacked support with most modern source-ports. BOOM also provided certain extensions for DeHacked support, so if you see a file ending in .BEX, for Boom Extended, that is a file that uses said extensions. BEX allows greater flexibility in string editing (such as being able to do it AT ALL outside of [[vanilla Doom]], because the prior format relied on replacing text based on offsets, which were useless unless used in conjunction with the original executable file the patch was created for.) BEX also allows application of codepointers to any frame.<br /> <br /> ZDoom did the same, and now has its own [[ZDoom codepointer extensions]] in addition to [[BOOM]]'s, which allow using effects such as the ones in Hexen and more in Doom. These are ZDoom-specific and not backward-compatible with [[vanilla Doom]] or with any other source-ports.<br /> <br /> A great place to learn to use DeHacked from the ground up is at Enjay's reference: http://www.btinternet.com/~Enjay001/<br /> <br /> [[Zdooms additions to Dehacked]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Talk:Action_specials&diff=629 2004-01-06T11:39:19Z

<p>Lexus Alyus: Someone needs to fill in gaps</p> <hr /> <div>I've attempted to add a lot of the line specials from the reference of 1999, plus I've added a few things that I've noted. Just as a note, anything that has a '-' means that I don't know what it is, but I'm sure some kind person will beable to fill in the gaps. <br /> <br /> It looks like I'm the first person to log in... so as my kind contribution to the comunity, I feel that it is my duty to get this thing started :-). Thanx randy for this cool idea, this will really help once it gets up and running. So, lets start helping each other out ;-).<br /> <br /> -Lexus Alyus 4/1/2004<br /> <br /> Somebody sereously needs to fill in the gaps. This would help out a lot.<br /> <br /> -Lexus Alyus 6/1/2004</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Talk:Console_commands&diff=5089 2004-01-06T11:33:27Z

<p>Lexus Alyus: </p> <hr /> <div>Okay, I've attempted to clean up this page by having sections and subsections to make it a lot easier to navigate. I think this is a good idea, but that is just my opinion and you can disagree if you want. If you disagree then let me know.<br /> <br /> It's finished now.<br /> <br /> (edited)-Lexus Alyus 6/1/04</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=521 2004-01-06T11:32:45Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, etc...<br /> <br /> You access the console by pressing &quot;~&quot; at any time. (This depends on your keyboard layout, for German keyboard, it is &quot;^&quot;, but to summarize it, it is the key above TAB.)<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. (EDIT: That's just a string, i.e. testcolor &quot;ff 00 00&quot;)<br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key?ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> <br /> ===addkeysection (menu-heading) (ini-section-name)&lt;br&gt;===<br /> This command does two things. First, it adds a new heading called menu-heading to the controls menu. You can use the addmenukey command to add your own custom keys beneath this heading. Second, it loads all the bindings from the corresponding ini-section-name section in zdoom.ini. You can use this command multiple times to create different sections in the menu and ini for different sets of commands. If you use a menu-heading that was already added to the menu, new controls added with addmenukey will appear at the end of that section, but the bindings will not be reloaded from the ini. <br /> <br /> ===addmenukey (description) (command)&lt;br&gt;===<br /> Adds a new control to the controls menu. Description is the name of this control in the menu, and command is a console command or alias to be executed when the control is pressed. New controls are added to the last section specified with addkeysection.<br /> <br /> ===addslot (slot) (weapon)===<br /> Adds a single weapon to the list of weapons in a weapon slot.<br /> <br /> ===alias (new-command) [command-string]===<br /> If specified with no parameters, will display a list of all current aliases. If only new-command is specified, it will be removed from the list of aliases. If command-string is also specified, it will be added to the list of aliases as new-command. For example, to create a new command to kill the monsters on the level, you can use the command: <br /> alias massacre &quot;kill monsters&quot;<br /> Then you can use the newly created massacre command to kill all the monsters on the level.<br /> <br /> ===archivecvar (cvar)===<br /> When you create a custom cvar with the set command, it will not normally be saved in the ini. You can use archivecvar after creating the cvar to indicate that the custom cvar's value should persist even after you quit.<br /> <br /> ===atexit [command]===<br /> If you specify a command, it will be added to a list of console commands to execute when the user quits the game. Commands are executed in the reverse order that they were added in. If you do not specify any arguments to atexit, then it will list the current set of commands that will execute when you quit.<br /> <br /> ===bind (key [command string])===<br /> If no parameters are specified, the entire list of bound keys will be printed to the console. If only [key] is specified, the binding for that specific key will be printed. If both [key] and [command string] are specified, [command string] will be bound to [key]. <br /> <br /> ===binddefaults===<br /> Binds all keys to their default commands. This will not unbind any keys that do not have any default bindings, so if you want to properly restore the default controls, you need to use unbindall first. <br /> defaultbind key command<br /> Binds command to the key if and only if key is not already bound and there are no keys already bound to command.<br /> <br /> ===doublebind (key [command string])===<br /> This command works just like bind, except it controls the action that occurs when a key is double-clicked. If a key does not have a doublebinding, then double-clicking it has the same result as pressing it twice. Otherwise, the first press will execute the normal command set with bind, and the second press of the double-click will execute the command set with doublebind. <br /> <br /> ===eval expression [variable]===<br /> Evaluates a mathematical expression and either prints it to the console or stores it in variable. Expressions are written using prefix notation instead of the more common infix notation. Basically, you first specify what you want to do (the operator) and then what you want to do it to (the operands). You must separate operators and operands with spaces. <br /> <br /> Examples: <br /> To compute 2+2: <br /> eval + 2 2To compute 5-3: <br /> eval - 5 3To compute 2+(5*6): <br /> eval + 2 * 5 6To decrease the number of screenblocks: <br /> eval - $screenblocks 1 screenblocksThe supported operators are:<br /> + a b Adds a and b. <br /> - a b Subtracts b from a. <br /> * a b Multiplies a and b. <br /> / a b Divides a by b. <br /> % a b Calculates the remainder of a/b. <br /> ^ a b Raises a to the b-th power . <br /> &lt; a b Produces 1 if a is less than b and 0 if not. <br /> &lt;= a b Produces 1 if a is less than or equal to b and 0 if not. <br /> &gt; a b Produces 1 if a is greater than b and 0 if not. <br /> &gt;= a b Produces 1 if a is greater than or equal to b and 0 if not. <br /> = a b Produces 1 if a is equal to b and 0 if not.<br /> <br /> == a b Produces 1 if a is equal to b and 0 if not. <br /> != a b Produces 1 if a is not equal to b and 0 if it is. <br /> &lt;&gt; a b Produces 1 if a is not equal to b and 0 if is. <br /> xor a b Calculates the bit-wise exclusive-or of a and b. <br /> &amp; a b Calculates the bit-wise and of a and b. <br /> | a b Calculates the bit-wise or of a and b. <br /> &amp;&amp; a b Calculates the logical and of a and b. <br /> || a b Calculates the logical or of a and b. <br /> <br /> ===exec (script-file)===<br /> Executes a series of commands stored in the script-file as if they had been typed in at the console directly. <br /> <br /> ===key value1 [value2]===<br /> Translates all parameters to the command into their corresponding key values which are used internally for command and alias lookup. Probably not very useful for the average user. <br /> <br /> ===puke (script [arguments])===<br /> Executes an ACS script on the current map, optionally passing it up to three numerical arguments. <br /> <br /> ===pullin (wadfile)===<br /> Loads a wadfile at startup. This command is only valid inside .cfg files that have been execed at startup.<br /> <br /> ===set (cvar) (value)===<br /> Sets cvar to value. If cvar does not exist, it will be created. <br /> <br /> ===rebind (binding)===<br /> Changes the binding for the key that caused the rebind command to execute. For obvious reasons, this command cannot be used at the console.<br /> <br /> Example: <br /> <br /> bind b &quot;echo setting 1; rebind \&quot;echo setting 2\&quot;&quot;<br /> <br /> This will cause the first press of b to echo &quot;setting 1&quot; to the console. All future presses of b will echo &quot;setting 2&quot; instead. <br /> <br /> ===unbind (key)===<br /> Removes a binding from the specified key.<br /> <br /> ===unbindall===<br /> Removes all bindings and doublebindings from every key. To restore the default bindings, you can use the binddefaults command. There is no way to restore any custom bindings after issuing this command except by retyping each bind command or using the controls setup menu.<br /> <br /> ===undoublebind (key)===<br /> Removes a doublebinding from the specified key.<br /> <br /> ===unset (cvar)===<br /> Undefines a user-created cvar.<br /> <br /> ==Screenshots==<br /> <br /> ===png_gamma===<br /> float: 0&lt;br&gt;<br /> Controls the gamma level stored in PNG screenshots. If this is 0, then your current gamma setting will be used.<br /> <br /> ===png_level===<br /> integer: 5&lt;br&gt;<br /> This is the level of compression to use for PNG screenshots. 0 is no compression at all, 1 is minimal compression (fastest), 9 is maximum compression (slowest), and intermediate values offer intermediate compression. 5 is offers a decent trade-of between file size and compression time. An uncompressed image will not neccessarily save faster than a compressed image, because the extra time needed to write out a complete uncompressed image may be longer than the time required to compress the image. If you need to create screenshots as quickly as possible, consider setting screenshot_type to &quot;pcx&quot;. <br /> <br /> ===screenshot [file]===<br /> Dumps a copy of the screen to disk as a PNG or PCX file. If file is not specified, the screenshot will be saved to the directory the game was run from with a name of the form doom????.png. <br /> <br /> ===screenshot_quiet===<br /> boolean: false&lt;br&gt;<br /> Setting this to true will suppress the messages informing you what file a screenshot was saved to.<br /> <br /> ===screenshot_type===<br /> string: &quot;png&quot;&lt;br&gt;<br /> Determines the type of screenshots that will be saved. This can be either &quot;png&quot; or &quot;pcx&quot;. In my empirical studies, PNG screenshots are about half the size of pcx screenshots. PCX screenshots have the advantage that they require less time to create so are most useful for rapid screenshot generation. The following sequence of console commands will take a screenshot every frame. You can use an external program to assemble these into a video, if desired. <br /> <br /> screenshot_type &quot;png&quot;&lt;br&gt;<br /> screenshot_quiet true&lt;br&gt;<br /> alias autoshot &quot;screenshot; wait 1; autoshot&quot;&lt;br&gt;<br /> autoshot&lt;br&gt;<br /> <br /> If you use the autoshot alias, the command alias autoshot will stop automatic screenshot taking before you hit 10000 screenshots (approximately 4 minutes, 45 seconds).<br /> <br /> ===storesavepic===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will produce smaller savegames (by about 14k typically) by not storing a screenshot inside the savegame.<br /> <br /> ==Chatting==<br /> <br /> ===chat_substitution===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want to chat using special keywords that will be replaced with appropriate text when your messages are sent. The supported keywords are:<br /> <br /> $health &lt;br&gt;<br /> Replaced by your current health. &lt;br&gt;<br /> $weapon &lt;br&gt;<br /> Replaced by the name of your current weapon. &lt;br&gt;<br /> $armor &lt;br&gt;<br /> Replaced by your current armor count. &lt;br&gt;<br /> $ammocount &lt;br&gt;<br /> Replaced by your current ammo count. &lt;br&gt;<br /> $ammo &lt;br&gt;<br /> Replaced by the name of your current ammo.<br /> <br /> As an example, if you just started a new game of Doom and have chat substitution turned on, when you send the message &quot;My health is $health, and I am using a $weapon&quot;, the message that is actually sent will be &quot;My health is 100, and I am using a Pistol&quot;.<br /> <br /> chatmacro0&lt;br&gt;<br /> chatmacro1&lt;br&gt;<br /> chatmacro2&lt;br&gt;<br /> chatmacro3&lt;br&gt;<br /> chatmacro4&lt;br&gt;<br /> chatmacro5&lt;br&gt;<br /> chatmacro6&lt;br&gt;<br /> chatmacro7&lt;br&gt;<br /> chatmacro8&lt;br&gt;<br /> chatmacro9&lt;br&gt;<br /> string&lt;br&gt;<br /> These are all strings that can be assigned to hotkeys in chat mode. To use these, enter chat mode and then hold down Alt and press one of the number keys. The string stored in the corresponding chatmacro cvar will be sent as if you had typed it yourself. <br /> <br /> ===messagemode===<br /> Enters message entry mode. Anything typed while in this mode will be sent to everyone else as if you had used the say command once you press enter. <br /> <br /> ===messagemode2===<br /> This is just like messagemode except that the message is only sent to other members of your team. If teamplay is false or you don't have a team, then this command will work just like messagemode and send the message to everyone. <br /> <br /> ===say (message)===<br /> Sends a message to everyone playing. If your message begins with &quot;/me&quot; then &quot;/me&quot; will be replaced by your name ala IRC. <br /> <br /> ===say_team (message)===<br /> This is just like say except it only sends a message to your teammates. If teamplay is inactive, then this command will act exactly like say and send the message to everyone.<br /> <br /> ==Cheating==<br /> <br /> ===sv_cheats===<br /> boolean: false<br /> When true, cheats will be allowed in Nightmare difficulty and network games. For purposes of fairness, this cvar can only be set from the command line when you run ZDoom. This is to avoid situations where the key player in a multiplayer game (player 1) could go to the console and type something like this:<br /> <br /> sv_cheats 1<br /> god<br /> sv_cheats 0<br /> <br /> whereby rendering himself immune to the attacks of others.<br /> <br /> ===anubis===<br /> Toggles monster fear on and off. Scared monsters will run away from you and attack less frequently.<br /> <br /> ===fly===<br /> Toggles fly mode on and off.<br /> <br /> ===give (item)===<br /> Gives an item to the player. Give understands the following special items: <br /> all - gives you everything <br /> health - gives you full health <br /> weapons - gives you every weapon <br /> ammo - gives you full ammo <br /> armor - gives you full armor <br /> keys - gives you every key <br /> It also understands the names of individual inventory items. Use the command dumpclasses inventory for a complete list of these. <br /> <br /> ===god===<br /> Toggles God (Degreelessness) mode on/off. While active, you cannot be hurt by normal attacks (although telefragging will still kill you). Also known as iddqd. <br /> <br /> ===iddqd===<br /> The same as god, except it also gives you 100 health.<br /> <br /> ===kill [monsters]===<br /> If used as &quot;kill monsters&quot;, will kill all monsters on the level. Otherwise, it will kill you instead. This command is broken in netgames, so don't use it unless you are playing a single player game. <br /> <br /> ===logfile [log-file]===<br /> If log-file is not specified, console logging will be stopped (if active). Otherwise, a file named log-file will be created on disk, and all console output will be recorded in it as well as on the screen. <br /> <br /> ===mdk===<br /> This cheat will kill whatever you are looking at.<br /> <br /> ===morphme===<br /> Transforms you into a chicken in Heretic and a pig in Hexen and Doom (The latter only happens if you have the releven graphics present).<br /> <br /> ===noclip===<br /> Toggles noclipping mode on/off. <br /> <br /> ===notarget===<br /> Toggles notarget mode on/off. While active, monsters will not target you unless you hurt them first. In &quot;modern FPS&quot;, monsters &quot;can't find you&quot; when in notarget mode. This is not the case with ZDoom.<br /> <br /> ===powerup===<br /> Powers you up in Heretic as if you had used a Tome of Power.<br /> <br /> ===sv_fastweapons (0-2)===<br /> Increases speed of weapons in Doom, Heretic, and Hexen. Setting to 2 makes weapons even faster.<br /> <br /> ===turbo===<br /> float: 100&lt;br&gt;<br /> This cvar affects how quickly the player moves. A value of 100 will cause the player to move at normal speed, 200 will cause the player to move at 200% of normal speed, 50 will cause the player to move at 50% of normal speed, etc. Valid values range from 10 to 256.<br /> <br /> ==Display==<br /> <br /> ===bumpgamma===<br /> Increases the current gamma level by 0.1. If the new gamma level would be greater than 3.0, it wraps the gamma around to 1.0 <br /> <br /> ===cl_bbannounce===<br /> boolean: false&lt;br&gt;<br /> When true, enables the Bloodbath announcer for deathmatch games. The Bloodbath announcer is &quot;The Voice&quot; from Monolith Software's Blood game. To hear the announcer, you need to load Blood's sounds.rff either at the command line or through one of zdoom.ini's [*.Autoload] sections. You can get this file either from the demo or full version of Blood. If you don't have sounds.rff, you can still see the announcer's messages even though you won't hear anything. <br /> <br /> ===cl_showmultikills===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player makes several kills in a short period of time.<br /> <br /> ===cl_showsprees===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player is on a killing spree.<br /> <br /> ===cl_spreaddecals===<br /> boolean: true&lt;br&gt;<br /> ZDoom clips decals to sidedefs. In order to hide this, the game will create as many duplicate decals on adjoining sidedefs as needed to make it appear that there is only one unbroken decal on the wall. Set this cvar to false if you don't want this.<br /> <br /> ===con_centernotify===<br /> boolean: false for Doom, true for Heretic and Hexen&lt;br&gt;<br /> When true, notify messages at the top of the screen are centered. Otherwise, they are justified against the left margin.<br /> <br /> ===con_midtime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that messages in the middle of the screen will be displayed before they dispapper. <br /> <br /> ===con_notifytime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that new messages will stay at the top of the screen before they start scrolling away. <br /> <br /> ===con_scaletext===<br /> boolean: false&lt;br&gt;<br /> If this cvar is true, then message text will be scaled to larger sizes depending on the screen resolution so that it will stay approximately the same size it would be on a 320x200 screen. <br /> <br /> ===crosshair===<br /> integer: 0&lt;br&gt;<br /> If this cvar is non-zero, it draws a crosshair. If this cvar is negative, the crosshair is translucent, otherwise it is opaque. The specific crosshair drawn depends on the value of this cvar. <br /> <br /> ===crosshaircolor===<br /> color: &quot;ff 00 00&quot;&lt;br&gt;<br /> This is the crosshair's color if crosshairhealth is false.<br /> <br /> ===crosshairgrow===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to temporarily enlarge each time you pick up an item.<br /> <br /> ===crosshairhealth===<br /> boolean: true&lt;br&gt;<br /> When true, the crosshair's color reflects your current health. Green is healthy, red is near death, and intermediate colors are somewhere in between. Set this to false, if you want the crosshair to have a constant color (specified by the crosshaircolor cvar) instead.<br /> <br /> ===crosshairscale===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to always appear the same size at all resolutions. Leaving it at false causes the crosshair to be drawn normally.<br /> <br /> ===gamma===<br /> float: 1.0&lt;br&gt;<br /> Controls the amount of gamma correction applied to the display. 1.0 is equivalent to no correction, while larger numbers translate into a brighter display, and smaller numbers translate into a darker display. 0.0 is invalid and will be rejected. Negative numbers are technically invalid but will be accepted solely for the novelty value doing so provides. <br /> <br /> ===hud_scale===<br /> boolean: false&lt;br&gt;<br /> Controls scaling of the fullscreen hud. At resolutions of 640x400 or above, setting this cvar to true will cause the icons to be scaled to approximately the same size they would be at 320x200. If this cvar is false, the icons will always be drawn without any scaling. <br /> <br /> ===msg===<br /> integer: 0&lt;br&gt;<br /> This is the minimum message level that you will see. You will not see any messages with a lower priority than this. The different message levels are: <br /> <br /> #Item pickup <br /> #Obituaries <br /> #Critical messages <br /> #Chat messages <br /> #Chat messages from a teammate <br /> <br /> ===msg0color===<br /> integer: 6&lt;br&gt;<br /> This cvar controls the color used to display level 0 (item pickup) messages. Available colors are: <br /> <br /> #Brick <br /> #Tan <br /> #Gray <br /> #Green <br /> #Brown <br /> #Gold <br /> #Red <br /> #Blue <br /> #Orange <br /> #White <br /> #Yellow <br /> <br /> ===msg1color===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display level 1 (obituary) messages. Available colors are the same as for&quot; msg0color. <br /> <br /> ===msg2color===<br /> integer: 2&lt;br&gt;<br /> This cvar selects the color used to display level 2 (critical) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg3color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 3 (chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg4color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 4 (team chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor2===<br /> integer: 4&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen that are sent to everyone. Available colors are the same as for msg0color. <br /> <br /> ===st_scale===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, the status bar will be scaled so that it covers the entire width of the screen in higher resolutions. At low resolutions this may look ugly, but at high resolutions it should look good enough.<br /> <br /> ==Renderer==<br /> <br /> ===r_columnmethod===<br /> integer: 1&lt;br&gt;<br /> Selects which of two algorithms to use to draw sprites and masked textures. Method 0 is the original algorithm used by DOOM. Method 1 is a new algorithm optimized for Pentium IIs and can perform significantly better with that or comparable processors. Ironically, method 0 is slightly faster than method 1 on Pentium III and Athlon processors (though not significantly so). <br /> <br /> ===r_detail===<br /> integer: 0&lt;br&gt;<br /> This cvar selects the detail level of the view window. Valid values are: <br /> <br /> #Normal detail level. Equivalent to Doom's high detail mode. <br /> #Double pixels horizontally. Equivalent to Doom's low detail mode. <br /> #Double pixels vertically. <br /> #Double pixels horizontally and vertically. <br /> <br /> Because of the way the renderer works, doubling pixels horizontally offers more of a speed-up than doubling them vertically does. Unless you have a very slow computer, there should be no reason to use any detail level other than 0. <br /> <br /> ===r_drawflat===<br /> boolean: false&lt;br&gt;<br /> When set to 0, segs will be drawn as solid colors instead of textures. This is useful if you want to see how a node builder split a level's linedefs. Otherwise, it just looks ugly. <br /> <br /> ===r_drawfuzzbr===<br /> boolean: true&lt;br&gt;<br /> When set to false, the &quot;fuzz&quot; effect on spectres and partially invisible players will be replaced with translucency. <br /> <br /> ===r_drawmirrors===<br /> boolean: true&lt;br&gt;<br /> Setting this false will disable the display of mirrors.<br /> <br /> ===r_drawplayersprites===<br /> boolean: true&lt;br&gt;<br /> When false, the game will not draw the player's weapon or muzzle flash, which can be nice for screenshots. <br /> <br /> ===r_drawtrans===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will disable all translucency effects in the game.<br /> <br /> ===r_fogboundary===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will disable the display of fog boundaries. Fog boundaries are sections where two areas with different fog colors meet. If the boundary is not drawn, then it will look like there is no fog at all in front of the boundary. Some old levels may look bad with fog boundary drawing enabled, which is why this cvar is available.<br /> <br /> ===r_particles===<br /> boolean: true&lt;br&gt;<br /> If set to true, particles are drawn. Otherwise, they aren't. <br /> <br /> ===r_stretchsky===<br /> boolean: true&lt;br&gt;<br /> Controls whether or not short sky textures are stretched so that you don't see them wrap when you look up. <br /> <br /> ===r_viewsize===<br /> string&lt;br&gt;<br /> This cvar contains the width and height of the current view window. This cvar is read only. <br /> <br /> ===r_visibility [visibility]===<br /> Without any parameters, displays the current visibility. With a parameter, the visibility is set. Standard visibility for the Doom engine is 8. Visibility determines how quickly light drops off with distance from the viewer. At 0 visibility, there is no change in lighting with depth.<br /> <br /> ==Video==<br /> <br /> ===fullscreen===<br /> boolean: true&lt;br&gt;<br /> If this cvar is true, the game will be displayed fullscreen. Otherwise, it will be drawn in a window. Some video cards may require that you have fullscreen false in order to run ZDoom. <br /> <br /> ===vid_attachedsurfaces (Win32 only)===<br /> boolean: false&lt;br&gt;<br /> Controls how the game allocates video memory. False is the standard setting and will always produce a useable display. If you find that there are patches of pure black and pure white on the screen (especially noticeable when a demon is right in your face), try setting this to true. Certain old Windows 95 video drivers are said to need this fix, and it is also necessary under NT 4. Unfortunately, many new video drivers (including those under NT 4) will produce a scrambled display if the screen width is not 512 or 1024 pixels and this is set to true.<br /> <br /> ===vid_currentmode===<br /> Displays the resolution of the current video mode.<br /> <br /> ===vid_defbits===<br /> integer: 8&lt;br&gt;<br /> Ignored. This cvar is meant to specify the default screen depth, but the setting is currently ignored because only 256-color displays are supported.<br /> <br /> ===vid_defheight===<br /> integer: 200&lt;br&gt;<br /> Specifies the default screen height to use if not overridden at the command line by the -height switch.<br /> <br /> ===vid_defwidth===<br /> integer: 320&lt;br&gt;<br /> Specifies the default screen width to use if not overridden at the command line with the -width switch.<br /> <br /> ===vid_listmodes===<br /> Lists all resolutions supported by the current display driver.<br /> <br /> ===vid_fps===<br /> boolean: false&lt;br&gt;<br /> When true, displays the average framerate over the past second in the lower-left corner of the screen. Because Doom's internal game rate and frame rate are linked, the framerate will never be (much) above 35 fps.<br /> <br /> ===vid_noblitter (Win32 only)===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will allow the use of the hardware to assist moving image data to video memory. When I initial wrote the code to use the blitter, it was faster than not using it. Now the blitter is slower, and I can't figure out why, so the default is true.<br /> <br /> ===vid_palettehack (Win32 only)===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, the game will refresh the palette every time the screen is redrawn. This can be useful with some buggy video drivers. If the display is fine without it, leave it that way because this can slightly slow things down.<br /> <br /> ===vid_setmode (width) (height) [depth]===<br /> Sets the screen mode to width x height with an optional color depth (if your video hardware supports it). Only a depth of 8 is supported. See also vid_currentmode, vid_listmodes<br /> <br /> ===vid_vsync (Win32 only)===<br /> boolean: true&lt;br&gt;<br /> Set this to false to disable vsync. Not all video cards support disabling vsync.<br /> <br /> ==Bots==<br /> <br /> ===addbot [name]===<br /> Spawns a bot. If a name is given, the corresponding bot in bots.cfg will be spawned. Otherwise, a bot will be picked at random from bots.cfg. <br /> <br /> ===bot_allowspy===<br /> boolean: false&lt;br&gt;<br /> Allows you to see through the eyes of bots during botmatch games. <br /> <br /> ===bot_observer===<br /> boolean: false&lt;br&gt;<br /> When set to 1, the player will experience minimal interaction with the world, and bots will ignore him. <br /> <br /> ===listbots===<br /> Lists the bots available in bots.cfg, and indicates which are currently playing. <br /> <br /> ===removebots===<br /> Removes any bots from the game. Bots will also be automatically removed from network games when the arbitrator quits.<br /> <br /> ==Automap==<br /> <br /> ===togglemap===<br /> Toggles the automap on/off.<br /> <br /> ===am_backcolor===<br /> color: &quot;6c 54 40&quot;&lt;br&gt;<br /> The color of the automap background. Changes to this cvar take effect the next time the automap is activated. <br /> <br /> ===am_cdwallcolor===<br /> color: &quot;4c 38 20&quot;&lt;br&gt;<br /> The color of two-sided lines that have a different ceiling height on each side. <br /> <br /> ===am_fdwallcolor===<br /> color: &quot;88 70 58&quot;&lt;br&gt;<br /> The color of two-sided lines that have a different floor height on each side. <br /> <br /> ===am_gridcolor===<br /> color: &quot;8b 5a 2b&quot;&lt;br&gt;<br /> The color of the automap grid. <br /> <br /> ===am_interlevelcolor===<br /> color: &quot;ff 00 00&quot;&lt;br&gt;<br /> The color of inter-level teleporters. These are teleporters that teleport you to a different map. <br /> <br /> ===am_intralevelcolor===<br /> color: &quot;00 00 ff&quot;&lt;br&gt;<br /> The color of intra-level teleporters. These are teleporters that teleport you to a different location on the same map. <br /> <br /> ===am_lockedcolor===<br /> color: &quot;00 00 98&quot;&lt;br&gt;<br /> The color of lines that open locked doors. <br /> <br /> ===am_notseencolor===<br /> color: &quot;6c 6c 6c&quot;&lt;br&gt;<br /> The color of lines on the automap that haven't yet been seen. Visible with a computer area map. <br /> <br /> ===am_overlay===<br /> boolean: false&lt;br&gt;<br /> Normally, the togglemap command switches the automap between fully off and fully on. Setting this cvar to &quot;1&quot; will cause togglemap to draw the automap on top of the player's view before it draws the automap fullscreen. (Bad description, I know. Just try it) <br /> <br /> ===am_ovotherwallscolor===<br /> color: &quot;00 88 44&quot;&lt;br&gt;<br /> The color of passable lines on the automap when the map is overlayed. <br /> <br /> ===am_ovtelecolor===<br /> color: &quot;ff ff 00&quot;&lt;br&gt;<br /> The color of teleporters—both inter- and intra-level—on the overlayed automap.<br /> <br /> ===am_ovthingcolor===<br /> color: &quot;e8 88 00&quot;&lt;br&gt;<br /> The color of things visible with the automap cheat when the map is overlayed. <br /> <br /> ===am_ovunseencolor===<br /> color: &quot;00 22 6e&quot;&lt;br&gt;<br /> The color of unseen lines on the automap when the map is overlayed. <br /> <br /> ===am_ovwallcolor===<br /> color: &quot;00 ff 00&quot;&lt;br&gt;<br /> The color of impassable walls when the automap is overlayed. <br /> <br /> ===am_ovyourcolor===<br /> color: &quot;fc e8 d8&quot;&lt;br&gt;<br /> The color of the arrow representing the player in single player games when the map is overlayed. <br /> <br /> ===am_rotate===<br /> boolean: false&lt;br&gt;<br /> Normally, the automap is always drawn such that north is at the top of the screen. Setting this cvar to &quot;1&quot; causes the automap to be drawn so that lines toward the top of the screen are always directly in front of the player's view. This can be particularly useful when the automap is overlayed. <br /> <br /> ===am_showitems===<br /> boolean: false&lt;br&gt;<br /> When true, the fullscreen automap will display a count of all the &quot;special&quot; items you have found on the map. These are the same items that are used to determine the Items stat on the intermission screen.<br /> <br /> ===am_showmonsters===<br /> boolean: true&lt;br&gt;<br /> When true, the fullscreen automap will display a count of the number of monsters that have been killed in the current level and the total number of monsters in the level. <br /> <br /> ===am_showsecrets===<br /> boolean: true&lt;br&gt;<br /> When true, the fullscreen automap will display a count of the number of secrets that have been found in the current level and the total number of secrets in the level. <br /> <br /> ===am_showtime===<br /> boolean: true&lt;br&gt;<br /> When true, the fullscreen automap will display the total amount of time you have been in a level (excluding time that has been paused). <br /> <br /> ===am_thingcolor===<br /> color: &quot;fc fc fc&quot;&lt;br&gt;<br /> The color of things revealed with the map cheat. <br /> <br /> ===am_tswallcolor===<br /> color: &quot;88 88 88&quot;&lt;br&gt;<br /> The color of two-sided lines that don't have any difference in floor or ceiling heights on either side. Only seen using map cheat. <br /> <br /> ===am_usecustomcolors===<br /> boolean: true&lt;br&gt;<br /> When true, the automap uses the colors specified by the am_* cvars, otherwise it uses the standard DOOM automap colors. <br /> <br /> am_wallcolor&lt;br&gt;<br /> color: &quot;2c 18 08&quot;&lt;br&gt;<br /> The color of one-sided and secret walls in the automap. <br /> <br /> ===am_xhaircolor===<br /> color: &quot;80 80 80&quot;&lt;br&gt;<br /> The color of the &quot;crosshair&quot; dot in the center of the automap. <br /> <br /> ===am_yourcolor===<br /> color: &quot;fc e8 d8&quot;&lt;br&gt;<br /> The color of the arrow representing the player in single player games.<br /> <br /> ==Player Settings==<br /> <br /> ===autoaim===<br /> float: 5000&lt;br&gt;<br /> This represents the vertical distance from an object that the player's sight must be before that object is aimed at. Setting this cvar to &quot;0&quot; disables autoaiming, while large values such as &quot;5000&quot; will reproduce the original DOOM behavior of always autoaiming. <br /> <br /> ===color===<br /> color&lt;br&gt;<br /> This is your player's color. The default varies depending on which game you are playing. <br /> <br /> ===gender===<br /> string: &quot;male&quot;&lt;br&gt;<br /> This is the gender of your player. Valid values are &quot;male&quot;, &quot;female&quot;, and &quot;neuter&quot;. Anything else will be treated as male. When you die, certain messages will be altered to reflect the gender selected here. Unfortunately, I don't provide any non-male player sounds, so you'll still sound like a man no matter what this cvar is set to unless you provide your own sounds. <br /> <br /> ===movebob===<br /> float: 0.25&lt;br&gt;<br /> Controls how much the view bobs up and down while you are moving. 0 would be no bob at all.<br /> <br /> ===name===<br /> string: &quot;Player&quot;&lt;br&gt;<br /> This is your player's name. This is only really useful in a multiplayer game, but it can also be set for single player. <br /> <br /> ===neverswitchonpickup===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, you won't automatically switch to a new weapon when you pick one up. <br /> <br /> ===skin===<br /> string: &quot;base&quot;&lt;br&gt;<br /> This is your player's skin. &quot;Base&quot; is the name of the regular Doom marine and is always available. Additional skins are contained in wad files that you either load with -file at the command line or autoload using the .ini or skins directory. <br /> <br /> ===stillbob===<br /> float: 0&lt;br&gt;<br /> Controls the amount of bobbing up and down that occurs when standing still. 0 is no bobbing at all.<br /> <br /> ===team===<br /> integer: 255&lt;br&gt;<br /> This is the team that your player belongs to. It is only meaningful during deathmatch games. There are four teams available: <br /> <br /> #Red <br /> #Blue <br /> #Green <br /> #Gold<br /> <br /> Using a team of 255 is special and will automatically assign you to whichever team has fewer players.<br /> <br /> ==Debugging==<br /> <br /> ===autosavenum===<br /> integer: 0&lt;br&gt;<br /> This cvar keeps track of the number used for the next automatic save and is updated each time an automatic save is made. You cannot change it from the console.<br /> <br /> ===clearwallcycles===<br /> Used for profiling the wall drawer.&lt;br&gt;<br /> <br /> ===countdecals===<br /> Returns the internal count of automatically generated decals.<br /> <br /> ===countdecalsreal===<br /> Iterates through every automatically generated decal in the level and returns how many are present. Compare this value with what countdecals returns to ensure that the internal count is accurate.<br /> <br /> ===demo_compress===<br /> boolean: true&lt;br&gt;<br /> Keep this cvar true to compress demos so that they take up less space on disk.<br /> <br /> ===developer===<br /> boolean: false&lt;br&gt;<br /> When true, prints various debugging messages to the console. <br /> <br /> ===dir [[path/][pattern]]===<br /> This command lists the contents of a directory. It supports wildcards (but will not recurse into multiple directories). If [path] is not specified, it will display the contents of the directory the game was run from. <br /> <br /> ===disableautosave===<br /> integer: 0&lt;br&gt;<br /> Controls how frequently the game automatically saves for you. The possible settings are: <br /> #Whenever you enter a new level and whenever the level requests it. <br /> #Only when the level requests it. <br /> #Never. <br /> <br /> ===dumpclasses [base-class]===<br /> Displays a list of all classes in the game. You can use base-class to limit the list to only those classes that derive from base-class. For example, dumpclasses actor will only show those classes that can be spawned in a level (including actors from all supported games). If you only want a list of weapons, you can use dumpclasses weapon. This list can be quite long and exceed the length of the console buffer, so it is a good idea to capture its output to a file using the logfile command.<br /> <br /> ===dumpheap===<br /> Prints detailed information about the zone heap. Probably not very useful to the average user. The zone heap's primary purpose is to hold graphics while you run around a level so that they don't need to be constantly reloaded from disk. <br /> <br /> ===dumpmap (wadname) [mapname]===<br /> Saves the current state of the level (minus actors) to a new wad called wadname. If you don't specify a mapname, it will be saved as MAP01. I used this while testing the internal node builder. Because ZDoom can now load Build maps, you can use this as a simple Build-&gt;Doom converter (although limitations in the Doom map format will likely force you to make several edits to produce a useable map).<br /> <br /> ===dumpmapthings===<br /> Lists all the map editor numbers for actors in the current game.<br /> dumpspawnables<br /> Lists all the spawn numbers for actors in the current game.<br /> <br /> ===echo (string)===<br /> Prints string to the console. <br /> <br /> ===error (error-message)===<br /> Simulates an error by killing the current game and falling back to the fullscreen console with the specified message. <br /> <br /> ===error_fatal (error-message)===<br /> Simulates a fatal error by exiting the game completely and showing the error-message.<br /> <br /> ===freeze===<br /> Use this command once to freeze gameplay (while still allowing you to move around). Use it again to unfreeze gameplay. <br /> <br /> ===gameversion===<br /> Prints the version number and compile date of ZDoom. <br /> <br /> ===genblockmap===<br /> boolean: false&lt;br&gt;<br /> Set this to true to force the game to ignore the blockmap saved with a map and always generate it from scratch, whether it needs to be generated or not.<br /> <br /> ===gennodes===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the game to ignore the BSP tree saved with a map and always build a new one. A value of true for gennodes also implies a true value for genblockmap.<br /> <br /> ===get (cvar)===<br /> Displays the value of cvar. This is redundant because typing the name of the cvar alone at the console will accomplish the same thing. <br /> <br /> ===nofilecompression===<br /> boolean: false&lt;br&gt;<br /> This is a debugging cvar used to disable file compression. You should leave it set to false. <br /> <br /> ===noise===<br /> boolean: false&lt;br&gt;<br /> When set to true, the current status of all sound channels is displayed on the screen. <br /> <br /> ===pings===<br /> This lists a very rough estimate of the speed of the connection between your machine and any others in the game. In reality, the values printed by this command aren't even pings; they're just the number of milliseconds that have passed since the last time you received a network packet from the other machines. <br /> <br /> ===playerinfo [player-number]===<br /> Without parameters, lists the numbers for each player in the game. If you specify a player-number, then details about that player's user info will be listed.<br /> <br /> ===playersounds===<br /> Lists the player sounds defined by each player class and skin.<br /> <br /> ===skins===<br /> Lists the names of the skins that were loaded when the game was started. <br /> <br /> ===playmovie (filename)===<br /> Plays a movie. Gameplay will be halted either until the movie finishes or the user presses the Escape key. Under Windows, DirectShow is used to play the movie, so you can watch anything that Windows Media Player can play. Movie playback is not implemented under other operating systems.<br /> <br /> ===playsound (sound)===<br /> Plays a sound on the local machine. Like all other sounds in the game, sound must be properly defined in a SNDINFO lump before you can use it.<br /> <br /> ===print (string)===<br /> Prints a named string to the console. These are the strings you can edit with a bex patch.<br /> <br /> ===scriptstat===<br /> Lists the scripts running on the current level.<br /> <br /> ===soundlinks===<br /> Lists the links between different sounds that use the same sound data. Links are generated dynamically while you play, so it is possible for this command to give different results in different games and even at different times during the same game. <br /> <br /> ===soundlist===<br /> Lists all the sounds defined and the lumps that they alias to. Unlike regular Doom, ZDoom refers to sounds using a long name and uses a SNDINFO lump to map those to the lumps in a WAD file that contain the actual sounds. Logical sounds that refer to the same sound data will have links generated as neccessary to avoid actually loading multiple copies of the same sound into memory. <br /> <br /> ===summon (actor-class)===<br /> Spawns a new actor in front of you. A complete list of actors can be obtained with the dumpclasses actor command. For a list of actors limited to those you can place in an editor, use the dumpmapthings command. It is possible to spawn actors from another game with this command, but they will not be visible unless you provide the missing graphics for them.<br /> <br /> ===spray (decal)===<br /> Sprays a decal on a nearby wall so you can see what it looks like.<br /> <br /> ===stat [page]===<br /> Displays profiling information. When used alone, displays a list of available displays. Use one of those as the page parameter to toggle the display on and off. <br /> <br /> ===stat (blit)===<br /> :Time spent copying the display to video memory. <br /> <br /> ===stat (bots)===<br /> :Time spent doing bot-related activities. <br /> <br /> ===stat (destroys)=== <br /> :Statistics on object deletion each frame. <br /> <br /> ===stat (detail)=== <br /> :Time spent replicating pixels for low detail modes. <br /> <br /> ===stat (fps)=== <br /> :Time spent rendering the scene (not the same as setting vid_fps to true). <br /> <br /> ===stat (purge)===<br /> :Statistics of memory purged from the zone heap each frame. <br /> <br /> ===stat (sight)=== <br /> :Time spent in sight calculations. <br /> <br /> ===stat (sound)===<br /> :Number of active channels and %CPU used for sound. <br /> <br /> ===stat (think)=== <br /> :Time spent running all thinkers. <br /> <br /> ===stat (wallcycles)=== <br /> :Used in conjunction with clearwallcycles to profile the wall drawer. <br /> <br /> ===ticker===<br /> boolean: false&lt;br&gt;<br /> When true, draws a series of dots at the bottom of the screen representing the number of tics it took to display the current frame. (One tic is 1/35th of a second.) When -devparm is specified on the command line, this cvar is automatically set to true. You can get a rough idea of your fps by counting the number of lit dots and dividing that from 35. A better way would be to use vid_fps.<br /> <br /> ===tilt===<br /> boolean: false&lt;br&gt;<br /> Setting this to true causes all planes to be drawn using the sloped drawer, even if they aren't sloped.<br /> <br /> ===tx===<br /> integer: 8&lt;br&gt;<br /> The horizontal scale for textures that don't specify their own.<br /> <br /> ===ty===<br /> integer: 8&lt;br&gt;<br /> The vertical scale for textures that don't specify their own.<br /> <br /> ===warp (x-coordinate) (y-coordinate)===<br /> Sends you to the specified coordinates immediately. This can be used with idmypos to debug problems in a specific area of a map.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=514 2004-01-06T11:26:45Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, etc...<br /> <br /> You access the console by pressing &quot;~&quot; at any time. (This depends on your keyboard layout, for German keyboard, it is &quot;^&quot;, but to summarize it, it is the key above TAB.)<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. (EDIT: That's just a string, i.e. testcolor &quot;ff 00 00&quot;)<br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key?ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> <br /> ===addkeysection (menu-heading) (ini-section-name)&lt;br&gt;===<br /> This command does two things. First, it adds a new heading called menu-heading to the controls menu. You can use the addmenukey command to add your own custom keys beneath this heading. Second, it loads all the bindings from the corresponding ini-section-name section in zdoom.ini. You can use this command multiple times to create different sections in the menu and ini for different sets of commands. If you use a menu-heading that was already added to the menu, new controls added with addmenukey will appear at the end of that section, but the bindings will not be reloaded from the ini. <br /> <br /> ===addmenukey (description) (command)&lt;br&gt;===<br /> Adds a new control to the controls menu. Description is the name of this control in the menu, and command is a console command or alias to be executed when the control is pressed. New controls are added to the last section specified with addkeysection.<br /> <br /> ===addslot (slot) (weapon)===<br /> Adds a single weapon to the list of weapons in a weapon slot.<br /> <br /> ===alias (new-command) [command-string]===<br /> If specified with no parameters, will display a list of all current aliases. If only new-command is specified, it will be removed from the list of aliases. If command-string is also specified, it will be added to the list of aliases as new-command. For example, to create a new command to kill the monsters on the level, you can use the command: <br /> alias massacre &quot;kill monsters&quot;<br /> Then you can use the newly created massacre command to kill all the monsters on the level.<br /> <br /> ===archivecvar (cvar)===<br /> When you create a custom cvar with the set command, it will not normally be saved in the ini. You can use archivecvar after creating the cvar to indicate that the custom cvar's value should persist even after you quit.<br /> <br /> ===atexit [command]===<br /> If you specify a command, it will be added to a list of console commands to execute when the user quits the game. Commands are executed in the reverse order that they were added in. If you do not specify any arguments to atexit, then it will list the current set of commands that will execute when you quit.<br /> <br /> ===bind (key [command string])===<br /> If no parameters are specified, the entire list of bound keys will be printed to the console. If only [key] is specified, the binding for that specific key will be printed. If both [key] and [command string] are specified, [command string] will be bound to [key]. <br /> <br /> ===binddefaults===<br /> Binds all keys to their default commands. This will not unbind any keys that do not have any default bindings, so if you want to properly restore the default controls, you need to use unbindall first. <br /> defaultbind key command<br /> Binds command to the key if and only if key is not already bound and there are no keys already bound to command.<br /> <br /> ===doublebind (key [command string])===<br /> This command works just like bind, except it controls the action that occurs when a key is double-clicked. If a key does not have a doublebinding, then double-clicking it has the same result as pressing it twice. Otherwise, the first press will execute the normal command set with bind, and the second press of the double-click will execute the command set with doublebind. <br /> <br /> ===eval expression [variable]===<br /> Evaluates a mathematical expression and either prints it to the console or stores it in variable. Expressions are written using prefix notation instead of the more common infix notation. Basically, you first specify what you want to do (the operator) and then what you want to do it to (the operands). You must separate operators and operands with spaces. <br /> <br /> Examples: <br /> To compute 2+2: <br /> eval + 2 2To compute 5-3: <br /> eval - 5 3To compute 2+(5*6): <br /> eval + 2 * 5 6To decrease the number of screenblocks: <br /> eval - $screenblocks 1 screenblocksThe supported operators are:<br /> + a b Adds a and b. <br /> - a b Subtracts b from a. <br /> * a b Multiplies a and b. <br /> / a b Divides a by b. <br /> % a b Calculates the remainder of a/b. <br /> ^ a b Raises a to the b-th power . <br /> &lt; a b Produces 1 if a is less than b and 0 if not. <br /> &lt;= a b Produces 1 if a is less than or equal to b and 0 if not. <br /> &gt; a b Produces 1 if a is greater than b and 0 if not. <br /> &gt;= a b Produces 1 if a is greater than or equal to b and 0 if not. <br /> = a b Produces 1 if a is equal to b and 0 if not.<br /> <br /> == a b Produces 1 if a is equal to b and 0 if not. <br /> != a b Produces 1 if a is not equal to b and 0 if it is. <br /> &lt;&gt; a b Produces 1 if a is not equal to b and 0 if is. <br /> xor a b Calculates the bit-wise exclusive-or of a and b. <br /> &amp; a b Calculates the bit-wise and of a and b. <br /> | a b Calculates the bit-wise or of a and b. <br /> &amp;&amp; a b Calculates the logical and of a and b. <br /> || a b Calculates the logical or of a and b. <br /> <br /> ===exec (script-file)===<br /> Executes a series of commands stored in the script-file as if they had been typed in at the console directly. <br /> <br /> ===key value1 [value2]===<br /> Translates all parameters to the command into their corresponding key values which are used internally for command and alias lookup. Probably not very useful for the average user. <br /> <br /> ===puke (script [arguments])===<br /> Executes an ACS script on the current map, optionally passing it up to three numerical arguments. <br /> <br /> ===pullin (wadfile)===<br /> Loads a wadfile at startup. This command is only valid inside .cfg files that have been execed at startup.<br /> <br /> ===set (cvar) (value)===<br /> Sets cvar to value. If cvar does not exist, it will be created. <br /> <br /> ===rebind (binding)===<br /> Changes the binding for the key that caused the rebind command to execute. For obvious reasons, this command cannot be used at the console.<br /> <br /> Example: <br /> <br /> bind b &quot;echo setting 1; rebind \&quot;echo setting 2\&quot;&quot;<br /> <br /> This will cause the first press of b to echo &quot;setting 1&quot; to the console. All future presses of b will echo &quot;setting 2&quot; instead. <br /> <br /> ===unbind (key)===<br /> Removes a binding from the specified key.<br /> <br /> ===unbindall===<br /> Removes all bindings and doublebindings from every key. To restore the default bindings, you can use the binddefaults command. There is no way to restore any custom bindings after issuing this command except by retyping each bind command or using the controls setup menu.<br /> <br /> ===undoublebind (key)===<br /> Removes a doublebinding from the specified key.<br /> <br /> ===unset (cvar)===<br /> Undefines a user-created cvar.<br /> <br /> ==Screenshots==<br /> <br /> ===png_gamma===<br /> float: 0&lt;br&gt;<br /> Controls the gamma level stored in PNG screenshots. If this is 0, then your current gamma setting will be used.<br /> <br /> ===png_level===<br /> integer: 5&lt;br&gt;<br /> This is the level of compression to use for PNG screenshots. 0 is no compression at all, 1 is minimal compression (fastest), 9 is maximum compression (slowest), and intermediate values offer intermediate compression. 5 is offers a decent trade-of between file size and compression time. An uncompressed image will not neccessarily save faster than a compressed image, because the extra time needed to write out a complete uncompressed image may be longer than the time required to compress the image. If you need to create screenshots as quickly as possible, consider setting screenshot_type to &quot;pcx&quot;. <br /> <br /> ===screenshot [file]===<br /> Dumps a copy of the screen to disk as a PNG or PCX file. If file is not specified, the screenshot will be saved to the directory the game was run from with a name of the form doom????.png. <br /> <br /> ===screenshot_quiet===<br /> boolean: false&lt;br&gt;<br /> Setting this to true will suppress the messages informing you what file a screenshot was saved to.<br /> <br /> ===screenshot_type===<br /> string: &quot;png&quot;&lt;br&gt;<br /> Determines the type of screenshots that will be saved. This can be either &quot;png&quot; or &quot;pcx&quot;. In my empirical studies, PNG screenshots are about half the size of pcx screenshots. PCX screenshots have the advantage that they require less time to create so are most useful for rapid screenshot generation. The following sequence of console commands will take a screenshot every frame. You can use an external program to assemble these into a video, if desired. <br /> <br /> screenshot_type &quot;png&quot;&lt;br&gt;<br /> screenshot_quiet true&lt;br&gt;<br /> alias autoshot &quot;screenshot; wait 1; autoshot&quot;&lt;br&gt;<br /> autoshot&lt;br&gt;<br /> <br /> If you use the autoshot alias, the command alias autoshot will stop automatic screenshot taking before you hit 10000 screenshots (approximately 4 minutes, 45 seconds).<br /> <br /> ===storesavepic===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will produce smaller savegames (by about 14k typically) by not storing a screenshot inside the savegame.<br /> <br /> ==Chatting==<br /> <br /> ===chat_substitution===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want to chat using special keywords that will be replaced with appropriate text when your messages are sent. The supported keywords are:<br /> <br /> $health &lt;br&gt;<br /> Replaced by your current health. &lt;br&gt;<br /> $weapon &lt;br&gt;<br /> Replaced by the name of your current weapon. &lt;br&gt;<br /> $armor &lt;br&gt;<br /> Replaced by your current armor count. &lt;br&gt;<br /> $ammocount &lt;br&gt;<br /> Replaced by your current ammo count. &lt;br&gt;<br /> $ammo &lt;br&gt;<br /> Replaced by the name of your current ammo.<br /> <br /> As an example, if you just started a new game of Doom and have chat substitution turned on, when you send the message &quot;My health is $health, and I am using a $weapon&quot;, the message that is actually sent will be &quot;My health is 100, and I am using a Pistol&quot;.<br /> <br /> chatmacro0&lt;br&gt;<br /> chatmacro1&lt;br&gt;<br /> chatmacro2&lt;br&gt;<br /> chatmacro3&lt;br&gt;<br /> chatmacro4&lt;br&gt;<br /> chatmacro5&lt;br&gt;<br /> chatmacro6&lt;br&gt;<br /> chatmacro7&lt;br&gt;<br /> chatmacro8&lt;br&gt;<br /> chatmacro9&lt;br&gt;<br /> string&lt;br&gt;<br /> These are all strings that can be assigned to hotkeys in chat mode. To use these, enter chat mode and then hold down Alt and press one of the number keys. The string stored in the corresponding chatmacro cvar will be sent as if you had typed it yourself. <br /> <br /> ===messagemode===<br /> Enters message entry mode. Anything typed while in this mode will be sent to everyone else as if you had used the say command once you press enter. <br /> <br /> ===messagemode2===<br /> This is just like messagemode except that the message is only sent to other members of your team. If teamplay is false or you don't have a team, then this command will work just like messagemode and send the message to everyone. <br /> <br /> ===say (message)===<br /> Sends a message to everyone playing. If your message begins with &quot;/me&quot; then &quot;/me&quot; will be replaced by your name ala IRC. <br /> <br /> ===say_team (message)===<br /> This is just like say except it only sends a message to your teammates. If teamplay is inactive, then this command will act exactly like say and send the message to everyone.<br /> <br /> ==Cheating==<br /> <br /> ===sv_cheats===<br /> boolean: false<br /> When true, cheats will be allowed in Nightmare difficulty and network games. For purposes of fairness, this cvar can only be set from the command line when you run ZDoom. This is to avoid situations where the key player in a multiplayer game (player 1) could go to the console and type something like this:<br /> <br /> sv_cheats 1<br /> god<br /> sv_cheats 0<br /> <br /> whereby rendering himself immune to the attacks of others.<br /> <br /> ===anubis===<br /> Toggles monster fear on and off. Scared monsters will run away from you and attack less frequently.<br /> <br /> ===fly===<br /> Toggles fly mode on and off.<br /> <br /> ===give (item)===<br /> Gives an item to the player. Give understands the following special items: <br /> all - gives you everything <br /> health - gives you full health <br /> weapons - gives you every weapon <br /> ammo - gives you full ammo <br /> armor - gives you full armor <br /> keys - gives you every key <br /> It also understands the names of individual inventory items. Use the command dumpclasses inventory for a complete list of these. <br /> <br /> ===god===<br /> Toggles God (Degreelessness) mode on/off. While active, you cannot be hurt by normal attacks (although telefragging will still kill you). Also known as iddqd. <br /> <br /> ===iddqd===<br /> The same as god, except it also gives you 100 health.<br /> <br /> ===kill [monsters]===<br /> If used as &quot;kill monsters&quot;, will kill all monsters on the level. Otherwise, it will kill you instead. This command is broken in netgames, so don't use it unless you are playing a single player game. <br /> <br /> ===logfile [log-file]===<br /> If log-file is not specified, console logging will be stopped (if active). Otherwise, a file named log-file will be created on disk, and all console output will be recorded in it as well as on the screen. <br /> <br /> ===mdk===<br /> This cheat will kill whatever you are looking at.<br /> <br /> ===morphme===<br /> Transforms you into a chicken in Heretic and a pig in Hexen and Doom (The latter only happens if you have the releven graphics present).<br /> <br /> ===noclip===<br /> Toggles noclipping mode on/off. <br /> <br /> ===notarget===<br /> Toggles notarget mode on/off. While active, monsters will not target you unless you hurt them first. In &quot;modern FPS&quot;, monsters &quot;can't find you&quot; when in notarget mode. This is not the case with ZDoom.<br /> <br /> ===powerup===<br /> Powers you up in Heretic as if you had used a Tome of Power.<br /> <br /> ===sv_fastweapons (0-2)===<br /> Increases speed of weapons in Doom, Heretic, and Hexen. Setting to 2 makes weapons even faster.<br /> <br /> ===turbo===<br /> float: 100&lt;br&gt;<br /> This cvar affects how quickly the player moves. A value of 100 will cause the player to move at normal speed, 200 will cause the player to move at 200% of normal speed, 50 will cause the player to move at 50% of normal speed, etc. Valid values range from 10 to 256.<br /> <br /> ==Display==<br /> <br /> ===bumpgamma===<br /> Increases the current gamma level by 0.1. If the new gamma level would be greater than 3.0, it wraps the gamma around to 1.0 <br /> <br /> ===cl_bbannounce===<br /> boolean: false&lt;br&gt;<br /> When true, enables the Bloodbath announcer for deathmatch games. The Bloodbath announcer is &quot;The Voice&quot; from Monolith Software's Blood game. To hear the announcer, you need to load Blood's sounds.rff either at the command line or through one of zdoom.ini's [*.Autoload] sections. You can get this file either from the demo or full version of Blood. If you don't have sounds.rff, you can still see the announcer's messages even though you won't hear anything. <br /> <br /> ===cl_showmultikills===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player makes several kills in a short period of time.<br /> <br /> ===cl_showsprees===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player is on a killing spree.<br /> <br /> ===cl_spreaddecals===<br /> boolean: true&lt;br&gt;<br /> ZDoom clips decals to sidedefs. In order to hide this, the game will create as many duplicate decals on adjoining sidedefs as needed to make it appear that there is only one unbroken decal on the wall. Set this cvar to false if you don't want this.<br /> <br /> ===con_centernotify===<br /> boolean: false for Doom, true for Heretic and Hexen&lt;br&gt;<br /> When true, notify messages at the top of the screen are centered. Otherwise, they are justified against the left margin.<br /> <br /> ===con_midtime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that messages in the middle of the screen will be displayed before they dispapper. <br /> <br /> ===con_notifytime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that new messages will stay at the top of the screen before they start scrolling away. <br /> <br /> ===con_scaletext===<br /> boolean: false&lt;br&gt;<br /> If this cvar is true, then message text will be scaled to larger sizes depending on the screen resolution so that it will stay approximately the same size it would be on a 320x200 screen. <br /> <br /> ===crosshair===<br /> integer: 0&lt;br&gt;<br /> If this cvar is non-zero, it draws a crosshair. If this cvar is negative, the crosshair is translucent, otherwise it is opaque. The specific crosshair drawn depends on the value of this cvar. <br /> <br /> ===crosshaircolor===<br /> color: &quot;ff 00 00&quot;&lt;br&gt;<br /> This is the crosshair's color if crosshairhealth is false.<br /> <br /> ===crosshairgrow===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to temporarily enlarge each time you pick up an item.<br /> <br /> ===crosshairhealth===<br /> boolean: true&lt;br&gt;<br /> When true, the crosshair's color reflects your current health. Green is healthy, red is near death, and intermediate colors are somewhere in between. Set this to false, if you want the crosshair to have a constant color (specified by the crosshaircolor cvar) instead.<br /> <br /> ===crosshairscale===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to always appear the same size at all resolutions. Leaving it at false causes the crosshair to be drawn normally.<br /> <br /> ===gamma===<br /> float: 1.0&lt;br&gt;<br /> Controls the amount of gamma correction applied to the display. 1.0 is equivalent to no correction, while larger numbers translate into a brighter display, and smaller numbers translate into a darker display. 0.0 is invalid and will be rejected. Negative numbers are technically invalid but will be accepted solely for the novelty value doing so provides. <br /> <br /> ===hud_scale===<br /> boolean: false&lt;br&gt;<br /> Controls scaling of the fullscreen hud. At resolutions of 640x400 or above, setting this cvar to true will cause the icons to be scaled to approximately the same size they would be at 320x200. If this cvar is false, the icons will always be drawn without any scaling. <br /> <br /> ===msg===<br /> integer: 0&lt;br&gt;<br /> This is the minimum message level that you will see. You will not see any messages with a lower priority than this. The different message levels are: <br /> <br /> #Item pickup <br /> #Obituaries <br /> #Critical messages <br /> #Chat messages <br /> #Chat messages from a teammate <br /> <br /> ===msg0color===<br /> integer: 6&lt;br&gt;<br /> This cvar controls the color used to display level 0 (item pickup) messages. Available colors are: <br /> <br /> #Brick <br /> #Tan <br /> #Gray <br /> #Green <br /> #Brown <br /> #Gold <br /> #Red <br /> #Blue <br /> #Orange <br /> #White <br /> #Yellow <br /> <br /> ===msg1color===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display level 1 (obituary) messages. Available colors are the same as for&quot; msg0color. <br /> <br /> ===msg2color===<br /> integer: 2&lt;br&gt;<br /> This cvar selects the color used to display level 2 (critical) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg3color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 3 (chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg4color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 4 (team chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor2===<br /> integer: 4&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen that are sent to everyone. Available colors are the same as for msg0color. <br /> <br /> ===st_scale===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, the status bar will be scaled so that it covers the entire width of the screen in higher resolutions. At low resolutions this may look ugly, but at high resolutions it should look good enough.<br /> <br /> ==Renderer==<br /> <br /> ===r_columnmethod===<br /> integer: 1&lt;br&gt;<br /> Selects which of two algorithms to use to draw sprites and masked textures. Method 0 is the original algorithm used by DOOM. Method 1 is a new algorithm optimized for Pentium IIs and can perform significantly better with that or comparable processors. Ironically, method 0 is slightly faster than method 1 on Pentium III and Athlon processors (though not significantly so). <br /> <br /> ===r_detail===<br /> integer: 0&lt;br&gt;<br /> This cvar selects the detail level of the view window. Valid values are: <br /> <br /> #Normal detail level. Equivalent to Doom's high detail mode. <br /> #Double pixels horizontally. Equivalent to Doom's low detail mode. <br /> #Double pixels vertically. <br /> #Double pixels horizontally and vertically. <br /> <br /> Because of the way the renderer works, doubling pixels horizontally offers more of a speed-up than doubling them vertically does. Unless you have a very slow computer, there should be no reason to use any detail level other than 0. <br /> <br /> ===r_drawflat===<br /> boolean: false&lt;br&gt;<br /> When set to 0, segs will be drawn as solid colors instead of textures. This is useful if you want to see how a node builder split a level's linedefs. Otherwise, it just looks ugly. <br /> <br /> ===r_drawfuzzbr===<br /> boolean: true&lt;br&gt;<br /> When set to false, the &quot;fuzz&quot; effect on spectres and partially invisible players will be replaced with translucency. <br /> <br /> ===r_drawmirrors===<br /> boolean: true&lt;br&gt;<br /> Setting this false will disable the display of mirrors.<br /> <br /> ===r_drawplayersprites===<br /> boolean: true&lt;br&gt;<br /> When false, the game will not draw the player's weapon or muzzle flash, which can be nice for screenshots. <br /> <br /> ===r_drawtrans===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will disable all translucency effects in the game.<br /> <br /> ===r_fogboundary===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will disable the display of fog boundaries. Fog boundaries are sections where two areas with different fog colors meet. If the boundary is not drawn, then it will look like there is no fog at all in front of the boundary. Some old levels may look bad with fog boundary drawing enabled, which is why this cvar is available.<br /> <br /> ===r_particles===<br /> boolean: true&lt;br&gt;<br /> If set to true, particles are drawn. Otherwise, they aren't. <br /> <br /> ===r_stretchsky===<br /> boolean: true&lt;br&gt;<br /> Controls whether or not short sky textures are stretched so that you don't see them wrap when you look up. <br /> <br /> ===r_viewsize===<br /> string&lt;br&gt;<br /> This cvar contains the width and height of the current view window. This cvar is read only. <br /> <br /> ===r_visibility [visibility]===<br /> Without any parameters, displays the current visibility. With a parameter, the visibility is set. Standard visibility for the Doom engine is 8. Visibility determines how quickly light drops off with distance from the viewer. At 0 visibility, there is no change in lighting with depth.<br /> <br /> ==Video==<br /> <br /> ===fullscreen===<br /> boolean: true&lt;br&gt;<br /> If this cvar is true, the game will be displayed fullscreen. Otherwise, it will be drawn in a window. Some video cards may require that you have fullscreen false in order to run ZDoom. <br /> <br /> ===vid_attachedsurfaces (Win32 only)===<br /> boolean: false&lt;br&gt;<br /> Controls how the game allocates video memory. False is the standard setting and will always produce a useable display. If you find that there are patches of pure black and pure white on the screen (especially noticeable when a demon is right in your face), try setting this to true. Certain old Windows 95 video drivers are said to need this fix, and it is also necessary under NT 4. Unfortunately, many new video drivers (including those under NT 4) will produce a scrambled display if the screen width is not 512 or 1024 pixels and this is set to true.<br /> <br /> ===vid_currentmode===<br /> Displays the resolution of the current video mode.<br /> <br /> ===vid_defbits===<br /> integer: 8&lt;br&gt;<br /> Ignored. This cvar is meant to specify the default screen depth, but the setting is currently ignored because only 256-color displays are supported.<br /> <br /> ===vid_defheight===<br /> integer: 200&lt;br&gt;<br /> Specifies the default screen height to use if not overridden at the command line by the -height switch.<br /> <br /> ===vid_defwidth===<br /> integer: 320&lt;br&gt;<br /> Specifies the default screen width to use if not overridden at the command line with the -width switch.<br /> <br /> ===vid_listmodes===<br /> Lists all resolutions supported by the current display driver.<br /> <br /> ===vid_fps===<br /> boolean: false&lt;br&gt;<br /> When true, displays the average framerate over the past second in the lower-left corner of the screen. Because Doom's internal game rate and frame rate are linked, the framerate will never be (much) above 35 fps.<br /> <br /> ===vid_noblitter (Win32 only)===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will allow the use of the hardware to assist moving image data to video memory. When I initial wrote the code to use the blitter, it was faster than not using it. Now the blitter is slower, and I can't figure out why, so the default is true.<br /> <br /> ===vid_palettehack (Win32 only)===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, the game will refresh the palette every time the screen is redrawn. This can be useful with some buggy video drivers. If the display is fine without it, leave it that way because this can slightly slow things down.<br /> <br /> ===vid_setmode (width) (height) [depth]===<br /> Sets the screen mode to width x height with an optional color depth (if your video hardware supports it). Only a depth of 8 is supported. See also vid_currentmode, vid_listmodes<br /> <br /> ===vid_vsync (Win32 only)===<br /> boolean: true&lt;br&gt;<br /> Set this to false to disable vsync. Not all video cards support disabling vsync.<br /> <br /> ==Bots==<br /> <br /> ===addbot [name]===<br /> Spawns a bot. If a name is given, the corresponding bot in bots.cfg will be spawned. Otherwise, a bot will be picked at random from bots.cfg. <br /> <br /> ===bot_allowspy===<br /> boolean: false&lt;br&gt;<br /> Allows you to see through the eyes of bots during botmatch games. <br /> <br /> ===bot_observer===<br /> boolean: false&lt;br&gt;<br /> When set to 1, the player will experience minimal interaction with the world, and bots will ignore him. <br /> <br /> ===listbots===<br /> Lists the bots available in bots.cfg, and indicates which are currently playing. <br /> <br /> ===removebots===<br /> Removes any bots from the game. Bots will also be automatically removed from network games when the arbitrator quits.<br /> <br /> ==Automap==<br /> <br /> ===togglemap===<br /> Toggles the automap on/off.<br /> <br /> ===am_backcolor===<br /> color: &quot;6c 54 40&quot;&lt;br&gt;<br /> The color of the automap background. Changes to this cvar take effect the next time the automap is activated. <br /> <br /> ===am_cdwallcolor===<br /> color: &quot;4c 38 20&quot;&lt;br&gt;<br /> The color of two-sided lines that have a different ceiling height on each side. <br /> <br /> ===am_fdwallcolor===<br /> color: &quot;88 70 58&quot;&lt;br&gt;<br /> The color of two-sided lines that have a different floor height on each side. <br /> <br /> ===am_gridcolor===<br /> color: &quot;8b 5a 2b&quot;&lt;br&gt;<br /> The color of the automap grid. <br /> <br /> ===am_interlevelcolor===<br /> color: &quot;ff 00 00&quot;&lt;br&gt;<br /> The color of inter-level teleporters. These are teleporters that teleport you to a different map. <br /> <br /> ===am_intralevelcolor===<br /> color: &quot;00 00 ff&quot;&lt;br&gt;<br /> The color of intra-level teleporters. These are teleporters that teleport you to a different location on the same map. <br /> <br /> ===am_lockedcolor===<br /> color: &quot;00 00 98&quot;&lt;br&gt;<br /> The color of lines that open locked doors. <br /> <br /> ===am_notseencolor===<br /> color: &quot;6c 6c 6c&quot;&lt;br&gt;<br /> The color of lines on the automap that haven't yet been seen. Visible with a computer area map. <br /> <br /> ===am_overlay===<br /> boolean: false&lt;br&gt;<br /> Normally, the togglemap command switches the automap between fully off and fully on. Setting this cvar to &quot;1&quot; will cause togglemap to draw the automap on top of the player's view before it draws the automap fullscreen. (Bad description, I know. Just try it) <br /> <br /> ===am_ovotherwallscolor===<br /> color: &quot;00 88 44&quot;&lt;br&gt;<br /> The color of passable lines on the automap when the map is overlayed. <br /> <br /> ===am_ovtelecolor===<br /> color: &quot;ff ff 00&quot;&lt;br&gt;<br /> The color of teleporters—both inter- and intra-level—on the overlayed automap.<br /> <br /> ===am_ovthingcolor===<br /> color: &quot;e8 88 00&quot;&lt;br&gt;<br /> The color of things visible with the automap cheat when the map is overlayed. <br /> <br /> ===am_ovunseencolor===<br /> color: &quot;00 22 6e&quot;&lt;br&gt;<br /> The color of unseen lines on the automap when the map is overlayed. <br /> <br /> ===am_ovwallcolor===<br /> color: &quot;00 ff 00&quot;&lt;br&gt;<br /> The color of impassable walls when the automap is overlayed. <br /> <br /> ===am_ovyourcolor===<br /> color: &quot;fc e8 d8&quot;&lt;br&gt;<br /> The color of the arrow representing the player in single player games when the map is overlayed. <br /> <br /> ===am_rotate===<br /> boolean: false&lt;br&gt;<br /> Normally, the automap is always drawn such that north is at the top of the screen. Setting this cvar to &quot;1&quot; causes the automap to be drawn so that lines toward the top of the screen are always directly in front of the player's view. This can be particularly useful when the automap is overlayed. <br /> <br /> ===am_showitems===<br /> boolean: false&lt;br&gt;<br /> When true, the fullscreen automap will display a count of all the &quot;special&quot; items you have found on the map. These are the same items that are used to determine the Items stat on the intermission screen.<br /> <br /> ===am_showmonsters===<br /> boolean: true&lt;br&gt;<br /> When true, the fullscreen automap will display a count of the number of monsters that have been killed in the current level and the total number of monsters in the level. <br /> <br /> ===am_showsecrets===<br /> boolean: true&lt;br&gt;<br /> When true, the fullscreen automap will display a count of the number of secrets that have been found in the current level and the total number of secrets in the level. <br /> <br /> ===am_showtime===<br /> boolean: true&lt;br&gt;<br /> When true, the fullscreen automap will display the total amount of time you have been in a level (excluding time that has been paused). <br /> <br /> ===am_thingcolor===<br /> color: &quot;fc fc fc&quot;&lt;br&gt;<br /> The color of things revealed with the map cheat. <br /> <br /> ===am_tswallcolor===<br /> color: &quot;88 88 88&quot;&lt;br&gt;<br /> The color of two-sided lines that don't have any difference in floor or ceiling heights on either side. Only seen using map cheat. <br /> <br /> ===am_usecustomcolors===<br /> boolean: true&lt;br&gt;<br /> When true, the automap uses the colors specified by the am_* cvars, otherwise it uses the standard DOOM automap colors. <br /> <br /> am_wallcolor&lt;br&gt;<br /> color: &quot;2c 18 08&quot;&lt;br&gt;<br /> The color of one-sided and secret walls in the automap. <br /> <br /> ===am_xhaircolor===<br /> color: &quot;80 80 80&quot;&lt;br&gt;<br /> The color of the &quot;crosshair&quot; dot in the center of the automap. <br /> <br /> ===am_yourcolor===<br /> color: &quot;fc e8 d8&quot;&lt;br&gt;<br /> The color of the arrow representing the player in single player games.<br /> <br /> ==Player Settings==<br /> <br /> ===autoaim===<br /> float: 5000&lt;br&gt;<br /> This represents the vertical distance from an object that the player's sight must be before that object is aimed at. Setting this cvar to &quot;0&quot; disables autoaiming, while large values such as &quot;5000&quot; will reproduce the original DOOM behavior of always autoaiming. <br /> <br /> ===color===<br /> color&lt;br&gt;<br /> This is your player's color. The default varies depending on which game you are playing. <br /> <br /> ===gender===<br /> string: &quot;male&quot;&lt;br&gt;<br /> This is the gender of your player. Valid values are &quot;male&quot;, &quot;female&quot;, and &quot;neuter&quot;. Anything else will be treated as male. When you die, certain messages will be altered to reflect the gender selected here. Unfortunately, I don't provide any non-male player sounds, so you'll still sound like a man no matter what this cvar is set to unless you provide your own sounds. <br /> <br /> ===movebob===<br /> float: 0.25&lt;br&gt;<br /> Controls how much the view bobs up and down while you are moving. 0 would be no bob at all.<br /> <br /> ===name===<br /> string: &quot;Player&quot;&lt;br&gt;<br /> This is your player's name. This is only really useful in a multiplayer game, but it can also be set for single player. <br /> <br /> ===neverswitchonpickup===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, you won't automatically switch to a new weapon when you pick one up. <br /> <br /> ===skin===<br /> string: &quot;base&quot;&lt;br&gt;<br /> This is your player's skin. &quot;Base&quot; is the name of the regular Doom marine and is always available. Additional skins are contained in wad files that you either load with -file at the command line or autoload using the .ini or skins directory. <br /> <br /> ===stillbob===<br /> float: 0&lt;br&gt;<br /> Controls the amount of bobbing up and down that occurs when standing still. 0 is no bobbing at all.<br /> <br /> ===team===<br /> integer: 255&lt;br&gt;<br /> This is the team that your player belongs to. It is only meaningful during deathmatch games. There are four teams available: <br /> <br /> #Red <br /> #Blue <br /> #Green <br /> #Gold<br /> <br /> Using a team of 255 is special and will automatically assign you to whichever team has fewer players.<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=513 2004-01-06T11:25:37Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, etc...<br /> <br /> You access the console by pressing &quot;~&quot; at any time. (This depends on your keyboard layout, for German keyboard, it is &quot;^&quot;, but to summarize it, it is the key above TAB.)<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. (EDIT: That's just a string, i.e. testcolor &quot;ff 00 00&quot;)<br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key?ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> <br /> ===addkeysection (menu-heading) (ini-section-name)&lt;br&gt;===<br /> This command does two things. First, it adds a new heading called menu-heading to the controls menu. You can use the addmenukey command to add your own custom keys beneath this heading. Second, it loads all the bindings from the corresponding ini-section-name section in zdoom.ini. You can use this command multiple times to create different sections in the menu and ini for different sets of commands. If you use a menu-heading that was already added to the menu, new controls added with addmenukey will appear at the end of that section, but the bindings will not be reloaded from the ini. <br /> <br /> ===addmenukey (description) (command)&lt;br&gt;===<br /> Adds a new control to the controls menu. Description is the name of this control in the menu, and command is a console command or alias to be executed when the control is pressed. New controls are added to the last section specified with addkeysection.<br /> <br /> ===addslot (slot) (weapon)===<br /> Adds a single weapon to the list of weapons in a weapon slot.<br /> <br /> ===alias (new-command) [command-string]===<br /> If specified with no parameters, will display a list of all current aliases. If only new-command is specified, it will be removed from the list of aliases. If command-string is also specified, it will be added to the list of aliases as new-command. For example, to create a new command to kill the monsters on the level, you can use the command: <br /> alias massacre &quot;kill monsters&quot;<br /> Then you can use the newly created massacre command to kill all the monsters on the level.<br /> <br /> ===archivecvar (cvar)===<br /> When you create a custom cvar with the set command, it will not normally be saved in the ini. You can use archivecvar after creating the cvar to indicate that the custom cvar's value should persist even after you quit.<br /> <br /> ===atexit [command]===<br /> If you specify a command, it will be added to a list of console commands to execute when the user quits the game. Commands are executed in the reverse order that they were added in. If you do not specify any arguments to atexit, then it will list the current set of commands that will execute when you quit.<br /> <br /> ===bind (key [command string])===<br /> If no parameters are specified, the entire list of bound keys will be printed to the console. If only [key] is specified, the binding for that specific key will be printed. If both [key] and [command string] are specified, [command string] will be bound to [key]. <br /> <br /> ===binddefaults===<br /> Binds all keys to their default commands. This will not unbind any keys that do not have any default bindings, so if you want to properly restore the default controls, you need to use unbindall first. <br /> defaultbind key command<br /> Binds command to the key if and only if key is not already bound and there are no keys already bound to command.<br /> <br /> ===doublebind (key [command string])===<br /> This command works just like bind, except it controls the action that occurs when a key is double-clicked. If a key does not have a doublebinding, then double-clicking it has the same result as pressing it twice. Otherwise, the first press will execute the normal command set with bind, and the second press of the double-click will execute the command set with doublebind. <br /> <br /> ===eval expression [variable]===<br /> Evaluates a mathematical expression and either prints it to the console or stores it in variable. Expressions are written using prefix notation instead of the more common infix notation. Basically, you first specify what you want to do (the operator) and then what you want to do it to (the operands). You must separate operators and operands with spaces. <br /> <br /> Examples: <br /> To compute 2+2: <br /> eval + 2 2To compute 5-3: <br /> eval - 5 3To compute 2+(5*6): <br /> eval + 2 * 5 6To decrease the number of screenblocks: <br /> eval - $screenblocks 1 screenblocksThe supported operators are:<br /> + a b Adds a and b. <br /> - a b Subtracts b from a. <br /> * a b Multiplies a and b. <br /> / a b Divides a by b. <br /> % a b Calculates the remainder of a/b. <br /> ^ a b Raises a to the b-th power . <br /> &lt; a b Produces 1 if a is less than b and 0 if not. <br /> &lt;= a b Produces 1 if a is less than or equal to b and 0 if not. <br /> &gt; a b Produces 1 if a is greater than b and 0 if not. <br /> &gt;= a b Produces 1 if a is greater than or equal to b and 0 if not. <br /> = a b Produces 1 if a is equal to b and 0 if not.<br /> <br /> == a b Produces 1 if a is equal to b and 0 if not. <br /> != a b Produces 1 if a is not equal to b and 0 if it is. <br /> &lt;&gt; a b Produces 1 if a is not equal to b and 0 if is. <br /> xor a b Calculates the bit-wise exclusive-or of a and b. <br /> &amp; a b Calculates the bit-wise and of a and b. <br /> | a b Calculates the bit-wise or of a and b. <br /> &amp;&amp; a b Calculates the logical and of a and b. <br /> || a b Calculates the logical or of a and b. <br /> <br /> ===exec (script-file)===<br /> Executes a series of commands stored in the script-file as if they had been typed in at the console directly. <br /> <br /> ===key value1 [value2]===<br /> Translates all parameters to the command into their corresponding key values which are used internally for command and alias lookup. Probably not very useful for the average user. <br /> <br /> ===puke (script [arguments])===<br /> Executes an ACS script on the current map, optionally passing it up to three numerical arguments. <br /> <br /> ===pullin (wadfile)===<br /> Loads a wadfile at startup. This command is only valid inside .cfg files that have been execed at startup.<br /> <br /> ===set (cvar) (value)===<br /> Sets cvar to value. If cvar does not exist, it will be created. <br /> <br /> ===rebind (binding)===<br /> Changes the binding for the key that caused the rebind command to execute. For obvious reasons, this command cannot be used at the console.<br /> <br /> Example: <br /> <br /> bind b &quot;echo setting 1; rebind \&quot;echo setting 2\&quot;&quot;<br /> <br /> This will cause the first press of b to echo &quot;setting 1&quot; to the console. All future presses of b will echo &quot;setting 2&quot; instead. <br /> <br /> ===unbind (key)===<br /> Removes a binding from the specified key.<br /> <br /> ===unbindall===<br /> Removes all bindings and doublebindings from every key. To restore the default bindings, you can use the binddefaults command. There is no way to restore any custom bindings after issuing this command except by retyping each bind command or using the controls setup menu.<br /> <br /> ===undoublebind (key)===<br /> Removes a doublebinding from the specified key.<br /> <br /> ===unset (cvar)===<br /> Undefines a user-created cvar.<br /> <br /> ==Screenshots==<br /> <br /> ===png_gamma===<br /> float: 0&lt;br&gt;<br /> Controls the gamma level stored in PNG screenshots. If this is 0, then your current gamma setting will be used.<br /> <br /> ===png_level===<br /> integer: 5&lt;br&gt;<br /> This is the level of compression to use for PNG screenshots. 0 is no compression at all, 1 is minimal compression (fastest), 9 is maximum compression (slowest), and intermediate values offer intermediate compression. 5 is offers a decent trade-of between file size and compression time. An uncompressed image will not neccessarily save faster than a compressed image, because the extra time needed to write out a complete uncompressed image may be longer than the time required to compress the image. If you need to create screenshots as quickly as possible, consider setting screenshot_type to &quot;pcx&quot;. <br /> <br /> ===screenshot [file]===<br /> Dumps a copy of the screen to disk as a PNG or PCX file. If file is not specified, the screenshot will be saved to the directory the game was run from with a name of the form doom????.png. <br /> <br /> ===screenshot_quiet===<br /> boolean: false&lt;br&gt;<br /> Setting this to true will suppress the messages informing you what file a screenshot was saved to.<br /> <br /> ===screenshot_type===<br /> string: &quot;png&quot;&lt;br&gt;<br /> Determines the type of screenshots that will be saved. This can be either &quot;png&quot; or &quot;pcx&quot;. In my empirical studies, PNG screenshots are about half the size of pcx screenshots. PCX screenshots have the advantage that they require less time to create so are most useful for rapid screenshot generation. The following sequence of console commands will take a screenshot every frame. You can use an external program to assemble these into a video, if desired. <br /> <br /> screenshot_type &quot;png&quot;&lt;br&gt;<br /> screenshot_quiet true&lt;br&gt;<br /> alias autoshot &quot;screenshot; wait 1; autoshot&quot;&lt;br&gt;<br /> autoshot&lt;br&gt;<br /> <br /> If you use the autoshot alias, the command alias autoshot will stop automatic screenshot taking before you hit 10000 screenshots (approximately 4 minutes, 45 seconds).<br /> <br /> ===storesavepic===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will produce smaller savegames (by about 14k typically) by not storing a screenshot inside the savegame.<br /> <br /> ==Chatting==<br /> <br /> ===chat_substitution===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want to chat using special keywords that will be replaced with appropriate text when your messages are sent. The supported keywords are:<br /> <br /> $health &lt;br&gt;<br /> Replaced by your current health. &lt;br&gt;<br /> $weapon &lt;br&gt;<br /> Replaced by the name of your current weapon. &lt;br&gt;<br /> $armor &lt;br&gt;<br /> Replaced by your current armor count. &lt;br&gt;<br /> $ammocount &lt;br&gt;<br /> Replaced by your current ammo count. &lt;br&gt;<br /> $ammo &lt;br&gt;<br /> Replaced by the name of your current ammo.<br /> <br /> As an example, if you just started a new game of Doom and have chat substitution turned on, when you send the message &quot;My health is $health, and I am using a $weapon&quot;, the message that is actually sent will be &quot;My health is 100, and I am using a Pistol&quot;.<br /> <br /> chatmacro0&lt;br&gt;<br /> chatmacro1&lt;br&gt;<br /> chatmacro2&lt;br&gt;<br /> chatmacro3&lt;br&gt;<br /> chatmacro4&lt;br&gt;<br /> chatmacro5&lt;br&gt;<br /> chatmacro6&lt;br&gt;<br /> chatmacro7&lt;br&gt;<br /> chatmacro8&lt;br&gt;<br /> chatmacro9&lt;br&gt;<br /> string&lt;br&gt;<br /> These are all strings that can be assigned to hotkeys in chat mode. To use these, enter chat mode and then hold down Alt and press one of the number keys. The string stored in the corresponding chatmacro cvar will be sent as if you had typed it yourself. <br /> <br /> ===messagemode===<br /> Enters message entry mode. Anything typed while in this mode will be sent to everyone else as if you had used the say command once you press enter. <br /> <br /> ===messagemode2===<br /> This is just like messagemode except that the message is only sent to other members of your team. If teamplay is false or you don't have a team, then this command will work just like messagemode and send the message to everyone. <br /> <br /> ===say (message)===<br /> Sends a message to everyone playing. If your message begins with &quot;/me&quot; then &quot;/me&quot; will be replaced by your name ala IRC. <br /> <br /> ===say_team (message)===<br /> This is just like say except it only sends a message to your teammates. If teamplay is inactive, then this command will act exactly like say and send the message to everyone.<br /> <br /> ==Cheating==<br /> <br /> ===sv_cheats===<br /> boolean: false<br /> When true, cheats will be allowed in Nightmare difficulty and network games. For purposes of fairness, this cvar can only be set from the command line when you run ZDoom. This is to avoid situations where the key player in a multiplayer game (player 1) could go to the console and type something like this:<br /> <br /> sv_cheats 1<br /> god<br /> sv_cheats 0<br /> <br /> whereby rendering himself immune to the attacks of others.<br /> <br /> ===anubis===<br /> Toggles monster fear on and off. Scared monsters will run away from you and attack less frequently.<br /> <br /> ===fly===<br /> Toggles fly mode on and off.<br /> <br /> ===give (item)===<br /> Gives an item to the player. Give understands the following special items: <br /> all - gives you everything <br /> health - gives you full health <br /> weapons - gives you every weapon <br /> ammo - gives you full ammo <br /> armor - gives you full armor <br /> keys - gives you every key <br /> It also understands the names of individual inventory items. Use the command dumpclasses inventory for a complete list of these. <br /> <br /> ===god===<br /> Toggles God (Degreelessness) mode on/off. While active, you cannot be hurt by normal attacks (although telefragging will still kill you). Also known as iddqd. <br /> <br /> ===iddqd===<br /> The same as god, except it also gives you 100 health.<br /> <br /> ===kill [monsters]===<br /> If used as &quot;kill monsters&quot;, will kill all monsters on the level. Otherwise, it will kill you instead. This command is broken in netgames, so don't use it unless you are playing a single player game. <br /> <br /> ===logfile [log-file]===<br /> If log-file is not specified, console logging will be stopped (if active). Otherwise, a file named log-file will be created on disk, and all console output will be recorded in it as well as on the screen. <br /> <br /> ===mdk===<br /> This cheat will kill whatever you are looking at.<br /> <br /> ===morphme===<br /> Transforms you into a chicken in Heretic and a pig in Hexen and Doom (The latter only happens if you have the releven graphics present).<br /> <br /> ===noclip===<br /> Toggles noclipping mode on/off. <br /> <br /> ===notarget===<br /> Toggles notarget mode on/off. While active, monsters will not target you unless you hurt them first. In &quot;modern FPS&quot;, monsters &quot;can't find you&quot; when in notarget mode. This is not the case with ZDoom.<br /> <br /> ===powerup===<br /> Powers you up in Heretic as if you had used a Tome of Power.<br /> <br /> ===sv_fastweapons (0-2)===<br /> Increases speed of weapons in Doom, Heretic, and Hexen. Setting to 2 makes weapons even faster.<br /> <br /> ===turbo===<br /> float: 100&lt;br&gt;<br /> This cvar affects how quickly the player moves. A value of 100 will cause the player to move at normal speed, 200 will cause the player to move at 200% of normal speed, 50 will cause the player to move at 50% of normal speed, etc. Valid values range from 10 to 256.<br /> <br /> ==Display==<br /> <br /> ===bumpgamma===<br /> Increases the current gamma level by 0.1. If the new gamma level would be greater than 3.0, it wraps the gamma around to 1.0 <br /> <br /> ===cl_bbannounce===<br /> boolean: false&lt;br&gt;<br /> When true, enables the Bloodbath announcer for deathmatch games. The Bloodbath announcer is &quot;The Voice&quot; from Monolith Software's Blood game. To hear the announcer, you need to load Blood's sounds.rff either at the command line or through one of zdoom.ini's [*.Autoload] sections. You can get this file either from the demo or full version of Blood. If you don't have sounds.rff, you can still see the announcer's messages even though you won't hear anything. <br /> <br /> ===cl_showmultikills===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player makes several kills in a short period of time.<br /> <br /> ===cl_showsprees===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player is on a killing spree.<br /> <br /> ===cl_spreaddecals===<br /> boolean: true&lt;br&gt;<br /> ZDoom clips decals to sidedefs. In order to hide this, the game will create as many duplicate decals on adjoining sidedefs as needed to make it appear that there is only one unbroken decal on the wall. Set this cvar to false if you don't want this.<br /> <br /> ===con_centernotify===<br /> boolean: false for Doom, true for Heretic and Hexen&lt;br&gt;<br /> When true, notify messages at the top of the screen are centered. Otherwise, they are justified against the left margin.<br /> <br /> ===con_midtime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that messages in the middle of the screen will be displayed before they dispapper. <br /> <br /> ===con_notifytime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that new messages will stay at the top of the screen before they start scrolling away. <br /> <br /> ===con_scaletext===<br /> boolean: false&lt;br&gt;<br /> If this cvar is true, then message text will be scaled to larger sizes depending on the screen resolution so that it will stay approximately the same size it would be on a 320x200 screen. <br /> <br /> ===crosshair===<br /> integer: 0&lt;br&gt;<br /> If this cvar is non-zero, it draws a crosshair. If this cvar is negative, the crosshair is translucent, otherwise it is opaque. The specific crosshair drawn depends on the value of this cvar. <br /> <br /> ===crosshaircolor===<br /> color: &quot;ff 00 00&quot;&lt;br&gt;<br /> This is the crosshair's color if crosshairhealth is false.<br /> <br /> ===crosshairgrow===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to temporarily enlarge each time you pick up an item.<br /> <br /> ===crosshairhealth===<br /> boolean: true&lt;br&gt;<br /> When true, the crosshair's color reflects your current health. Green is healthy, red is near death, and intermediate colors are somewhere in between. Set this to false, if you want the crosshair to have a constant color (specified by the crosshaircolor cvar) instead.<br /> <br /> ===crosshairscale===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to always appear the same size at all resolutions. Leaving it at false causes the crosshair to be drawn normally.<br /> <br /> ===gamma===<br /> float: 1.0&lt;br&gt;<br /> Controls the amount of gamma correction applied to the display. 1.0 is equivalent to no correction, while larger numbers translate into a brighter display, and smaller numbers translate into a darker display. 0.0 is invalid and will be rejected. Negative numbers are technically invalid but will be accepted solely for the novelty value doing so provides. <br /> <br /> ===hud_scale===<br /> boolean: false&lt;br&gt;<br /> Controls scaling of the fullscreen hud. At resolutions of 640x400 or above, setting this cvar to true will cause the icons to be scaled to approximately the same size they would be at 320x200. If this cvar is false, the icons will always be drawn without any scaling. <br /> <br /> ===msg===<br /> integer: 0&lt;br&gt;<br /> This is the minimum message level that you will see. You will not see any messages with a lower priority than this. The different message levels are: <br /> <br /> #Item pickup <br /> #Obituaries <br /> #Critical messages <br /> #Chat messages <br /> #Chat messages from a teammate <br /> <br /> ===msg0color===<br /> integer: 6&lt;br&gt;<br /> This cvar controls the color used to display level 0 (item pickup) messages. Available colors are: <br /> <br /> #Brick <br /> #Tan <br /> #Gray <br /> #Green <br /> #Brown <br /> #Gold <br /> #Red <br /> #Blue <br /> #Orange <br /> #White <br /> #Yellow <br /> <br /> ===msg1color===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display level 1 (obituary) messages. Available colors are the same as for&quot; msg0color. <br /> <br /> ===msg2color===<br /> integer: 2&lt;br&gt;<br /> This cvar selects the color used to display level 2 (critical) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg3color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 3 (chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg4color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 4 (team chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor2===<br /> integer: 4&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen that are sent to everyone. Available colors are the same as for msg0color. <br /> <br /> ===st_scale===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, the status bar will be scaled so that it covers the entire width of the screen in higher resolutions. At low resolutions this may look ugly, but at high resolutions it should look good enough.<br /> <br /> ==Renderer==<br /> <br /> ===r_columnmethod===<br /> integer: 1&lt;br&gt;<br /> Selects which of two algorithms to use to draw sprites and masked textures. Method 0 is the original algorithm used by DOOM. Method 1 is a new algorithm optimized for Pentium IIs and can perform significantly better with that or comparable processors. Ironically, method 0 is slightly faster than method 1 on Pentium III and Athlon processors (though not significantly so). <br /> <br /> ===r_detail===<br /> integer: 0&lt;br&gt;<br /> This cvar selects the detail level of the view window. Valid values are: <br /> <br /> #Normal detail level. Equivalent to Doom's high detail mode. <br /> #Double pixels horizontally. Equivalent to Doom's low detail mode. <br /> #Double pixels vertically. <br /> #Double pixels horizontally and vertically. <br /> <br /> Because of the way the renderer works, doubling pixels horizontally offers more of a speed-up than doubling them vertically does. Unless you have a very slow computer, there should be no reason to use any detail level other than 0. <br /> <br /> ===r_drawflat===<br /> boolean: false&lt;br&gt;<br /> When set to 0, segs will be drawn as solid colors instead of textures. This is useful if you want to see how a node builder split a level's linedefs. Otherwise, it just looks ugly. <br /> <br /> ===r_drawfuzzbr===<br /> boolean: true&lt;br&gt;<br /> When set to false, the &quot;fuzz&quot; effect on spectres and partially invisible players will be replaced with translucency. <br /> <br /> ===r_drawmirrors===<br /> boolean: true&lt;br&gt;<br /> Setting this false will disable the display of mirrors.<br /> <br /> ===r_drawplayersprites===<br /> boolean: true&lt;br&gt;<br /> When false, the game will not draw the player's weapon or muzzle flash, which can be nice for screenshots. <br /> <br /> ===r_drawtrans===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will disable all translucency effects in the game.<br /> <br /> ===r_fogboundary===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will disable the display of fog boundaries. Fog boundaries are sections where two areas with different fog colors meet. If the boundary is not drawn, then it will look like there is no fog at all in front of the boundary. Some old levels may look bad with fog boundary drawing enabled, which is why this cvar is available.<br /> <br /> ===r_particles===<br /> boolean: true&lt;br&gt;<br /> If set to true, particles are drawn. Otherwise, they aren't. <br /> <br /> ===r_stretchsky===<br /> boolean: true&lt;br&gt;<br /> Controls whether or not short sky textures are stretched so that you don't see them wrap when you look up. <br /> <br /> ===r_viewsize===<br /> string&lt;br&gt;<br /> This cvar contains the width and height of the current view window. This cvar is read only. <br /> <br /> ===r_visibility [visibility]===<br /> Without any parameters, displays the current visibility. With a parameter, the visibility is set. Standard visibility for the Doom engine is 8. Visibility determines how quickly light drops off with distance from the viewer. At 0 visibility, there is no change in lighting with depth.<br /> <br /> ==Video==<br /> <br /> ===fullscreen===<br /> boolean: true&lt;br&gt;<br /> If this cvar is true, the game will be displayed fullscreen. Otherwise, it will be drawn in a window. Some video cards may require that you have fullscreen false in order to run ZDoom. <br /> <br /> ===vid_attachedsurfaces (Win32 only)===<br /> boolean: false&lt;br&gt;<br /> Controls how the game allocates video memory. False is the standard setting and will always produce a useable display. If you find that there are patches of pure black and pure white on the screen (especially noticeable when a demon is right in your face), try setting this to true. Certain old Windows 95 video drivers are said to need this fix, and it is also necessary under NT 4. Unfortunately, many new video drivers (including those under NT 4) will produce a scrambled display if the screen width is not 512 or 1024 pixels and this is set to true.<br /> <br /> ===vid_currentmode===<br /> Displays the resolution of the current video mode.<br /> <br /> ===vid_defbits===<br /> integer: 8&lt;br&gt;<br /> Ignored. This cvar is meant to specify the default screen depth, but the setting is currently ignored because only 256-color displays are supported.<br /> <br /> ===vid_defheight===<br /> integer: 200&lt;br&gt;<br /> Specifies the default screen height to use if not overridden at the command line by the -height switch.<br /> <br /> ===vid_defwidth===<br /> integer: 320&lt;br&gt;<br /> Specifies the default screen width to use if not overridden at the command line with the -width switch.<br /> <br /> ===vid_listmodes===<br /> Lists all resolutions supported by the current display driver.<br /> <br /> ===vid_fps===<br /> boolean: false&lt;br&gt;<br /> When true, displays the average framerate over the past second in the lower-left corner of the screen. Because Doom's internal game rate and frame rate are linked, the framerate will never be (much) above 35 fps.<br /> <br /> ===vid_noblitter (Win32 only)===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will allow the use of the hardware to assist moving image data to video memory. When I initial wrote the code to use the blitter, it was faster than not using it. Now the blitter is slower, and I can't figure out why, so the default is true.<br /> <br /> ===vid_palettehack (Win32 only)===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, the game will refresh the palette every time the screen is redrawn. This can be useful with some buggy video drivers. If the display is fine without it, leave it that way because this can slightly slow things down.<br /> <br /> ===vid_setmode (width) (height) [depth]===<br /> Sets the screen mode to width x height with an optional color depth (if your video hardware supports it). Only a depth of 8 is supported. See also vid_currentmode, vid_listmodes<br /> <br /> ===vid_vsync (Win32 only)===<br /> boolean: true&lt;br&gt;<br /> Set this to false to disable vsync. Not all video cards support disabling vsync.<br /> <br /> ==Bots==<br /> <br /> ===addbot [name]===<br /> Spawns a bot. If a name is given, the corresponding bot in bots.cfg will be spawned. Otherwise, a bot will be picked at random from bots.cfg. <br /> <br /> ===bot_allowspy===<br /> boolean: false&lt;br&gt;<br /> Allows you to see through the eyes of bots during botmatch games. <br /> <br /> ===bot_observer===<br /> boolean: false&lt;br&gt;<br /> When set to 1, the player will experience minimal interaction with the world, and bots will ignore him. <br /> <br /> ===listbots===<br /> Lists the bots available in bots.cfg, and indicates which are currently playing. <br /> <br /> ===removebots===<br /> Removes any bots from the game. Bots will also be automatically removed from network games when the arbitrator quits.<br /> <br /> ==Automap==<br /> <br /> ===togglemap===<br /> Toggles the automap on/off.<br /> <br /> ===am_backcolor===<br /> color: &quot;6c 54 40&quot;&lt;br&gt;<br /> The color of the automap background. Changes to this cvar take effect the next time the automap is activated. <br /> <br /> ===am_cdwallcolor===<br /> color: &quot;4c 38 20&quot;&lt;br&gt;<br /> The color of two-sided lines that have a different ceiling height on each side. <br /> <br /> ===am_fdwallcolor===<br /> color: &quot;88 70 58&quot;&lt;br&gt;<br /> The color of two-sided lines that have a different floor height on each side. <br /> <br /> ===am_gridcolor===<br /> color: &quot;8b 5a 2b&quot;&lt;br&gt;<br /> The color of the automap grid. <br /> <br /> ===am_interlevelcolor===<br /> color: &quot;ff 00 00&quot;&lt;br&gt;<br /> The color of inter-level teleporters. These are teleporters that teleport you to a different map. <br /> <br /> ===am_intralevelcolor===<br /> color: &quot;00 00 ff&quot;&lt;br&gt;<br /> The color of intra-level teleporters. These are teleporters that teleport you to a different location on the same map. <br /> <br /> ===am_lockedcolor===<br /> color: &quot;00 00 98&quot;&lt;br&gt;<br /> The color of lines that open locked doors. <br /> <br /> ===am_notseencolor===<br /> color: &quot;6c 6c 6c&quot;&lt;br&gt;<br /> The color of lines on the automap that haven't yet been seen. Visible with a computer area map. <br /> <br /> ===am_overlay===<br /> boolean: false&lt;br&gt;<br /> Normally, the togglemap command switches the automap between fully off and fully on. Setting this cvar to &quot;1&quot; will cause togglemap to draw the automap on top of the player's view before it draws the automap fullscreen. (Bad description, I know. Just try it) <br /> <br /> ===am_ovotherwallscolor===<br /> color: &quot;00 88 44&quot;&lt;br&gt;<br /> The color of passable lines on the automap when the map is overlayed. <br /> <br /> ===am_ovtelecolor===<br /> color: &quot;ff ff 00&quot;&lt;br&gt;<br /> The color of teleporters—both inter- and intra-level—on the overlayed automap.<br /> <br /> ===am_ovthingcolor===<br /> color: &quot;e8 88 00&quot;&lt;br&gt;<br /> The color of things visible with the automap cheat when the map is overlayed. <br /> <br /> ===am_ovunseencolor===<br /> color: &quot;00 22 6e&quot;&lt;br&gt;<br /> The color of unseen lines on the automap when the map is overlayed. <br /> <br /> ===am_ovwallcolor===<br /> color: &quot;00 ff 00&quot;&lt;br&gt;<br /> The color of impassable walls when the automap is overlayed. <br /> <br /> ===am_ovyourcolor===<br /> color: &quot;fc e8 d8&quot;&lt;br&gt;<br /> The color of the arrow representing the player in single player games when the map is overlayed. <br /> <br /> ===am_rotate===<br /> boolean: false&lt;br&gt;<br /> Normally, the automap is always drawn such that north is at the top of the screen. Setting this cvar to &quot;1&quot; causes the automap to be drawn so that lines toward the top of the screen are always directly in front of the player's view. This can be particularly useful when the automap is overlayed. <br /> <br /> ===am_showitems===<br /> boolean: false&lt;br&gt;<br /> When true, the fullscreen automap will display a count of all the &quot;special&quot; items you have found on the map. These are the same items that are used to determine the Items stat on the intermission screen.<br /> <br /> ===am_showmonsters===<br /> boolean: true&lt;br&gt;<br /> When true, the fullscreen automap will display a count of the number of monsters that have been killed in the current level and the total number of monsters in the level. <br /> <br /> ===am_showsecrets===<br /> boolean: true&lt;br&gt;<br /> When true, the fullscreen automap will display a count of the number of secrets that have been found in the current level and the total number of secrets in the level. <br /> <br /> ===am_showtime===<br /> boolean: true&lt;br&gt;<br /> When true, the fullscreen automap will display the total amount of time you have been in a level (excluding time that has been paused). <br /> <br /> ===am_thingcolor===<br /> color: &quot;fc fc fc&quot;&lt;br&gt;<br /> The color of things revealed with the map cheat. <br /> <br /> ===am_tswallcolor===<br /> color: &quot;88 88 88&quot;&lt;br&gt;<br /> The color of two-sided lines that don't have any difference in floor or ceiling heights on either side. Only seen using map cheat. <br /> <br /> ===am_usecustomcolors===<br /> boolean: true&lt;br&gt;<br /> When true, the automap uses the colors specified by the am_* cvars, otherwise it uses the standard DOOM automap colors. <br /> <br /> am_wallcolor&lt;br&gt;<br /> color: &quot;2c 18 08&quot;&lt;br&gt;<br /> The color of one-sided and secret walls in the automap. <br /> <br /> ===am_xhaircolor===<br /> color: &quot;80 80 80&quot;&lt;br&gt;<br /> The color of the &quot;crosshair&quot; dot in the center of the automap. <br /> <br /> ===am_yourcolor===<br /> color: &quot;fc e8 d8&quot;&lt;br&gt;<br /> The color of the arrow representing the player in single player games.<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=512 2004-01-06T11:23:15Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, etc...<br /> <br /> You access the console by pressing &quot;~&quot; at any time. (This depends on your keyboard layout, for German keyboard, it is &quot;^&quot;, but to summarize it, it is the key above TAB.)<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. (EDIT: That's just a string, i.e. testcolor &quot;ff 00 00&quot;)<br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key?ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> <br /> ===addkeysection (menu-heading) (ini-section-name)&lt;br&gt;===<br /> This command does two things. First, it adds a new heading called menu-heading to the controls menu. You can use the addmenukey command to add your own custom keys beneath this heading. Second, it loads all the bindings from the corresponding ini-section-name section in zdoom.ini. You can use this command multiple times to create different sections in the menu and ini for different sets of commands. If you use a menu-heading that was already added to the menu, new controls added with addmenukey will appear at the end of that section, but the bindings will not be reloaded from the ini. <br /> <br /> ===addmenukey (description) (command)&lt;br&gt;===<br /> Adds a new control to the controls menu. Description is the name of this control in the menu, and command is a console command or alias to be executed when the control is pressed. New controls are added to the last section specified with addkeysection.<br /> <br /> ===addslot (slot) (weapon)===<br /> Adds a single weapon to the list of weapons in a weapon slot.<br /> <br /> ===alias (new-command) [command-string]===<br /> If specified with no parameters, will display a list of all current aliases. If only new-command is specified, it will be removed from the list of aliases. If command-string is also specified, it will be added to the list of aliases as new-command. For example, to create a new command to kill the monsters on the level, you can use the command: <br /> alias massacre &quot;kill monsters&quot;<br /> Then you can use the newly created massacre command to kill all the monsters on the level.<br /> <br /> ===archivecvar (cvar)===<br /> When you create a custom cvar with the set command, it will not normally be saved in the ini. You can use archivecvar after creating the cvar to indicate that the custom cvar's value should persist even after you quit.<br /> <br /> ===atexit [command]===<br /> If you specify a command, it will be added to a list of console commands to execute when the user quits the game. Commands are executed in the reverse order that they were added in. If you do not specify any arguments to atexit, then it will list the current set of commands that will execute when you quit.<br /> <br /> ===bind (key [command string])===<br /> If no parameters are specified, the entire list of bound keys will be printed to the console. If only [key] is specified, the binding for that specific key will be printed. If both [key] and [command string] are specified, [command string] will be bound to [key]. <br /> <br /> ===binddefaults===<br /> Binds all keys to their default commands. This will not unbind any keys that do not have any default bindings, so if you want to properly restore the default controls, you need to use unbindall first. <br /> defaultbind key command<br /> Binds command to the key if and only if key is not already bound and there are no keys already bound to command.<br /> <br /> ===doublebind (key [command string])===<br /> This command works just like bind, except it controls the action that occurs when a key is double-clicked. If a key does not have a doublebinding, then double-clicking it has the same result as pressing it twice. Otherwise, the first press will execute the normal command set with bind, and the second press of the double-click will execute the command set with doublebind. <br /> <br /> ===eval expression [variable]===<br /> Evaluates a mathematical expression and either prints it to the console or stores it in variable. Expressions are written using prefix notation instead of the more common infix notation. Basically, you first specify what you want to do (the operator) and then what you want to do it to (the operands). You must separate operators and operands with spaces. <br /> <br /> Examples: <br /> To compute 2+2: <br /> eval + 2 2To compute 5-3: <br /> eval - 5 3To compute 2+(5*6): <br /> eval + 2 * 5 6To decrease the number of screenblocks: <br /> eval - $screenblocks 1 screenblocksThe supported operators are:<br /> + a b Adds a and b. <br /> - a b Subtracts b from a. <br /> * a b Multiplies a and b. <br /> / a b Divides a by b. <br /> % a b Calculates the remainder of a/b. <br /> ^ a b Raises a to the b-th power . <br /> &lt; a b Produces 1 if a is less than b and 0 if not. <br /> &lt;= a b Produces 1 if a is less than or equal to b and 0 if not. <br /> &gt; a b Produces 1 if a is greater than b and 0 if not. <br /> &gt;= a b Produces 1 if a is greater than or equal to b and 0 if not. <br /> = a b Produces 1 if a is equal to b and 0 if not.<br /> <br /> == a b Produces 1 if a is equal to b and 0 if not. <br /> != a b Produces 1 if a is not equal to b and 0 if it is. <br /> &lt;&gt; a b Produces 1 if a is not equal to b and 0 if is. <br /> xor a b Calculates the bit-wise exclusive-or of a and b. <br /> &amp; a b Calculates the bit-wise and of a and b. <br /> | a b Calculates the bit-wise or of a and b. <br /> &amp;&amp; a b Calculates the logical and of a and b. <br /> || a b Calculates the logical or of a and b. <br /> <br /> ===exec (script-file)===<br /> Executes a series of commands stored in the script-file as if they had been typed in at the console directly. <br /> <br /> ===key value1 [value2]===<br /> Translates all parameters to the command into their corresponding key values which are used internally for command and alias lookup. Probably not very useful for the average user. <br /> <br /> ===puke (script [arguments])===<br /> Executes an ACS script on the current map, optionally passing it up to three numerical arguments. <br /> <br /> ===pullin (wadfile)===<br /> Loads a wadfile at startup. This command is only valid inside .cfg files that have been execed at startup.<br /> <br /> ===set (cvar) (value)===<br /> Sets cvar to value. If cvar does not exist, it will be created. <br /> <br /> ===rebind (binding)===<br /> Changes the binding for the key that caused the rebind command to execute. For obvious reasons, this command cannot be used at the console.<br /> <br /> Example: <br /> <br /> bind b &quot;echo setting 1; rebind \&quot;echo setting 2\&quot;&quot;<br /> <br /> This will cause the first press of b to echo &quot;setting 1&quot; to the console. All future presses of b will echo &quot;setting 2&quot; instead. <br /> <br /> ===unbind (key)===<br /> Removes a binding from the specified key.<br /> <br /> ===unbindall===<br /> Removes all bindings and doublebindings from every key. To restore the default bindings, you can use the binddefaults command. There is no way to restore any custom bindings after issuing this command except by retyping each bind command or using the controls setup menu.<br /> <br /> ===undoublebind (key)===<br /> Removes a doublebinding from the specified key.<br /> <br /> ===unset (cvar)===<br /> Undefines a user-created cvar.<br /> <br /> ==Screenshots==<br /> <br /> ===png_gamma===<br /> float: 0&lt;br&gt;<br /> Controls the gamma level stored in PNG screenshots. If this is 0, then your current gamma setting will be used.<br /> <br /> ===png_level===<br /> integer: 5&lt;br&gt;<br /> This is the level of compression to use for PNG screenshots. 0 is no compression at all, 1 is minimal compression (fastest), 9 is maximum compression (slowest), and intermediate values offer intermediate compression. 5 is offers a decent trade-of between file size and compression time. An uncompressed image will not neccessarily save faster than a compressed image, because the extra time needed to write out a complete uncompressed image may be longer than the time required to compress the image. If you need to create screenshots as quickly as possible, consider setting screenshot_type to &quot;pcx&quot;. <br /> <br /> ===screenshot [file]===<br /> Dumps a copy of the screen to disk as a PNG or PCX file. If file is not specified, the screenshot will be saved to the directory the game was run from with a name of the form doom????.png. <br /> <br /> ===screenshot_quiet===<br /> boolean: false&lt;br&gt;<br /> Setting this to true will suppress the messages informing you what file a screenshot was saved to.<br /> <br /> ===screenshot_type===<br /> string: &quot;png&quot;&lt;br&gt;<br /> Determines the type of screenshots that will be saved. This can be either &quot;png&quot; or &quot;pcx&quot;. In my empirical studies, PNG screenshots are about half the size of pcx screenshots. PCX screenshots have the advantage that they require less time to create so are most useful for rapid screenshot generation. The following sequence of console commands will take a screenshot every frame. You can use an external program to assemble these into a video, if desired. <br /> <br /> screenshot_type &quot;png&quot;&lt;br&gt;<br /> screenshot_quiet true&lt;br&gt;<br /> alias autoshot &quot;screenshot; wait 1; autoshot&quot;&lt;br&gt;<br /> autoshot&lt;br&gt;<br /> <br /> If you use the autoshot alias, the command alias autoshot will stop automatic screenshot taking before you hit 10000 screenshots (approximately 4 minutes, 45 seconds).<br /> <br /> ===storesavepic===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will produce smaller savegames (by about 14k typically) by not storing a screenshot inside the savegame.<br /> <br /> ==Chatting==<br /> <br /> ===chat_substitution===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want to chat using special keywords that will be replaced with appropriate text when your messages are sent. The supported keywords are:<br /> <br /> $health &lt;br&gt;<br /> Replaced by your current health. &lt;br&gt;<br /> $weapon &lt;br&gt;<br /> Replaced by the name of your current weapon. &lt;br&gt;<br /> $armor &lt;br&gt;<br /> Replaced by your current armor count. &lt;br&gt;<br /> $ammocount &lt;br&gt;<br /> Replaced by your current ammo count. &lt;br&gt;<br /> $ammo &lt;br&gt;<br /> Replaced by the name of your current ammo.<br /> <br /> As an example, if you just started a new game of Doom and have chat substitution turned on, when you send the message &quot;My health is $health, and I am using a $weapon&quot;, the message that is actually sent will be &quot;My health is 100, and I am using a Pistol&quot;.<br /> <br /> chatmacro0&lt;br&gt;<br /> chatmacro1&lt;br&gt;<br /> chatmacro2&lt;br&gt;<br /> chatmacro3&lt;br&gt;<br /> chatmacro4&lt;br&gt;<br /> chatmacro5&lt;br&gt;<br /> chatmacro6&lt;br&gt;<br /> chatmacro7&lt;br&gt;<br /> chatmacro8&lt;br&gt;<br /> chatmacro9&lt;br&gt;<br /> string&lt;br&gt;<br /> These are all strings that can be assigned to hotkeys in chat mode. To use these, enter chat mode and then hold down Alt and press one of the number keys. The string stored in the corresponding chatmacro cvar will be sent as if you had typed it yourself. <br /> <br /> ===messagemode===<br /> Enters message entry mode. Anything typed while in this mode will be sent to everyone else as if you had used the say command once you press enter. <br /> <br /> ===messagemode2===<br /> This is just like messagemode except that the message is only sent to other members of your team. If teamplay is false or you don't have a team, then this command will work just like messagemode and send the message to everyone. <br /> <br /> ===say (message)===<br /> Sends a message to everyone playing. If your message begins with &quot;/me&quot; then &quot;/me&quot; will be replaced by your name ala IRC. <br /> <br /> ===say_team (message)===<br /> This is just like say except it only sends a message to your teammates. If teamplay is inactive, then this command will act exactly like say and send the message to everyone.<br /> <br /> ==Cheating==<br /> <br /> ===sv_cheats===<br /> boolean: false<br /> When true, cheats will be allowed in Nightmare difficulty and network games. For purposes of fairness, this cvar can only be set from the command line when you run ZDoom. This is to avoid situations where the key player in a multiplayer game (player 1) could go to the console and type something like this:<br /> <br /> sv_cheats 1<br /> god<br /> sv_cheats 0<br /> <br /> whereby rendering himself immune to the attacks of others.<br /> <br /> ===anubis===<br /> Toggles monster fear on and off. Scared monsters will run away from you and attack less frequently.<br /> <br /> ===fly===<br /> Toggles fly mode on and off.<br /> <br /> ===give (item)===<br /> Gives an item to the player. Give understands the following special items: <br /> all - gives you everything <br /> health - gives you full health <br /> weapons - gives you every weapon <br /> ammo - gives you full ammo <br /> armor - gives you full armor <br /> keys - gives you every key <br /> It also understands the names of individual inventory items. Use the command dumpclasses inventory for a complete list of these. <br /> <br /> ===god===<br /> Toggles God (Degreelessness) mode on/off. While active, you cannot be hurt by normal attacks (although telefragging will still kill you). Also known as iddqd. <br /> <br /> ===iddqd===<br /> The same as god, except it also gives you 100 health.<br /> <br /> ===kill [monsters]===<br /> If used as &quot;kill monsters&quot;, will kill all monsters on the level. Otherwise, it will kill you instead. This command is broken in netgames, so don't use it unless you are playing a single player game. <br /> <br /> ===logfile [log-file]===<br /> If log-file is not specified, console logging will be stopped (if active). Otherwise, a file named log-file will be created on disk, and all console output will be recorded in it as well as on the screen. <br /> <br /> ===mdk===<br /> This cheat will kill whatever you are looking at.<br /> <br /> ===morphme===<br /> Transforms you into a chicken in Heretic and a pig in Hexen and Doom (The latter only happens if you have the releven graphics present).<br /> <br /> ===noclip===<br /> Toggles noclipping mode on/off. <br /> <br /> ===notarget===<br /> Toggles notarget mode on/off. While active, monsters will not target you unless you hurt them first. In &quot;modern FPS&quot;, monsters &quot;can't find you&quot; when in notarget mode. This is not the case with ZDoom.<br /> <br /> ===powerup===<br /> Powers you up in Heretic as if you had used a Tome of Power.<br /> <br /> ===sv_fastweapons (0-2)===<br /> Increases speed of weapons in Doom, Heretic, and Hexen. Setting to 2 makes weapons even faster.<br /> <br /> ===turbo===<br /> float: 100&lt;br&gt;<br /> This cvar affects how quickly the player moves. A value of 100 will cause the player to move at normal speed, 200 will cause the player to move at 200% of normal speed, 50 will cause the player to move at 50% of normal speed, etc. Valid values range from 10 to 256.<br /> <br /> ==Display==<br /> <br /> ===bumpgamma===<br /> Increases the current gamma level by 0.1. If the new gamma level would be greater than 3.0, it wraps the gamma around to 1.0 <br /> <br /> ===cl_bbannounce===<br /> boolean: false&lt;br&gt;<br /> When true, enables the Bloodbath announcer for deathmatch games. The Bloodbath announcer is &quot;The Voice&quot; from Monolith Software's Blood game. To hear the announcer, you need to load Blood's sounds.rff either at the command line or through one of zdoom.ini's [*.Autoload] sections. You can get this file either from the demo or full version of Blood. If you don't have sounds.rff, you can still see the announcer's messages even though you won't hear anything. <br /> <br /> ===cl_showmultikills===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player makes several kills in a short period of time.<br /> <br /> ===cl_showsprees===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player is on a killing spree.<br /> <br /> ===cl_spreaddecals===<br /> boolean: true&lt;br&gt;<br /> ZDoom clips decals to sidedefs. In order to hide this, the game will create as many duplicate decals on adjoining sidedefs as needed to make it appear that there is only one unbroken decal on the wall. Set this cvar to false if you don't want this.<br /> <br /> ===con_centernotify===<br /> boolean: false for Doom, true for Heretic and Hexen&lt;br&gt;<br /> When true, notify messages at the top of the screen are centered. Otherwise, they are justified against the left margin.<br /> <br /> ===con_midtime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that messages in the middle of the screen will be displayed before they dispapper. <br /> <br /> ===con_notifytime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that new messages will stay at the top of the screen before they start scrolling away. <br /> <br /> ===con_scaletext===<br /> boolean: false&lt;br&gt;<br /> If this cvar is true, then message text will be scaled to larger sizes depending on the screen resolution so that it will stay approximately the same size it would be on a 320x200 screen. <br /> <br /> ===crosshair===<br /> integer: 0&lt;br&gt;<br /> If this cvar is non-zero, it draws a crosshair. If this cvar is negative, the crosshair is translucent, otherwise it is opaque. The specific crosshair drawn depends on the value of this cvar. <br /> <br /> ===crosshaircolor===<br /> color: &quot;ff 00 00&quot;&lt;br&gt;<br /> This is the crosshair's color if crosshairhealth is false.<br /> <br /> ===crosshairgrow===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to temporarily enlarge each time you pick up an item.<br /> <br /> ===crosshairhealth===<br /> boolean: true&lt;br&gt;<br /> When true, the crosshair's color reflects your current health. Green is healthy, red is near death, and intermediate colors are somewhere in between. Set this to false, if you want the crosshair to have a constant color (specified by the crosshaircolor cvar) instead.<br /> <br /> ===crosshairscale===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to always appear the same size at all resolutions. Leaving it at false causes the crosshair to be drawn normally.<br /> <br /> ===gamma===<br /> float: 1.0&lt;br&gt;<br /> Controls the amount of gamma correction applied to the display. 1.0 is equivalent to no correction, while larger numbers translate into a brighter display, and smaller numbers translate into a darker display. 0.0 is invalid and will be rejected. Negative numbers are technically invalid but will be accepted solely for the novelty value doing so provides. <br /> <br /> ===hud_scale===<br /> boolean: false&lt;br&gt;<br /> Controls scaling of the fullscreen hud. At resolutions of 640x400 or above, setting this cvar to true will cause the icons to be scaled to approximately the same size they would be at 320x200. If this cvar is false, the icons will always be drawn without any scaling. <br /> <br /> ===msg===<br /> integer: 0&lt;br&gt;<br /> This is the minimum message level that you will see. You will not see any messages with a lower priority than this. The different message levels are: <br /> <br /> #Item pickup <br /> #Obituaries <br /> #Critical messages <br /> #Chat messages <br /> #Chat messages from a teammate <br /> <br /> ===msg0color===<br /> integer: 6&lt;br&gt;<br /> This cvar controls the color used to display level 0 (item pickup) messages. Available colors are: <br /> <br /> #Brick <br /> #Tan <br /> #Gray <br /> #Green <br /> #Brown <br /> #Gold <br /> #Red <br /> #Blue <br /> #Orange <br /> #White <br /> #Yellow <br /> <br /> ===msg1color===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display level 1 (obituary) messages. Available colors are the same as for&quot; msg0color. <br /> <br /> ===msg2color===<br /> integer: 2&lt;br&gt;<br /> This cvar selects the color used to display level 2 (critical) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg3color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 3 (chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg4color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 4 (team chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor2===<br /> integer: 4&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen that are sent to everyone. Available colors are the same as for msg0color. <br /> <br /> ===st_scale===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, the status bar will be scaled so that it covers the entire width of the screen in higher resolutions. At low resolutions this may look ugly, but at high resolutions it should look good enough.<br /> <br /> ==Renderer==<br /> <br /> ===r_columnmethod===<br /> integer: 1&lt;br&gt;<br /> Selects which of two algorithms to use to draw sprites and masked textures. Method 0 is the original algorithm used by DOOM. Method 1 is a new algorithm optimized for Pentium IIs and can perform significantly better with that or comparable processors. Ironically, method 0 is slightly faster than method 1 on Pentium III and Athlon processors (though not significantly so). <br /> <br /> ===r_detail===<br /> integer: 0&lt;br&gt;<br /> This cvar selects the detail level of the view window. Valid values are: <br /> <br /> #Normal detail level. Equivalent to Doom's high detail mode. <br /> #Double pixels horizontally. Equivalent to Doom's low detail mode. <br /> #Double pixels vertically. <br /> #Double pixels horizontally and vertically. <br /> <br /> Because of the way the renderer works, doubling pixels horizontally offers more of a speed-up than doubling them vertically does. Unless you have a very slow computer, there should be no reason to use any detail level other than 0. <br /> <br /> ===r_drawflat===<br /> boolean: false&lt;br&gt;<br /> When set to 0, segs will be drawn as solid colors instead of textures. This is useful if you want to see how a node builder split a level's linedefs. Otherwise, it just looks ugly. <br /> <br /> ===r_drawfuzzbr===<br /> boolean: true&lt;br&gt;<br /> When set to false, the &quot;fuzz&quot; effect on spectres and partially invisible players will be replaced with translucency. <br /> <br /> ===r_drawmirrors===<br /> boolean: true&lt;br&gt;<br /> Setting this false will disable the display of mirrors.<br /> <br /> ===r_drawplayersprites===<br /> boolean: true&lt;br&gt;<br /> When false, the game will not draw the player's weapon or muzzle flash, which can be nice for screenshots. <br /> <br /> ===r_drawtrans===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will disable all translucency effects in the game.<br /> <br /> ===r_fogboundary===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will disable the display of fog boundaries. Fog boundaries are sections where two areas with different fog colors meet. If the boundary is not drawn, then it will look like there is no fog at all in front of the boundary. Some old levels may look bad with fog boundary drawing enabled, which is why this cvar is available.<br /> <br /> ===r_particles===<br /> boolean: true&lt;br&gt;<br /> If set to true, particles are drawn. Otherwise, they aren't. <br /> <br /> ===r_stretchsky===<br /> boolean: true&lt;br&gt;<br /> Controls whether or not short sky textures are stretched so that you don't see them wrap when you look up. <br /> <br /> ===r_viewsize===<br /> string&lt;br&gt;<br /> This cvar contains the width and height of the current view window. This cvar is read only. <br /> <br /> ===r_visibility [visibility]===<br /> Without any parameters, displays the current visibility. With a parameter, the visibility is set. Standard visibility for the Doom engine is 8. Visibility determines how quickly light drops off with distance from the viewer. At 0 visibility, there is no change in lighting with depth.<br /> <br /> ==Video==<br /> <br /> ===fullscreen===<br /> boolean: true&lt;br&gt;<br /> If this cvar is true, the game will be displayed fullscreen. Otherwise, it will be drawn in a window. Some video cards may require that you have fullscreen false in order to run ZDoom. <br /> <br /> ===vid_attachedsurfaces (Win32 only)===<br /> boolean: false&lt;br&gt;<br /> Controls how the game allocates video memory. False is the standard setting and will always produce a useable display. If you find that there are patches of pure black and pure white on the screen (especially noticeable when a demon is right in your face), try setting this to true. Certain old Windows 95 video drivers are said to need this fix, and it is also necessary under NT 4. Unfortunately, many new video drivers (including those under NT 4) will produce a scrambled display if the screen width is not 512 or 1024 pixels and this is set to true.<br /> <br /> ===vid_currentmode===<br /> Displays the resolution of the current video mode.<br /> <br /> ===vid_defbits===<br /> integer: 8&lt;br&gt;<br /> Ignored. This cvar is meant to specify the default screen depth, but the setting is currently ignored because only 256-color displays are supported.<br /> <br /> ===vid_defheight===<br /> integer: 200&lt;br&gt;<br /> Specifies the default screen height to use if not overridden at the command line by the -height switch.<br /> <br /> ===vid_defwidth===<br /> integer: 320&lt;br&gt;<br /> Specifies the default screen width to use if not overridden at the command line with the -width switch.<br /> <br /> ===vid_listmodes===<br /> Lists all resolutions supported by the current display driver.<br /> <br /> ===vid_fps===<br /> boolean: false&lt;br&gt;<br /> When true, displays the average framerate over the past second in the lower-left corner of the screen. Because Doom's internal game rate and frame rate are linked, the framerate will never be (much) above 35 fps.<br /> <br /> ===vid_noblitter (Win32 only)===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will allow the use of the hardware to assist moving image data to video memory. When I initial wrote the code to use the blitter, it was faster than not using it. Now the blitter is slower, and I can't figure out why, so the default is true.<br /> <br /> ===vid_palettehack (Win32 only)===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, the game will refresh the palette every time the screen is redrawn. This can be useful with some buggy video drivers. If the display is fine without it, leave it that way because this can slightly slow things down.<br /> <br /> ===vid_setmode (width) (height) [depth]===<br /> Sets the screen mode to width x height with an optional color depth (if your video hardware supports it). Only a depth of 8 is supported. See also vid_currentmode, vid_listmodes<br /> <br /> ===vid_vsync (Win32 only)===<br /> boolean: true&lt;br&gt;<br /> Set this to false to disable vsync. Not all video cards support disabling vsync.<br /> <br /> ==Bots==<br /> <br /> ===addbot [name]===<br /> Spawns a bot. If a name is given, the corresponding bot in bots.cfg will be spawned. Otherwise, a bot will be picked at random from bots.cfg. <br /> <br /> ===bot_allowspy===<br /> boolean: false&lt;br&gt;<br /> Allows you to see through the eyes of bots during botmatch games. <br /> <br /> ===bot_observer===<br /> boolean: false&lt;br&gt;<br /> When set to 1, the player will experience minimal interaction with the world, and bots will ignore him. <br /> <br /> ===listbots===<br /> Lists the bots available in bots.cfg, and indicates which are currently playing. <br /> <br /> ===removebots===<br /> Removes any bots from the game. Bots will also be automatically removed from network games when the arbitrator quits.<br /> <br /> ==Automap==<br /> * [[AutoMap]]<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=511 2004-01-06T11:22:31Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, etc...<br /> <br /> You access the console by pressing &quot;~&quot; at any time. (This depends on your keyboard layout, for German keyboard, it is &quot;^&quot;, but to summarize it, it is the key above TAB.)<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. (EDIT: That's just a string, i.e. testcolor &quot;ff 00 00&quot;)<br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key?ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> <br /> ===addkeysection (menu-heading) (ini-section-name)&lt;br&gt;===<br /> This command does two things. First, it adds a new heading called menu-heading to the controls menu. You can use the addmenukey command to add your own custom keys beneath this heading. Second, it loads all the bindings from the corresponding ini-section-name section in zdoom.ini. You can use this command multiple times to create different sections in the menu and ini for different sets of commands. If you use a menu-heading that was already added to the menu, new controls added with addmenukey will appear at the end of that section, but the bindings will not be reloaded from the ini. <br /> <br /> ===addmenukey (description) (command)&lt;br&gt;===<br /> Adds a new control to the controls menu. Description is the name of this control in the menu, and command is a console command or alias to be executed when the control is pressed. New controls are added to the last section specified with addkeysection.<br /> <br /> ===addslot (slot) (weapon)===<br /> Adds a single weapon to the list of weapons in a weapon slot.<br /> <br /> ===alias (new-command) [command-string]===<br /> If specified with no parameters, will display a list of all current aliases. If only new-command is specified, it will be removed from the list of aliases. If command-string is also specified, it will be added to the list of aliases as new-command. For example, to create a new command to kill the monsters on the level, you can use the command: <br /> alias massacre &quot;kill monsters&quot;<br /> Then you can use the newly created massacre command to kill all the monsters on the level.<br /> <br /> ===archivecvar (cvar)===<br /> When you create a custom cvar with the set command, it will not normally be saved in the ini. You can use archivecvar after creating the cvar to indicate that the custom cvar's value should persist even after you quit.<br /> <br /> ===atexit [command]===<br /> If you specify a command, it will be added to a list of console commands to execute when the user quits the game. Commands are executed in the reverse order that they were added in. If you do not specify any arguments to atexit, then it will list the current set of commands that will execute when you quit.<br /> <br /> ===bind (key [command string])===<br /> If no parameters are specified, the entire list of bound keys will be printed to the console. If only [key] is specified, the binding for that specific key will be printed. If both [key] and [command string] are specified, [command string] will be bound to [key]. <br /> <br /> ===binddefaults===<br /> Binds all keys to their default commands. This will not unbind any keys that do not have any default bindings, so if you want to properly restore the default controls, you need to use unbindall first. <br /> defaultbind key command<br /> Binds command to the key if and only if key is not already bound and there are no keys already bound to command.<br /> <br /> ===doublebind (key [command string])===<br /> This command works just like bind, except it controls the action that occurs when a key is double-clicked. If a key does not have a doublebinding, then double-clicking it has the same result as pressing it twice. Otherwise, the first press will execute the normal command set with bind, and the second press of the double-click will execute the command set with doublebind. <br /> <br /> ===eval expression [variable]===<br /> Evaluates a mathematical expression and either prints it to the console or stores it in variable. Expressions are written using prefix notation instead of the more common infix notation. Basically, you first specify what you want to do (the operator) and then what you want to do it to (the operands). You must separate operators and operands with spaces. <br /> <br /> Examples: <br /> To compute 2+2: <br /> eval + 2 2To compute 5-3: <br /> eval - 5 3To compute 2+(5*6): <br /> eval + 2 * 5 6To decrease the number of screenblocks: <br /> eval - $screenblocks 1 screenblocksThe supported operators are:<br /> + a b Adds a and b. <br /> - a b Subtracts b from a. <br /> * a b Multiplies a and b. <br /> / a b Divides a by b. <br /> % a b Calculates the remainder of a/b. <br /> ^ a b Raises a to the b-th power . <br /> &lt; a b Produces 1 if a is less than b and 0 if not. <br /> &lt;= a b Produces 1 if a is less than or equal to b and 0 if not. <br /> &gt; a b Produces 1 if a is greater than b and 0 if not. <br /> &gt;= a b Produces 1 if a is greater than or equal to b and 0 if not. <br /> = a b Produces 1 if a is equal to b and 0 if not.<br /> <br /> == a b Produces 1 if a is equal to b and 0 if not. <br /> != a b Produces 1 if a is not equal to b and 0 if it is. <br /> &lt;&gt; a b Produces 1 if a is not equal to b and 0 if is. <br /> xor a b Calculates the bit-wise exclusive-or of a and b. <br /> &amp; a b Calculates the bit-wise and of a and b. <br /> | a b Calculates the bit-wise or of a and b. <br /> &amp;&amp; a b Calculates the logical and of a and b. <br /> || a b Calculates the logical or of a and b. <br /> <br /> ===exec (script-file)===<br /> Executes a series of commands stored in the script-file as if they had been typed in at the console directly. <br /> <br /> ===key value1 [value2]===<br /> Translates all parameters to the command into their corresponding key values which are used internally for command and alias lookup. Probably not very useful for the average user. <br /> <br /> ===puke (script [arguments])===<br /> Executes an ACS script on the current map, optionally passing it up to three numerical arguments. <br /> <br /> ===pullin (wadfile)===<br /> Loads a wadfile at startup. This command is only valid inside .cfg files that have been execed at startup.<br /> <br /> ===set (cvar) (value)===<br /> Sets cvar to value. If cvar does not exist, it will be created. <br /> <br /> ===rebind (binding)===<br /> Changes the binding for the key that caused the rebind command to execute. For obvious reasons, this command cannot be used at the console.<br /> <br /> Example: <br /> <br /> bind b &quot;echo setting 1; rebind \&quot;echo setting 2\&quot;&quot;<br /> <br /> This will cause the first press of b to echo &quot;setting 1&quot; to the console. All future presses of b will echo &quot;setting 2&quot; instead. <br /> <br /> ===unbind (key)===<br /> Removes a binding from the specified key.<br /> <br /> ===unbindall===<br /> Removes all bindings and doublebindings from every key. To restore the default bindings, you can use the binddefaults command. There is no way to restore any custom bindings after issuing this command except by retyping each bind command or using the controls setup menu.<br /> <br /> ===undoublebind (key)===<br /> Removes a doublebinding from the specified key.<br /> <br /> ===unset (cvar)===<br /> Undefines a user-created cvar.<br /> <br /> ==Screenshots==<br /> <br /> ===png_gamma===<br /> float: 0&lt;br&gt;<br /> Controls the gamma level stored in PNG screenshots. If this is 0, then your current gamma setting will be used.<br /> <br /> ===png_level===<br /> integer: 5&lt;br&gt;<br /> This is the level of compression to use for PNG screenshots. 0 is no compression at all, 1 is minimal compression (fastest), 9 is maximum compression (slowest), and intermediate values offer intermediate compression. 5 is offers a decent trade-of between file size and compression time. An uncompressed image will not neccessarily save faster than a compressed image, because the extra time needed to write out a complete uncompressed image may be longer than the time required to compress the image. If you need to create screenshots as quickly as possible, consider setting screenshot_type to &quot;pcx&quot;. <br /> <br /> ===screenshot [file]===<br /> Dumps a copy of the screen to disk as a PNG or PCX file. If file is not specified, the screenshot will be saved to the directory the game was run from with a name of the form doom????.png. <br /> <br /> ===screenshot_quiet===<br /> boolean: false&lt;br&gt;<br /> Setting this to true will suppress the messages informing you what file a screenshot was saved to.<br /> <br /> ===screenshot_type===<br /> string: &quot;png&quot;&lt;br&gt;<br /> Determines the type of screenshots that will be saved. This can be either &quot;png&quot; or &quot;pcx&quot;. In my empirical studies, PNG screenshots are about half the size of pcx screenshots. PCX screenshots have the advantage that they require less time to create so are most useful for rapid screenshot generation. The following sequence of console commands will take a screenshot every frame. You can use an external program to assemble these into a video, if desired. <br /> <br /> screenshot_type &quot;png&quot;&lt;br&gt;<br /> screenshot_quiet true&lt;br&gt;<br /> alias autoshot &quot;screenshot; wait 1; autoshot&quot;&lt;br&gt;<br /> autoshot&lt;br&gt;<br /> <br /> If you use the autoshot alias, the command alias autoshot will stop automatic screenshot taking before you hit 10000 screenshots (approximately 4 minutes, 45 seconds).<br /> <br /> ===storesavepic===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will produce smaller savegames (by about 14k typically) by not storing a screenshot inside the savegame.<br /> <br /> ==Chatting==<br /> <br /> ===chat_substitution===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want to chat using special keywords that will be replaced with appropriate text when your messages are sent. The supported keywords are:<br /> <br /> $health &lt;br&gt;<br /> Replaced by your current health. &lt;br&gt;<br /> $weapon &lt;br&gt;<br /> Replaced by the name of your current weapon. &lt;br&gt;<br /> $armor &lt;br&gt;<br /> Replaced by your current armor count. &lt;br&gt;<br /> $ammocount &lt;br&gt;<br /> Replaced by your current ammo count. &lt;br&gt;<br /> $ammo &lt;br&gt;<br /> Replaced by the name of your current ammo.<br /> <br /> As an example, if you just started a new game of Doom and have chat substitution turned on, when you send the message &quot;My health is $health, and I am using a $weapon&quot;, the message that is actually sent will be &quot;My health is 100, and I am using a Pistol&quot;.<br /> <br /> chatmacro0&lt;br&gt;<br /> chatmacro1&lt;br&gt;<br /> chatmacro2&lt;br&gt;<br /> chatmacro3&lt;br&gt;<br /> chatmacro4&lt;br&gt;<br /> chatmacro5&lt;br&gt;<br /> chatmacro6&lt;br&gt;<br /> chatmacro7&lt;br&gt;<br /> chatmacro8&lt;br&gt;<br /> chatmacro9&lt;br&gt;<br /> string&lt;br&gt;<br /> These are all strings that can be assigned to hotkeys in chat mode. To use these, enter chat mode and then hold down Alt and press one of the number keys. The string stored in the corresponding chatmacro cvar will be sent as if you had typed it yourself. <br /> <br /> ===messagemode===<br /> Enters message entry mode. Anything typed while in this mode will be sent to everyone else as if you had used the say command once you press enter. <br /> <br /> ===messagemode2===<br /> This is just like messagemode except that the message is only sent to other members of your team. If teamplay is false or you don't have a team, then this command will work just like messagemode and send the message to everyone. <br /> <br /> ===say (message)===<br /> Sends a message to everyone playing. If your message begins with &quot;/me&quot; then &quot;/me&quot; will be replaced by your name ala IRC. <br /> <br /> ===say_team (message)===<br /> This is just like say except it only sends a message to your teammates. If teamplay is inactive, then this command will act exactly like say and send the message to everyone.<br /> <br /> ==Cheating==<br /> <br /> ===sv_cheats===<br /> boolean: false<br /> When true, cheats will be allowed in Nightmare difficulty and network games. For purposes of fairness, this cvar can only be set from the command line when you run ZDoom. This is to avoid situations where the key player in a multiplayer game (player 1) could go to the console and type something like this:<br /> <br /> sv_cheats 1<br /> god<br /> sv_cheats 0<br /> <br /> whereby rendering himself immune to the attacks of others.<br /> <br /> ===anubis===<br /> Toggles monster fear on and off. Scared monsters will run away from you and attack less frequently.<br /> <br /> ===fly===<br /> Toggles fly mode on and off.<br /> <br /> ===give (item)===<br /> Gives an item to the player. Give understands the following special items: <br /> all - gives you everything <br /> health - gives you full health <br /> weapons - gives you every weapon <br /> ammo - gives you full ammo <br /> armor - gives you full armor <br /> keys - gives you every key <br /> It also understands the names of individual inventory items. Use the command dumpclasses inventory for a complete list of these. <br /> <br /> ===god===<br /> Toggles God (Degreelessness) mode on/off. While active, you cannot be hurt by normal attacks (although telefragging will still kill you). Also known as iddqd. <br /> <br /> ===iddqd===<br /> The same as god, except it also gives you 100 health.<br /> <br /> ===kill [monsters]===<br /> If used as &quot;kill monsters&quot;, will kill all monsters on the level. Otherwise, it will kill you instead. This command is broken in netgames, so don't use it unless you are playing a single player game. <br /> <br /> ===logfile [log-file]===<br /> If log-file is not specified, console logging will be stopped (if active). Otherwise, a file named log-file will be created on disk, and all console output will be recorded in it as well as on the screen. <br /> <br /> ===mdk===<br /> This cheat will kill whatever you are looking at.<br /> <br /> ===morphme===<br /> Transforms you into a chicken in Heretic and a pig in Hexen and Doom (The latter only happens if you have the releven graphics present).<br /> <br /> ===noclip===<br /> Toggles noclipping mode on/off. <br /> <br /> ===notarget===<br /> Toggles notarget mode on/off. While active, monsters will not target you unless you hurt them first. In &quot;modern FPS&quot;, monsters &quot;can't find you&quot; when in notarget mode. This is not the case with ZDoom.<br /> <br /> ===powerup===<br /> Powers you up in Heretic as if you had used a Tome of Power.<br /> <br /> ===sv_fastweapons (0-2)===<br /> Increases speed of weapons in Doom, Heretic, and Hexen. Setting to 2 makes weapons even faster.<br /> <br /> ===turbo===<br /> float: 100&lt;br&gt;<br /> This cvar affects how quickly the player moves. A value of 100 will cause the player to move at normal speed, 200 will cause the player to move at 200% of normal speed, 50 will cause the player to move at 50% of normal speed, etc. Valid values range from 10 to 256.<br /> <br /> ==Display==<br /> <br /> ===bumpgamma===<br /> Increases the current gamma level by 0.1. If the new gamma level would be greater than 3.0, it wraps the gamma around to 1.0 <br /> <br /> ===cl_bbannounce===<br /> boolean: false&lt;br&gt;<br /> When true, enables the Bloodbath announcer for deathmatch games. The Bloodbath announcer is &quot;The Voice&quot; from Monolith Software's Blood game. To hear the announcer, you need to load Blood's sounds.rff either at the command line or through one of zdoom.ini's [*.Autoload] sections. You can get this file either from the demo or full version of Blood. If you don't have sounds.rff, you can still see the announcer's messages even though you won't hear anything. <br /> <br /> ===cl_showmultikills===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player makes several kills in a short period of time.<br /> <br /> ===cl_showsprees===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player is on a killing spree.<br /> <br /> ===cl_spreaddecals===<br /> boolean: true&lt;br&gt;<br /> ZDoom clips decals to sidedefs. In order to hide this, the game will create as many duplicate decals on adjoining sidedefs as needed to make it appear that there is only one unbroken decal on the wall. Set this cvar to false if you don't want this.<br /> <br /> ===con_centernotify===<br /> boolean: false for Doom, true for Heretic and Hexen&lt;br&gt;<br /> When true, notify messages at the top of the screen are centered. Otherwise, they are justified against the left margin.<br /> <br /> ===con_midtime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that messages in the middle of the screen will be displayed before they dispapper. <br /> <br /> ===con_notifytime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that new messages will stay at the top of the screen before they start scrolling away. <br /> <br /> ===con_scaletext===<br /> boolean: false&lt;br&gt;<br /> If this cvar is true, then message text will be scaled to larger sizes depending on the screen resolution so that it will stay approximately the same size it would be on a 320x200 screen. <br /> <br /> ===crosshair===<br /> integer: 0&lt;br&gt;<br /> If this cvar is non-zero, it draws a crosshair. If this cvar is negative, the crosshair is translucent, otherwise it is opaque. The specific crosshair drawn depends on the value of this cvar. <br /> <br /> ===crosshaircolor===<br /> color: &quot;ff 00 00&quot;&lt;br&gt;<br /> This is the crosshair's color if crosshairhealth is false.<br /> <br /> ===crosshairgrow===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to temporarily enlarge each time you pick up an item.<br /> <br /> ===crosshairhealth===<br /> boolean: true&lt;br&gt;<br /> When true, the crosshair's color reflects your current health. Green is healthy, red is near death, and intermediate colors are somewhere in between. Set this to false, if you want the crosshair to have a constant color (specified by the crosshaircolor cvar) instead.<br /> <br /> ===crosshairscale===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to always appear the same size at all resolutions. Leaving it at false causes the crosshair to be drawn normally.<br /> <br /> ===gamma===<br /> float: 1.0&lt;br&gt;<br /> Controls the amount of gamma correction applied to the display. 1.0 is equivalent to no correction, while larger numbers translate into a brighter display, and smaller numbers translate into a darker display. 0.0 is invalid and will be rejected. Negative numbers are technically invalid but will be accepted solely for the novelty value doing so provides. <br /> <br /> ===hud_scale===<br /> boolean: false&lt;br&gt;<br /> Controls scaling of the fullscreen hud. At resolutions of 640x400 or above, setting this cvar to true will cause the icons to be scaled to approximately the same size they would be at 320x200. If this cvar is false, the icons will always be drawn without any scaling. <br /> <br /> ===msg===<br /> integer: 0&lt;br&gt;<br /> This is the minimum message level that you will see. You will not see any messages with a lower priority than this. The different message levels are: <br /> <br /> #Item pickup <br /> #Obituaries <br /> #Critical messages <br /> #Chat messages <br /> #Chat messages from a teammate <br /> <br /> ===msg0color===<br /> integer: 6&lt;br&gt;<br /> This cvar controls the color used to display level 0 (item pickup) messages. Available colors are: <br /> <br /> #Brick <br /> #Tan <br /> #Gray <br /> #Green <br /> #Brown <br /> #Gold <br /> #Red <br /> #Blue <br /> #Orange <br /> #White <br /> #Yellow <br /> <br /> ===msg1color===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display level 1 (obituary) messages. Available colors are the same as for&quot; msg0color. <br /> <br /> ===msg2color===<br /> integer: 2&lt;br&gt;<br /> This cvar selects the color used to display level 2 (critical) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg3color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 3 (chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg4color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 4 (team chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor2===<br /> integer: 4&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen that are sent to everyone. Available colors are the same as for msg0color. <br /> <br /> ===st_scale===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, the status bar will be scaled so that it covers the entire width of the screen in higher resolutions. At low resolutions this may look ugly, but at high resolutions it should look good enough.<br /> <br /> ==Renderer==<br /> <br /> ===r_columnmethod===<br /> integer: 1&lt;br&gt;<br /> Selects which of two algorithms to use to draw sprites and masked textures. Method 0 is the original algorithm used by DOOM. Method 1 is a new algorithm optimized for Pentium IIs and can perform significantly better with that or comparable processors. Ironically, method 0 is slightly faster than method 1 on Pentium III and Athlon processors (though not significantly so). <br /> <br /> ===r_detail===<br /> integer: 0&lt;br&gt;<br /> This cvar selects the detail level of the view window. Valid values are: <br /> <br /> #Normal detail level. Equivalent to Doom's high detail mode. <br /> #Double pixels horizontally. Equivalent to Doom's low detail mode. <br /> #Double pixels vertically. <br /> #Double pixels horizontally and vertically. <br /> <br /> Because of the way the renderer works, doubling pixels horizontally offers more of a speed-up than doubling them vertically does. Unless you have a very slow computer, there should be no reason to use any detail level other than 0. <br /> <br /> ===r_drawflat===<br /> boolean: false&lt;br&gt;<br /> When set to 0, segs will be drawn as solid colors instead of textures. This is useful if you want to see how a node builder split a level's linedefs. Otherwise, it just looks ugly. <br /> <br /> ===r_drawfuzzbr===<br /> boolean: true&lt;br&gt;<br /> When set to false, the &quot;fuzz&quot; effect on spectres and partially invisible players will be replaced with translucency. <br /> <br /> ===r_drawmirrors===<br /> boolean: true&lt;br&gt;<br /> Setting this false will disable the display of mirrors.<br /> <br /> ===r_drawplayersprites===<br /> boolean: true&lt;br&gt;<br /> When false, the game will not draw the player's weapon or muzzle flash, which can be nice for screenshots. <br /> <br /> ===r_drawtrans===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will disable all translucency effects in the game.<br /> <br /> ===r_fogboundary===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will disable the display of fog boundaries. Fog boundaries are sections where two areas with different fog colors meet. If the boundary is not drawn, then it will look like there is no fog at all in front of the boundary. Some old levels may look bad with fog boundary drawing enabled, which is why this cvar is available.<br /> <br /> ===r_particles===<br /> boolean: true&lt;br&gt;<br /> If set to true, particles are drawn. Otherwise, they aren't. <br /> <br /> ===r_stretchsky===<br /> boolean: true&lt;br&gt;<br /> Controls whether or not short sky textures are stretched so that you don't see them wrap when you look up. <br /> <br /> ===r_viewsize===<br /> string&lt;br&gt;<br /> This cvar contains the width and height of the current view window. This cvar is read only. <br /> <br /> ===r_visibility [visibility]===<br /> Without any parameters, displays the current visibility. With a parameter, the visibility is set. Standard visibility for the Doom engine is 8. Visibility determines how quickly light drops off with distance from the viewer. At 0 visibility, there is no change in lighting with depth.<br /> <br /> ==Video==<br /> <br /> ===fullscreen===<br /> boolean: true&lt;br&gt;<br /> If this cvar is true, the game will be displayed fullscreen. Otherwise, it will be drawn in a window. Some video cards may require that you have fullscreen false in order to run ZDoom. <br /> <br /> ===vid_attachedsurfaces (Win32 only)===<br /> boolean: false&lt;br&gt;<br /> Controls how the game allocates video memory. False is the standard setting and will always produce a useable display. If you find that there are patches of pure black and pure white on the screen (especially noticeable when a demon is right in your face), try setting this to true. Certain old Windows 95 video drivers are said to need this fix, and it is also necessary under NT 4. Unfortunately, many new video drivers (including those under NT 4) will produce a scrambled display if the screen width is not 512 or 1024 pixels and this is set to true.<br /> <br /> ===vid_currentmode===<br /> Displays the resolution of the current video mode.<br /> <br /> ===vid_defbits===<br /> integer: 8&lt;br&gt;<br /> Ignored. This cvar is meant to specify the default screen depth, but the setting is currently ignored because only 256-color displays are supported.<br /> <br /> ===vid_defheight===<br /> integer: 200&lt;br&gt;<br /> Specifies the default screen height to use if not overridden at the command line by the -height switch.<br /> <br /> ===vid_defwidth===<br /> integer: 320&lt;br&gt;<br /> Specifies the default screen width to use if not overridden at the command line with the -width switch.<br /> <br /> ===vid_listmodes===<br /> Lists all resolutions supported by the current display driver.<br /> <br /> ===vid_fps===<br /> boolean: false&lt;br&gt;<br /> When true, displays the average framerate over the past second in the lower-left corner of the screen. Because Doom's internal game rate and frame rate are linked, the framerate will never be (much) above 35 fps.<br /> <br /> ===vid_noblitter (Win32 only)===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will allow the use of the hardware to assist moving image data to video memory. When I initial wrote the code to use the blitter, it was faster than not using it. Now the blitter is slower, and I can't figure out why, so the default is true.<br /> <br /> ===vid_palettehack (Win32 only)===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, the game will refresh the palette every time the screen is redrawn. This can be useful with some buggy video drivers. If the display is fine without it, leave it that way because this can slightly slow things down.<br /> <br /> ===vid_setmode (width) (height) [depth]===<br /> Sets the screen mode to width x height with an optional color depth (if your video hardware supports it). Only a depth of 8 is supported. See also vid_currentmode, vid_listmodes<br /> <br /> ===vid_vsync (Win32 only)===<br /> boolean: true&lt;br&gt;<br /> Set this to false to disable vsync. Not all video cards support disabling vsync.<br /> <br /> ==Bots==<br /> * [[Bots]]<br /> <br /> ==Automap==<br /> * [[AutoMap]]<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=510 2004-01-06T11:21:03Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, etc...<br /> <br /> You access the console by pressing &quot;~&quot; at any time. (This depends on your keyboard layout, for German keyboard, it is &quot;^&quot;, but to summarize it, it is the key above TAB.)<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. (EDIT: That's just a string, i.e. testcolor &quot;ff 00 00&quot;)<br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key?ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> <br /> ===addkeysection (menu-heading) (ini-section-name)&lt;br&gt;===<br /> This command does two things. First, it adds a new heading called menu-heading to the controls menu. You can use the addmenukey command to add your own custom keys beneath this heading. Second, it loads all the bindings from the corresponding ini-section-name section in zdoom.ini. You can use this command multiple times to create different sections in the menu and ini for different sets of commands. If you use a menu-heading that was already added to the menu, new controls added with addmenukey will appear at the end of that section, but the bindings will not be reloaded from the ini. <br /> <br /> ===addmenukey (description) (command)&lt;br&gt;===<br /> Adds a new control to the controls menu. Description is the name of this control in the menu, and command is a console command or alias to be executed when the control is pressed. New controls are added to the last section specified with addkeysection.<br /> <br /> ===addslot (slot) (weapon)===<br /> Adds a single weapon to the list of weapons in a weapon slot.<br /> <br /> ===alias (new-command) [command-string]===<br /> If specified with no parameters, will display a list of all current aliases. If only new-command is specified, it will be removed from the list of aliases. If command-string is also specified, it will be added to the list of aliases as new-command. For example, to create a new command to kill the monsters on the level, you can use the command: <br /> alias massacre &quot;kill monsters&quot;<br /> Then you can use the newly created massacre command to kill all the monsters on the level.<br /> <br /> ===archivecvar (cvar)===<br /> When you create a custom cvar with the set command, it will not normally be saved in the ini. You can use archivecvar after creating the cvar to indicate that the custom cvar's value should persist even after you quit.<br /> <br /> ===atexit [command]===<br /> If you specify a command, it will be added to a list of console commands to execute when the user quits the game. Commands are executed in the reverse order that they were added in. If you do not specify any arguments to atexit, then it will list the current set of commands that will execute when you quit.<br /> <br /> ===bind (key [command string])===<br /> If no parameters are specified, the entire list of bound keys will be printed to the console. If only [key] is specified, the binding for that specific key will be printed. If both [key] and [command string] are specified, [command string] will be bound to [key]. <br /> <br /> ===binddefaults===<br /> Binds all keys to their default commands. This will not unbind any keys that do not have any default bindings, so if you want to properly restore the default controls, you need to use unbindall first. <br /> defaultbind key command<br /> Binds command to the key if and only if key is not already bound and there are no keys already bound to command.<br /> <br /> ===doublebind (key [command string])===<br /> This command works just like bind, except it controls the action that occurs when a key is double-clicked. If a key does not have a doublebinding, then double-clicking it has the same result as pressing it twice. Otherwise, the first press will execute the normal command set with bind, and the second press of the double-click will execute the command set with doublebind. <br /> <br /> ===eval expression [variable]===<br /> Evaluates a mathematical expression and either prints it to the console or stores it in variable. Expressions are written using prefix notation instead of the more common infix notation. Basically, you first specify what you want to do (the operator) and then what you want to do it to (the operands). You must separate operators and operands with spaces. <br /> <br /> Examples: <br /> To compute 2+2: <br /> eval + 2 2To compute 5-3: <br /> eval - 5 3To compute 2+(5*6): <br /> eval + 2 * 5 6To decrease the number of screenblocks: <br /> eval - $screenblocks 1 screenblocksThe supported operators are:<br /> + a b Adds a and b. <br /> - a b Subtracts b from a. <br /> * a b Multiplies a and b. <br /> / a b Divides a by b. <br /> % a b Calculates the remainder of a/b. <br /> ^ a b Raises a to the b-th power . <br /> &lt; a b Produces 1 if a is less than b and 0 if not. <br /> &lt;= a b Produces 1 if a is less than or equal to b and 0 if not. <br /> &gt; a b Produces 1 if a is greater than b and 0 if not. <br /> &gt;= a b Produces 1 if a is greater than or equal to b and 0 if not. <br /> = a b Produces 1 if a is equal to b and 0 if not.<br /> <br /> == a b Produces 1 if a is equal to b and 0 if not. <br /> != a b Produces 1 if a is not equal to b and 0 if it is. <br /> &lt;&gt; a b Produces 1 if a is not equal to b and 0 if is. <br /> xor a b Calculates the bit-wise exclusive-or of a and b. <br /> &amp; a b Calculates the bit-wise and of a and b. <br /> | a b Calculates the bit-wise or of a and b. <br /> &amp;&amp; a b Calculates the logical and of a and b. <br /> || a b Calculates the logical or of a and b. <br /> <br /> ===exec (script-file)===<br /> Executes a series of commands stored in the script-file as if they had been typed in at the console directly. <br /> <br /> ===key value1 [value2]===<br /> Translates all parameters to the command into their corresponding key values which are used internally for command and alias lookup. Probably not very useful for the average user. <br /> <br /> ===puke (script [arguments])===<br /> Executes an ACS script on the current map, optionally passing it up to three numerical arguments. <br /> <br /> ===pullin (wadfile)===<br /> Loads a wadfile at startup. This command is only valid inside .cfg files that have been execed at startup.<br /> <br /> ===set (cvar) (value)===<br /> Sets cvar to value. If cvar does not exist, it will be created. <br /> <br /> ===rebind (binding)===<br /> Changes the binding for the key that caused the rebind command to execute. For obvious reasons, this command cannot be used at the console.<br /> <br /> Example: <br /> <br /> bind b &quot;echo setting 1; rebind \&quot;echo setting 2\&quot;&quot;<br /> <br /> This will cause the first press of b to echo &quot;setting 1&quot; to the console. All future presses of b will echo &quot;setting 2&quot; instead. <br /> <br /> ===unbind (key)===<br /> Removes a binding from the specified key.<br /> <br /> ===unbindall===<br /> Removes all bindings and doublebindings from every key. To restore the default bindings, you can use the binddefaults command. There is no way to restore any custom bindings after issuing this command except by retyping each bind command or using the controls setup menu.<br /> <br /> ===undoublebind (key)===<br /> Removes a doublebinding from the specified key.<br /> <br /> ===unset (cvar)===<br /> Undefines a user-created cvar.<br /> <br /> ==Screenshots==<br /> <br /> ===png_gamma===<br /> float: 0&lt;br&gt;<br /> Controls the gamma level stored in PNG screenshots. If this is 0, then your current gamma setting will be used.<br /> <br /> ===png_level===<br /> integer: 5&lt;br&gt;<br /> This is the level of compression to use for PNG screenshots. 0 is no compression at all, 1 is minimal compression (fastest), 9 is maximum compression (slowest), and intermediate values offer intermediate compression. 5 is offers a decent trade-of between file size and compression time. An uncompressed image will not neccessarily save faster than a compressed image, because the extra time needed to write out a complete uncompressed image may be longer than the time required to compress the image. If you need to create screenshots as quickly as possible, consider setting screenshot_type to &quot;pcx&quot;. <br /> <br /> ===screenshot [file]===<br /> Dumps a copy of the screen to disk as a PNG or PCX file. If file is not specified, the screenshot will be saved to the directory the game was run from with a name of the form doom????.png. <br /> <br /> ===screenshot_quiet===<br /> boolean: false&lt;br&gt;<br /> Setting this to true will suppress the messages informing you what file a screenshot was saved to.<br /> <br /> ===screenshot_type===<br /> string: &quot;png&quot;&lt;br&gt;<br /> Determines the type of screenshots that will be saved. This can be either &quot;png&quot; or &quot;pcx&quot;. In my empirical studies, PNG screenshots are about half the size of pcx screenshots. PCX screenshots have the advantage that they require less time to create so are most useful for rapid screenshot generation. The following sequence of console commands will take a screenshot every frame. You can use an external program to assemble these into a video, if desired. <br /> <br /> screenshot_type &quot;png&quot;&lt;br&gt;<br /> screenshot_quiet true&lt;br&gt;<br /> alias autoshot &quot;screenshot; wait 1; autoshot&quot;&lt;br&gt;<br /> autoshot&lt;br&gt;<br /> <br /> If you use the autoshot alias, the command alias autoshot will stop automatic screenshot taking before you hit 10000 screenshots (approximately 4 minutes, 45 seconds).<br /> <br /> ===storesavepic===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will produce smaller savegames (by about 14k typically) by not storing a screenshot inside the savegame.<br /> <br /> ==Chatting==<br /> <br /> ===chat_substitution===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want to chat using special keywords that will be replaced with appropriate text when your messages are sent. The supported keywords are:<br /> <br /> $health &lt;br&gt;<br /> Replaced by your current health. &lt;br&gt;<br /> $weapon &lt;br&gt;<br /> Replaced by the name of your current weapon. &lt;br&gt;<br /> $armor &lt;br&gt;<br /> Replaced by your current armor count. &lt;br&gt;<br /> $ammocount &lt;br&gt;<br /> Replaced by your current ammo count. &lt;br&gt;<br /> $ammo &lt;br&gt;<br /> Replaced by the name of your current ammo.<br /> <br /> As an example, if you just started a new game of Doom and have chat substitution turned on, when you send the message &quot;My health is $health, and I am using a $weapon&quot;, the message that is actually sent will be &quot;My health is 100, and I am using a Pistol&quot;.<br /> <br /> chatmacro0&lt;br&gt;<br /> chatmacro1&lt;br&gt;<br /> chatmacro2&lt;br&gt;<br /> chatmacro3&lt;br&gt;<br /> chatmacro4&lt;br&gt;<br /> chatmacro5&lt;br&gt;<br /> chatmacro6&lt;br&gt;<br /> chatmacro7&lt;br&gt;<br /> chatmacro8&lt;br&gt;<br /> chatmacro9&lt;br&gt;<br /> string&lt;br&gt;<br /> These are all strings that can be assigned to hotkeys in chat mode. To use these, enter chat mode and then hold down Alt and press one of the number keys. The string stored in the corresponding chatmacro cvar will be sent as if you had typed it yourself. <br /> <br /> ===messagemode===<br /> Enters message entry mode. Anything typed while in this mode will be sent to everyone else as if you had used the say command once you press enter. <br /> <br /> ===messagemode2===<br /> This is just like messagemode except that the message is only sent to other members of your team. If teamplay is false or you don't have a team, then this command will work just like messagemode and send the message to everyone. <br /> <br /> ===say (message)===<br /> Sends a message to everyone playing. If your message begins with &quot;/me&quot; then &quot;/me&quot; will be replaced by your name ala IRC. <br /> <br /> ===say_team (message)===<br /> This is just like say except it only sends a message to your teammates. If teamplay is inactive, then this command will act exactly like say and send the message to everyone.<br /> <br /> ==Cheating==<br /> <br /> ===sv_cheats===<br /> boolean: false<br /> When true, cheats will be allowed in Nightmare difficulty and network games. For purposes of fairness, this cvar can only be set from the command line when you run ZDoom. This is to avoid situations where the key player in a multiplayer game (player 1) could go to the console and type something like this:<br /> <br /> sv_cheats 1<br /> god<br /> sv_cheats 0<br /> <br /> whereby rendering himself immune to the attacks of others.<br /> <br /> ===anubis===<br /> Toggles monster fear on and off. Scared monsters will run away from you and attack less frequently.<br /> <br /> ===fly===<br /> Toggles fly mode on and off.<br /> <br /> ===give (item)===<br /> Gives an item to the player. Give understands the following special items: <br /> all - gives you everything <br /> health - gives you full health <br /> weapons - gives you every weapon <br /> ammo - gives you full ammo <br /> armor - gives you full armor <br /> keys - gives you every key <br /> It also understands the names of individual inventory items. Use the command dumpclasses inventory for a complete list of these. <br /> <br /> ===god===<br /> Toggles God (Degreelessness) mode on/off. While active, you cannot be hurt by normal attacks (although telefragging will still kill you). Also known as iddqd. <br /> <br /> ===iddqd===<br /> The same as god, except it also gives you 100 health.<br /> <br /> ===kill [monsters]===<br /> If used as &quot;kill monsters&quot;, will kill all monsters on the level. Otherwise, it will kill you instead. This command is broken in netgames, so don't use it unless you are playing a single player game. <br /> <br /> ===logfile [log-file]===<br /> If log-file is not specified, console logging will be stopped (if active). Otherwise, a file named log-file will be created on disk, and all console output will be recorded in it as well as on the screen. <br /> <br /> ===mdk===<br /> This cheat will kill whatever you are looking at.<br /> <br /> ===morphme===<br /> Transforms you into a chicken in Heretic and a pig in Hexen and Doom (The latter only happens if you have the releven graphics present).<br /> <br /> ===noclip===<br /> Toggles noclipping mode on/off. <br /> <br /> ===notarget===<br /> Toggles notarget mode on/off. While active, monsters will not target you unless you hurt them first. In &quot;modern FPS&quot;, monsters &quot;can't find you&quot; when in notarget mode. This is not the case with ZDoom.<br /> <br /> ===powerup===<br /> Powers you up in Heretic as if you had used a Tome of Power.<br /> <br /> ===sv_fastweapons (0-2)===<br /> Increases speed of weapons in Doom, Heretic, and Hexen. Setting to 2 makes weapons even faster.<br /> <br /> ===turbo===<br /> float: 100&lt;br&gt;<br /> This cvar affects how quickly the player moves. A value of 100 will cause the player to move at normal speed, 200 will cause the player to move at 200% of normal speed, 50 will cause the player to move at 50% of normal speed, etc. Valid values range from 10 to 256.<br /> <br /> ==Display==<br /> <br /> ===bumpgamma===<br /> Increases the current gamma level by 0.1. If the new gamma level would be greater than 3.0, it wraps the gamma around to 1.0 <br /> <br /> ===cl_bbannounce===<br /> boolean: false&lt;br&gt;<br /> When true, enables the Bloodbath announcer for deathmatch games. The Bloodbath announcer is &quot;The Voice&quot; from Monolith Software's Blood game. To hear the announcer, you need to load Blood's sounds.rff either at the command line or through one of zdoom.ini's [*.Autoload] sections. You can get this file either from the demo or full version of Blood. If you don't have sounds.rff, you can still see the announcer's messages even though you won't hear anything. <br /> <br /> ===cl_showmultikills===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player makes several kills in a short period of time.<br /> <br /> ===cl_showsprees===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player is on a killing spree.<br /> <br /> ===cl_spreaddecals===<br /> boolean: true&lt;br&gt;<br /> ZDoom clips decals to sidedefs. In order to hide this, the game will create as many duplicate decals on adjoining sidedefs as needed to make it appear that there is only one unbroken decal on the wall. Set this cvar to false if you don't want this.<br /> <br /> ===con_centernotify===<br /> boolean: false for Doom, true for Heretic and Hexen&lt;br&gt;<br /> When true, notify messages at the top of the screen are centered. Otherwise, they are justified against the left margin.<br /> <br /> ===con_midtime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that messages in the middle of the screen will be displayed before they dispapper. <br /> <br /> ===con_notifytime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that new messages will stay at the top of the screen before they start scrolling away. <br /> <br /> ===con_scaletext===<br /> boolean: false&lt;br&gt;<br /> If this cvar is true, then message text will be scaled to larger sizes depending on the screen resolution so that it will stay approximately the same size it would be on a 320x200 screen. <br /> <br /> ===crosshair===<br /> integer: 0&lt;br&gt;<br /> If this cvar is non-zero, it draws a crosshair. If this cvar is negative, the crosshair is translucent, otherwise it is opaque. The specific crosshair drawn depends on the value of this cvar. <br /> <br /> ===crosshaircolor===<br /> color: &quot;ff 00 00&quot;&lt;br&gt;<br /> This is the crosshair's color if crosshairhealth is false.<br /> <br /> ===crosshairgrow===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to temporarily enlarge each time you pick up an item.<br /> <br /> ===crosshairhealth===<br /> boolean: true&lt;br&gt;<br /> When true, the crosshair's color reflects your current health. Green is healthy, red is near death, and intermediate colors are somewhere in between. Set this to false, if you want the crosshair to have a constant color (specified by the crosshaircolor cvar) instead.<br /> <br /> ===crosshairscale===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to always appear the same size at all resolutions. Leaving it at false causes the crosshair to be drawn normally.<br /> <br /> ===gamma===<br /> float: 1.0&lt;br&gt;<br /> Controls the amount of gamma correction applied to the display. 1.0 is equivalent to no correction, while larger numbers translate into a brighter display, and smaller numbers translate into a darker display. 0.0 is invalid and will be rejected. Negative numbers are technically invalid but will be accepted solely for the novelty value doing so provides. <br /> <br /> ===hud_scale===<br /> boolean: false&lt;br&gt;<br /> Controls scaling of the fullscreen hud. At resolutions of 640x400 or above, setting this cvar to true will cause the icons to be scaled to approximately the same size they would be at 320x200. If this cvar is false, the icons will always be drawn without any scaling. <br /> <br /> ===msg===<br /> integer: 0&lt;br&gt;<br /> This is the minimum message level that you will see. You will not see any messages with a lower priority than this. The different message levels are: <br /> <br /> #Item pickup <br /> #Obituaries <br /> #Critical messages <br /> #Chat messages <br /> #Chat messages from a teammate <br /> <br /> ===msg0color===<br /> integer: 6&lt;br&gt;<br /> This cvar controls the color used to display level 0 (item pickup) messages. Available colors are: <br /> <br /> #Brick <br /> #Tan <br /> #Gray <br /> #Green <br /> #Brown <br /> #Gold <br /> #Red <br /> #Blue <br /> #Orange <br /> #White <br /> #Yellow <br /> <br /> ===msg1color===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display level 1 (obituary) messages. Available colors are the same as for&quot; msg0color. <br /> <br /> ===msg2color===<br /> integer: 2&lt;br&gt;<br /> This cvar selects the color used to display level 2 (critical) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg3color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 3 (chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg4color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 4 (team chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor2===<br /> integer: 4&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen that are sent to everyone. Available colors are the same as for msg0color. <br /> <br /> ===st_scale===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, the status bar will be scaled so that it covers the entire width of the screen in higher resolutions. At low resolutions this may look ugly, but at high resolutions it should look good enough.<br /> <br /> ==Renderer==<br /> <br /> ===r_columnmethod===<br /> integer: 1&lt;br&gt;<br /> Selects which of two algorithms to use to draw sprites and masked textures. Method 0 is the original algorithm used by DOOM. Method 1 is a new algorithm optimized for Pentium IIs and can perform significantly better with that or comparable processors. Ironically, method 0 is slightly faster than method 1 on Pentium III and Athlon processors (though not significantly so). <br /> <br /> ===r_detail===<br /> integer: 0&lt;br&gt;<br /> This cvar selects the detail level of the view window. Valid values are: <br /> <br /> #Normal detail level. Equivalent to Doom's high detail mode. <br /> #Double pixels horizontally. Equivalent to Doom's low detail mode. <br /> #Double pixels vertically. <br /> #Double pixels horizontally and vertically. <br /> <br /> Because of the way the renderer works, doubling pixels horizontally offers more of a speed-up than doubling them vertically does. Unless you have a very slow computer, there should be no reason to use any detail level other than 0. <br /> <br /> ===r_drawflat===<br /> boolean: false&lt;br&gt;<br /> When set to 0, segs will be drawn as solid colors instead of textures. This is useful if you want to see how a node builder split a level's linedefs. Otherwise, it just looks ugly. <br /> <br /> ===r_drawfuzzbr===<br /> boolean: true&lt;br&gt;<br /> When set to false, the &quot;fuzz&quot; effect on spectres and partially invisible players will be replaced with translucency. <br /> <br /> ===r_drawmirrors===<br /> boolean: true&lt;br&gt;<br /> Setting this false will disable the display of mirrors.<br /> <br /> ===r_drawplayersprites===<br /> boolean: true&lt;br&gt;<br /> When false, the game will not draw the player's weapon or muzzle flash, which can be nice for screenshots. <br /> <br /> ===r_drawtrans===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will disable all translucency effects in the game.<br /> <br /> ===r_fogboundary===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will disable the display of fog boundaries. Fog boundaries are sections where two areas with different fog colors meet. If the boundary is not drawn, then it will look like there is no fog at all in front of the boundary. Some old levels may look bad with fog boundary drawing enabled, which is why this cvar is available.<br /> <br /> ===r_particles===<br /> boolean: true&lt;br&gt;<br /> If set to true, particles are drawn. Otherwise, they aren't. <br /> <br /> ===r_stretchsky===<br /> boolean: true&lt;br&gt;<br /> Controls whether or not short sky textures are stretched so that you don't see them wrap when you look up. <br /> <br /> ===r_viewsize===<br /> string&lt;br&gt;<br /> This cvar contains the width and height of the current view window. This cvar is read only. <br /> <br /> ===r_visibility [visibility]===<br /> Without any parameters, displays the current visibility. With a parameter, the visibility is set. Standard visibility for the Doom engine is 8. Visibility determines how quickly light drops off with distance from the viewer. At 0 visibility, there is no change in lighting with depth.<br /> <br /> ==Video==<br /> * [[Video]]<br /> <br /> ==Bots==<br /> * [[Bots]]<br /> <br /> ==Automap==<br /> * [[AutoMap]]<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Talk:Console_commands&diff=515 2004-01-05T11:44:15Z

<p>Lexus Alyus: </p> <hr /> <div>Okay, I've attempted to clean up this page by having sections and subsections to make it a lot easier to navigate. I think this is a good idea, but that is just my opinion and you can disagree if you want. If you disagree then let me know.<br /> <br /> Anyway, I've gotten so far, but i've ran out of time, so if some kind soul could finish this off :-).<br /> <br /> -Lexus Alyus 5/1/04</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Talk:Console_commands&diff=426 2004-01-05T11:44:01Z

<p>Lexus Alyus: </p> <hr /> <div>Okay&lt; i've attempoted to clean up this poage by having sections and subsections to make it a lot easier to navigate. I think this is a good idea, but that is just my opinion and you can disagree if you want. If you disagree then let me know.<br /> <br /> Anyway, I've gotten so far, but i've ran out of time, so if some kind soul could finish this off :-).<br /> <br /> -Lexus Alyus 5/1/04</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=428 2004-01-05T11:42:15Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, ect...<br /> <br /> you access the console by pressing &quot;~&quot; at any time<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. <br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward&lt;br&gt;<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;&lt;br&gt;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key—ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> <br /> ===addkeysection (menu-heading) (ini-section-name)&lt;br&gt;===<br /> This command does two things. First, it adds a new heading called menu-heading to the controls menu. You can use the addmenukey command to add your own custom keys beneath this heading. Second, it loads all the bindings from the corresponding ini-section-name section in zdoom.ini. You can use this command multiple times to create different sections in the menu and ini for different sets of commands. If you use a menu-heading that was already added to the menu, new controls added with addmenukey will appear at the end of that section, but the bindings will not be reloaded from the ini. <br /> <br /> ===addmenukey (description) (command)&lt;br&gt;===<br /> Adds a new control to the controls menu. Description is the name of this control in the menu, and command is a console command or alias to be executed when the control is pressed. New controls are added to the last section specified with addkeysection.<br /> <br /> ===addslot (slot) (weapon)===<br /> Adds a single weapon to the list of weapons in a weapon slot.<br /> <br /> ===alias (new-command) [command-string]===<br /> If specified with no parameters, will display a list of all current aliases. If only new-command is specified, it will be removed from the list of aliases. If command-string is also specified, it will be added to the list of aliases as new-command. For example, to create a new command to kill the monsters on the level, you can use the command: <br /> alias massacre &quot;kill monsters&quot;Then you can use the newly created massacre command to kill all the monsters on the level.<br /> <br /> ===archivecvar (cvar)===<br /> When you create a custom cvar with the set command, it will not normally be saved in the ini. You can use archivecvar after creating the cvar to indicate that the custom cvar's value should persist even after you quit.<br /> <br /> ===atexit [command]===<br /> If you specify a command, it will be added to a list of console commands to execute when the user quits the game. Commands are executed in the reverse order that they were added in. If you do not specify any arguments to atexit, then it will list the current set of commands that will execute when you quit.<br /> <br /> ===bind (key [command string])===<br /> If no parameters are specified, the entire list of bound keys will be printed to the console. If only [key] is specified, the binding for that specific key will be printed. If both [key] and [command string] are specified, [command string] will be bound to [key]. <br /> <br /> ===binddefaults===<br /> Binds all keys to their default commands. This will not unbind any keys that do not have any default bindings, so if you want to properly restore the default controls, you need to use unbindall first. <br /> defaultbind key command<br /> Binds command to the key if and only if key is not already bound and there are no keys already bound to command.<br /> <br /> ===doublebind (key [command string])===<br /> This command works just like bind, except it controls the action that occurs when a key is double-clicked. If a key does not have a doublebinding, then double-clicking it has the same result as pressing it twice. Otherwise, the first press will execute the normal command set with bind, and the second press of the double-click will execute the command set with doublebind. <br /> <br /> ===eval expression [variable]===<br /> Evaluates a mathematical expression and either prints it to the console or stores it in variable. Expressions are written using prefix notation instead of the more common infix notation. Basically, you first specify what you want to do (the operator) and then what you want to do it to (the operands). You must separate operators and operands with spaces. <br /> <br /> Examples: <br /> To compute 2+2: <br /> eval + 2 2To compute 5-3: <br /> eval - 5 3To compute 2+(5*6): <br /> eval + 2 * 5 6To decrease the number of screenblocks: <br /> eval - $screenblocks 1 screenblocksThe supported operators are:<br /> + a b Adds a and b. <br /> - a b Subtracts b from a. <br /> * a b Multiplies a and b. <br /> / a b Divides a by b. <br /> % a b Calculates the remainder of a/b. <br /> ^ a b Raises a to the b-th power . <br /> &lt; a b Produces 1 if a is less than b and 0 if not. <br /> &lt;= a b Produces 1 if a is less than or equal to b and 0 if not. <br /> &gt; a b Produces 1 if a is greater than b and 0 if not. <br /> &gt;= a b Produces 1 if a is greater than or equal to b and 0 if not. <br /> = a b Produces 1 if a is equal to b and 0 if not. <br /> == a b Produces 1 if a is equal to b and 0 if not. <br /> != a b Produces 1 if a is not equal to b and 0 if it is. <br /> &lt;&gt; a b Produces 1 if a is not equal to b and 0 if is. <br /> xor a b Calculates the bit-wise exclusive-or of a and b. <br /> &amp; a b Calculates the bit-wise and of a and b. <br /> | a b Calculates the bit-wise or of a and b. <br /> &amp;&amp; a b Calculates the logical and of a and b. <br /> || a b Calculates the logical or of a and b. <br /> <br /> ===exec (script-file)===<br /> Executes a series of commands stored in the script-file as if they had been typed in at the console directly. <br /> <br /> ===key value1 [value2]===<br /> Translates all parameters to the command into their corresponding key values which are used internally for command and alias lookup. Probably not very useful for the average user. <br /> <br /> ===puke (script [arguments])===<br /> Executes an ACS script on the current map, optionally passing it up to three numerical arguments. <br /> <br /> ===pullin (wadfile)===<br /> Loads a wadfile at startup. This command is only valid inside .cfg files that have been execed at startup.<br /> <br /> ===set (cvar) (value)===<br /> Sets cvar to value. If cvar does not exist, it will be created. <br /> <br /> ===rebind (binding)===<br /> Changes the binding for the key that caused the rebind command to execute. For obvious reasons, this command cannot be used at the console.<br /> <br /> Example: <br /> <br /> bind b &quot;echo setting 1; rebind \&quot;echo setting 2\&quot;&quot;<br /> <br /> This will cause the first press of b to echo &quot;setting 1&quot; to the console. All future presses of b will echo &quot;setting 2&quot; instead. <br /> <br /> ===unbind (key)===<br /> Removes a binding from the specified key.<br /> <br /> ===unbindall===<br /> Removes all bindings and doublebindings from every key. To restore the default bindings, you can use the binddefaults command. There is no way to restore any custom bindings after issuing this command except by retyping each bind command or using the controls setup menu.<br /> <br /> ===undoublebind (key)===<br /> Removes a doublebinding from the specified key.<br /> <br /> ===unset (cvar)===<br /> Undefines a user-created cvar.<br /> <br /> ==Screenshots==<br /> <br /> ===png_gamma===<br /> float: 0&lt;br&gt;<br /> Controls the gamma level stored in PNG screenshots. If this is 0, then your current gamma setting will be used.<br /> <br /> ===png_level===<br /> integer: 5&lt;br&gt;<br /> This is the level of compression to use for PNG screenshots. 0 is no compression at all, 1 is minimal compression (fastest), 9 is maximum compression (slowest), and intermediate values offer intermediate compression. 5 is offers a decent trade-of between file size and compression time. An uncompressed image will not neccessarily save faster than a compressed image, because the extra time needed to write out a complete uncompressed image may be longer than the time required to compress the image. If you need to create screenshots as quickly as possible, consider setting screenshot_type to &quot;pcx&quot;. <br /> <br /> ===screenshot [file]===<br /> Dumps a copy of the screen to disk as a PNG or PCX file. If file is not specified, the screenshot will be saved to the directory the game was run from with a name of the form doom????.png. <br /> <br /> ===screenshot_quiet===<br /> boolean: false&lt;br&gt;<br /> Setting this to true will suppress the messages informing you what file a screenshot was saved to.<br /> <br /> ===screenshot_type===<br /> string: &quot;png&quot;&lt;br&gt;<br /> Determines the type of screenshots that will be saved. This can be either &quot;png&quot; or &quot;pcx&quot;. In my empirical studies, PNG screenshots are about half the size of pcx screenshots. PCX screenshots have the advantage that they require less time to create so are most useful for rapid screenshot generation. The following sequence of console commands will take a screenshot every frame. You can use an external program to assemble these into a video, if desired. <br /> <br /> screenshot_type &quot;png&quot;&lt;br&gt;<br /> screenshot_quiet true&lt;br&gt;<br /> alias autoshot &quot;screenshot; wait 1; autoshot&quot;&lt;br&gt;<br /> autoshot&lt;br&gt;<br /> <br /> If you use the autoshot alias, the command alias autoshot will stop automatic screenshot taking before you hit 10000 screenshots (approximately 4 minutes, 45 seconds).<br /> <br /> ===storesavepic===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will produce smaller savegames (by about 14k typically) by not storing a screenshot inside the savegame.<br /> <br /> ==Chatting==<br /> <br /> ===chat_substitution===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want to chat using special keywords that will be replaced with appropriate text when your messages are sent. The supported keywords are:<br /> <br /> $health &lt;br&gt;<br /> Replaced by your current health. &lt;br&gt;<br /> $weapon &lt;br&gt;<br /> Replaced by the name of your current weapon. &lt;br&gt;<br /> $armor &lt;br&gt;<br /> Replaced by your current armor count. &lt;br&gt;<br /> $ammocount &lt;br&gt;<br /> Replaced by your current ammo count. &lt;br&gt;<br /> $ammo &lt;br&gt;<br /> Replaced by the name of your current ammo.<br /> <br /> As an example, if you just started a new game of Doom and have chat substitution turned on, when you send the message &quot;My health is $health, and I am using a $weapon&quot;, the message that is actually sent will be &quot;My health is 100, and I am using a Pistol&quot;.<br /> <br /> chatmacro0&lt;br&gt;<br /> chatmacro1&lt;br&gt;<br /> chatmacro2&lt;br&gt;<br /> chatmacro3&lt;br&gt;<br /> chatmacro4&lt;br&gt;<br /> chatmacro5&lt;br&gt;<br /> chatmacro6&lt;br&gt;<br /> chatmacro7&lt;br&gt;<br /> chatmacro8&lt;br&gt;<br /> chatmacro9&lt;br&gt;<br /> string&lt;br&gt;<br /> These are all strings that can be assigned to hotkeys in chat mode. To use these, enter chat mode and then hold down Alt and press one of the number keys. The string stored in the corresponding chatmacro cvar will be sent as if you had typed it yourself. <br /> <br /> ===messagemode===<br /> Enters message entry mode. Anything typed while in this mode will be sent to everyone else as if you had used the say command once you press enter. <br /> <br /> ===messagemode2===<br /> This is just like messagemode except that the message is only sent to other members of your team. If teamplay is false or you don't have a team, then this command will work just like messagemode and send the message to everyone. <br /> <br /> ===say (message)===<br /> Sends a message to everyone playing. If your message begins with &quot;/me&quot; then &quot;/me&quot; will be replaced by your name ala IRC. <br /> <br /> ===say_team (message)===<br /> This is just like say except it only sends a message to your teammates. If teamplay is inactive, then this command will act exactly like say and send the message to everyone.<br /> <br /> ==Cheating==<br /> <br /> ===sv_cheats===<br /> boolean: false<br /> When true, cheats will be allowed in Nightmare difficulty and network games. For purposes of fairness, this cvar can only be set from the command line when you run ZDoom. This is to avoid situations where the key player in a multiplayer game (player 1) could go to the console and type something like this:<br /> <br /> sv_cheats 1&lt;br&gt;<br /> god&lt;br&gt;<br /> sv_cheats 0&lt;br&gt;<br /> <br /> whereby rendering himself immune to the attacks of others.<br /> <br /> ===anubis===<br /> Toggles monster fear on and off. Scared monsters will run away from you and attack less frequently.<br /> <br /> ===fly===<br /> Toggles fly mode on and off.<br /> <br /> ===give (item)===<br /> Gives an item to the player. Give understands the following special items: <br /> all - gives you everything <br /> health - gives you full health <br /> weapons - gives you every weapon <br /> ammo - gives you full ammo <br /> armor - gives you full armor <br /> keys - gives you every key <br /> It also understands the names of individual inventory items. Use the command dumpclasses inventory for a complete list of these. <br /> <br /> ===god===<br /> Toggles God (Degreelessness) mode on/off. While active, you cannot be hurt by normal attacks (although telefragging will still kill you). Also known as iddqd. <br /> <br /> ===iddqd===<br /> The same as god, except it also gives you 100 health.<br /> <br /> ===kill [monsters]===<br /> If used as &quot;kill monsters&quot;, will kill all monsters on the level. Otherwise, it will kill you instead. This command is broken in netgames, so don't use it unless you are playing a single player game. <br /> <br /> ===logfile [log-file]===<br /> If log-file is not specified, console logging will be stopped (if active). Otherwise, a file named log-file will be created on disk, and all console output will be recorded in it as well as on the screen. <br /> <br /> ===mdk===<br /> This cheat will kill whatever you are looking at.<br /> <br /> ===morphme===<br /> Transforms you into a chicken in Heretic and a pig in Hexen and Doom (The latter only happens if you have the releven graphics present).<br /> <br /> ===noclip===<br /> Toggles noclipping mode on/off. <br /> <br /> ===notarget===<br /> Toggles notarget mode on/off. While active, monsters will not target you unless you hurt them first. <br /> <br /> ===powerup===<br /> Powers you up in Heretic as if you had used a Tome of Power.<br /> <br /> ===turbo===<br /> float: 100&lt;br&gt;<br /> This cvar affects how quickly the player moves. A value of 100 will cause the player to move at normal speed, 200 will cause the player to move at 200% of normal speed, 50 will cause the player to move at 50% of normal speed, etc. Valid values range from 10 to 256.<br /> <br /> ==Display==<br /> <br /> ===bumpgamma===<br /> Increases the current gamma level by 0.1. If the new gamma level would be greater than 3.0, it wraps the gamma around to 1.0 <br /> <br /> ===cl_bbannounce===<br /> boolean: false&lt;br&gt;<br /> When true, enables the Bloodbath announcer for deathmatch games. The Bloodbath announcer is &quot;The Voice&quot; from Monolith Software's Blood game. To hear the announcer, you need to load Blood's sounds.rff either at the command line or through one of zdoom.ini's [*.Autoload] sections. You can get this file either from the demo or full version of Blood. If you don't have sounds.rff, you can still see the announcer's messages even though you won't hear anything. <br /> <br /> ===cl_showmultikills===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player makes several kills in a short period of time.<br /> <br /> ===cl_showsprees===<br /> boolean: true&lt;br&gt;<br /> Set this to false if you don't want to see Unreal Tournament-style messages when a player is on a killing spree.<br /> <br /> ===cl_spreaddecals===<br /> boolean: true&lt;br&gt;<br /> ZDoom clips decals to sidedefs. In order to hide this, the game will create as many duplicate decals on adjoining sidedefs as needed to make it appear that there is only one unbroken decal on the wall. Set this cvar to false if you don't want this.<br /> <br /> ===con_centernotify===<br /> boolean: false for Doom, true for Heretic and Hexen&lt;br&gt;<br /> When true, notify messages at the top of the screen are centered. Otherwise, they are justified against the left margin.<br /> <br /> ===con_midtime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that messages in the middle of the screen will be displayed before they dispapper. <br /> <br /> ===con_notifytime===<br /> float: 3&lt;br&gt;<br /> This is the number of seconds that new messages will stay at the top of the screen before they start scrolling away. <br /> <br /> ===con_scaletext===<br /> boolean: false&lt;br&gt;<br /> If this cvar is true, then message text will be scaled to larger sizes depending on the screen resolution so that it will stay approximately the same size it would be on a 320x200 screen. <br /> <br /> ===crosshair===<br /> integer: 0&lt;br&gt;<br /> If this cvar is non-zero, it draws a crosshair. If this cvar is negative, the crosshair is translucent, otherwise it is opaque. The specific crosshair drawn depends on the value of this cvar. <br /> <br /> ===crosshaircolor===<br /> color: &quot;ff 00 00&quot;&lt;br&gt;<br /> This is the crosshair's color if crosshairhealth is false.<br /> <br /> ===crosshairgrow===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to temporarily enlarge each time you pick up an item.<br /> <br /> ===crosshairhealth===<br /> boolean: true&lt;br&gt;<br /> When true, the crosshair's color reflects your current health. Green is healthy, red is near death, and intermediate colors are somewhere in between. Set this to false, if you want the crosshair to have a constant color (specified by the crosshaircolor cvar) instead.<br /> <br /> ===crosshairscale===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want the crosshair to always appear the same size at all resolutions. Leaving it at false causes the crosshair to be drawn normally.<br /> <br /> ===gamma===<br /> float: 1.0&lt;br&gt;<br /> Controls the amount of gamma correction applied to the display. 1.0 is equivalent to no correction, while larger numbers translate into a brighter display, and smaller numbers translate into a darker display. 0.0 is invalid and will be rejected. Negative numbers are technically invalid but will be accepted solely for the novelty value doing so provides. <br /> <br /> ===hud_scale===<br /> boolean: false&lt;br&gt;<br /> Controls scaling of the fullscreen hud. At resolutions of 640x400 or above, setting this cvar to true will cause the icons to be scaled to approximately the same size they would be at 320x200. If this cvar is false, the icons will always be drawn without any scaling. <br /> <br /> ===msg===<br /> integer: 0&lt;br&gt;<br /> This is the minimum message level that you will see. You will not see any messages with a lower priority than this. The different message levels are: <br /> <br /> #Item pickup <br /> #Obituaries <br /> #Critical messages <br /> #Chat messages <br /> #Chat messages from a teammate <br /> <br /> ===msg0color====<br /> integer: 6&lt;br&gt;<br /> This cvar controls the color used to display level 0 (item pickup) messages. Available colors are: <br /> <br /> #Brick <br /> #Tan <br /> #Gray <br /> #Green <br /> #Brown <br /> #Gold <br /> #Red <br /> #Blue <br /> #Orange <br /> #White <br /> #Yellow <br /> <br /> ===msg1color===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display level 1 (obituary) messages. Available colors are the same as for&quot; msg0color. <br /> <br /> ===msg2color===<br /> integer: 2&lt;br&gt;<br /> This cvar selects the color used to display level 2 (critical) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg3color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 3 (chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msg4color===<br /> integer: 3&lt;br&gt;<br /> This cvar selects the color used to display level 4 (team chat) messages. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor===<br /> integer: 5&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen. Available colors are the same as for msg0color. <br /> <br /> ===msgmidcolor2===<br /> integer: 4&lt;br&gt;<br /> This cvar selects the color used to display messages in the middle of the screen that are sent to everyone. Available colors are the same as for msg0color. <br /> <br /> ===st_scale===<br /> boolean: false&lt;br&gt;<br /> When this cvar is true, the status bar will be scaled so that it covers the entire width of the screen in higher resolutions. At low resolutions this may look ugly, but at high resolutions it should look good enough.<br /> <br /> ==Renderer==<br /> * [[Renderer]]<br /> <br /> ==Video==<br /> * [[Video]]<br /> <br /> ==Bots==<br /> * [[Bots]]<br /> <br /> ==Automap==<br /> * [[AutoMap]]<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=425 2004-01-05T11:40:07Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, ect...<br /> <br /> you access the console by pressing &quot;~&quot; at any time<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. <br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward&lt;br&gt;<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;&lt;br&gt;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key—ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> <br /> ===addkeysection (menu-heading) (ini-section-name)&lt;br&gt;===<br /> This command does two things. First, it adds a new heading called menu-heading to the controls menu. You can use the addmenukey command to add your own custom keys beneath this heading. Second, it loads all the bindings from the corresponding ini-section-name section in zdoom.ini. You can use this command multiple times to create different sections in the menu and ini for different sets of commands. If you use a menu-heading that was already added to the menu, new controls added with addmenukey will appear at the end of that section, but the bindings will not be reloaded from the ini. <br /> <br /> ===addmenukey (description) (command)&lt;br&gt;===<br /> Adds a new control to the controls menu. Description is the name of this control in the menu, and command is a console command or alias to be executed when the control is pressed. New controls are added to the last section specified with addkeysection.<br /> <br /> ===addslot (slot) (weapon)===<br /> Adds a single weapon to the list of weapons in a weapon slot.<br /> <br /> ===alias (new-command) [command-string]===<br /> If specified with no parameters, will display a list of all current aliases. If only new-command is specified, it will be removed from the list of aliases. If command-string is also specified, it will be added to the list of aliases as new-command. For example, to create a new command to kill the monsters on the level, you can use the command: <br /> alias massacre &quot;kill monsters&quot;Then you can use the newly created massacre command to kill all the monsters on the level.<br /> <br /> ===archivecvar (cvar)===<br /> When you create a custom cvar with the set command, it will not normally be saved in the ini. You can use archivecvar after creating the cvar to indicate that the custom cvar's value should persist even after you quit.<br /> <br /> ===atexit [command]===<br /> If you specify a command, it will be added to a list of console commands to execute when the user quits the game. Commands are executed in the reverse order that they were added in. If you do not specify any arguments to atexit, then it will list the current set of commands that will execute when you quit.<br /> <br /> ===bind (key [command string])===<br /> If no parameters are specified, the entire list of bound keys will be printed to the console. If only [key] is specified, the binding for that specific key will be printed. If both [key] and [command string] are specified, [command string] will be bound to [key]. <br /> <br /> ===binddefaults===<br /> Binds all keys to their default commands. This will not unbind any keys that do not have any default bindings, so if you want to properly restore the default controls, you need to use unbindall first. <br /> defaultbind key command<br /> Binds command to the key if and only if key is not already bound and there are no keys already bound to command.<br /> <br /> ===doublebind (key [command string])===<br /> This command works just like bind, except it controls the action that occurs when a key is double-clicked. If a key does not have a doublebinding, then double-clicking it has the same result as pressing it twice. Otherwise, the first press will execute the normal command set with bind, and the second press of the double-click will execute the command set with doublebind. <br /> <br /> ===eval expression [variable]===<br /> Evaluates a mathematical expression and either prints it to the console or stores it in variable. Expressions are written using prefix notation instead of the more common infix notation. Basically, you first specify what you want to do (the operator) and then what you want to do it to (the operands). You must separate operators and operands with spaces. <br /> <br /> Examples: <br /> To compute 2+2: <br /> eval + 2 2To compute 5-3: <br /> eval - 5 3To compute 2+(5*6): <br /> eval + 2 * 5 6To decrease the number of screenblocks: <br /> eval - $screenblocks 1 screenblocksThe supported operators are:<br /> + a b Adds a and b. <br /> - a b Subtracts b from a. <br /> * a b Multiplies a and b. <br /> / a b Divides a by b. <br /> % a b Calculates the remainder of a/b. <br /> ^ a b Raises a to the b-th power . <br /> &lt; a b Produces 1 if a is less than b and 0 if not. <br /> &lt;= a b Produces 1 if a is less than or equal to b and 0 if not. <br /> &gt; a b Produces 1 if a is greater than b and 0 if not. <br /> &gt;= a b Produces 1 if a is greater than or equal to b and 0 if not. <br /> = a b Produces 1 if a is equal to b and 0 if not. <br /> == a b Produces 1 if a is equal to b and 0 if not. <br /> != a b Produces 1 if a is not equal to b and 0 if it is. <br /> &lt;&gt; a b Produces 1 if a is not equal to b and 0 if is. <br /> xor a b Calculates the bit-wise exclusive-or of a and b. <br /> &amp; a b Calculates the bit-wise and of a and b. <br /> | a b Calculates the bit-wise or of a and b. <br /> &amp;&amp; a b Calculates the logical and of a and b. <br /> || a b Calculates the logical or of a and b. <br /> <br /> ===exec (script-file)===<br /> Executes a series of commands stored in the script-file as if they had been typed in at the console directly. <br /> <br /> ===key value1 [value2]===<br /> Translates all parameters to the command into their corresponding key values which are used internally for command and alias lookup. Probably not very useful for the average user. <br /> <br /> ===puke (script [arguments])===<br /> Executes an ACS script on the current map, optionally passing it up to three numerical arguments. <br /> <br /> ===pullin (wadfile)===<br /> Loads a wadfile at startup. This command is only valid inside .cfg files that have been execed at startup.<br /> <br /> ===set (cvar) (value)===<br /> Sets cvar to value. If cvar does not exist, it will be created. <br /> <br /> ===rebind (binding)===<br /> Changes the binding for the key that caused the rebind command to execute. For obvious reasons, this command cannot be used at the console.<br /> <br /> Example: <br /> <br /> bind b &quot;echo setting 1; rebind \&quot;echo setting 2\&quot;&quot;<br /> <br /> This will cause the first press of b to echo &quot;setting 1&quot; to the console. All future presses of b will echo &quot;setting 2&quot; instead. <br /> <br /> ===unbind (key)===<br /> Removes a binding from the specified key.<br /> <br /> ===unbindall===<br /> Removes all bindings and doublebindings from every key. To restore the default bindings, you can use the binddefaults command. There is no way to restore any custom bindings after issuing this command except by retyping each bind command or using the controls setup menu.<br /> <br /> ===undoublebind (key)===<br /> Removes a doublebinding from the specified key.<br /> <br /> ===unset (cvar)===<br /> Undefines a user-created cvar.<br /> <br /> ==Screenshots==<br /> <br /> ===png_gamma===<br /> float: 0&lt;br&gt;<br /> Controls the gamma level stored in PNG screenshots. If this is 0, then your current gamma setting will be used.<br /> <br /> ===png_level===<br /> integer: 5&lt;br&gt;<br /> This is the level of compression to use for PNG screenshots. 0 is no compression at all, 1 is minimal compression (fastest), 9 is maximum compression (slowest), and intermediate values offer intermediate compression. 5 is offers a decent trade-of between file size and compression time. An uncompressed image will not neccessarily save faster than a compressed image, because the extra time needed to write out a complete uncompressed image may be longer than the time required to compress the image. If you need to create screenshots as quickly as possible, consider setting screenshot_type to &quot;pcx&quot;. <br /> <br /> ===screenshot [file]===<br /> Dumps a copy of the screen to disk as a PNG or PCX file. If file is not specified, the screenshot will be saved to the directory the game was run from with a name of the form doom????.png. <br /> <br /> ===screenshot_quiet===<br /> boolean: false&lt;br&gt;<br /> Setting this to true will suppress the messages informing you what file a screenshot was saved to.<br /> <br /> ===screenshot_type===<br /> string: &quot;png&quot;&lt;br&gt;<br /> Determines the type of screenshots that will be saved. This can be either &quot;png&quot; or &quot;pcx&quot;. In my empirical studies, PNG screenshots are about half the size of pcx screenshots. PCX screenshots have the advantage that they require less time to create so are most useful for rapid screenshot generation. The following sequence of console commands will take a screenshot every frame. You can use an external program to assemble these into a video, if desired. <br /> <br /> screenshot_type &quot;png&quot;&lt;br&gt;<br /> screenshot_quiet true&lt;br&gt;<br /> alias autoshot &quot;screenshot; wait 1; autoshot&quot;&lt;br&gt;<br /> autoshot&lt;br&gt;<br /> <br /> If you use the autoshot alias, the command alias autoshot will stop automatic screenshot taking before you hit 10000 screenshots (approximately 4 minutes, 45 seconds).<br /> <br /> ===storesavepic===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will produce smaller savegames (by about 14k typically) by not storing a screenshot inside the savegame.<br /> <br /> ==Chatting==<br /> <br /> ===chat_substitution===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want to chat using special keywords that will be replaced with appropriate text when your messages are sent. The supported keywords are:<br /> <br /> $health &lt;br&gt;<br /> Replaced by your current health. &lt;br&gt;<br /> $weapon &lt;br&gt;<br /> Replaced by the name of your current weapon. &lt;br&gt;<br /> $armor &lt;br&gt;<br /> Replaced by your current armor count. &lt;br&gt;<br /> $ammocount &lt;br&gt;<br /> Replaced by your current ammo count. &lt;br&gt;<br /> $ammo &lt;br&gt;<br /> Replaced by the name of your current ammo.<br /> <br /> As an example, if you just started a new game of Doom and have chat substitution turned on, when you send the message &quot;My health is $health, and I am using a $weapon&quot;, the message that is actually sent will be &quot;My health is 100, and I am using a Pistol&quot;.<br /> <br /> chatmacro0&lt;br&gt;<br /> chatmacro1&lt;br&gt;<br /> chatmacro2&lt;br&gt;<br /> chatmacro3&lt;br&gt;<br /> chatmacro4&lt;br&gt;<br /> chatmacro5&lt;br&gt;<br /> chatmacro6&lt;br&gt;<br /> chatmacro7&lt;br&gt;<br /> chatmacro8&lt;br&gt;<br /> chatmacro9&lt;br&gt;<br /> string&lt;br&gt;<br /> These are all strings that can be assigned to hotkeys in chat mode. To use these, enter chat mode and then hold down Alt and press one of the number keys. The string stored in the corresponding chatmacro cvar will be sent as if you had typed it yourself. <br /> <br /> ===messagemode===<br /> Enters message entry mode. Anything typed while in this mode will be sent to everyone else as if you had used the say command once you press enter. <br /> <br /> ===messagemode2===<br /> This is just like messagemode except that the message is only sent to other members of your team. If teamplay is false or you don't have a team, then this command will work just like messagemode and send the message to everyone. <br /> <br /> ===say (message)===<br /> Sends a message to everyone playing. If your message begins with &quot;/me&quot; then &quot;/me&quot; will be replaced by your name ala IRC. <br /> <br /> ===say_team (message)===<br /> This is just like say except it only sends a message to your teammates. If teamplay is inactive, then this command will act exactly like say and send the message to everyone.<br /> <br /> ==Cheating==<br /> <br /> ===sv_cheats===<br /> boolean: false<br /> When true, cheats will be allowed in Nightmare difficulty and network games. For purposes of fairness, this cvar can only be set from the command line when you run ZDoom. This is to avoid situations where the key player in a multiplayer game (player 1) could go to the console and type something like this:<br /> <br /> sv_cheats 1&lt;br&gt;<br /> god&lt;br&gt;<br /> sv_cheats 0&lt;br&gt;<br /> <br /> whereby rendering himself immune to the attacks of others.<br /> <br /> ===anubis===<br /> Toggles monster fear on and off. Scared monsters will run away from you and attack less frequently.<br /> <br /> ===fly===<br /> Toggles fly mode on and off.<br /> <br /> ===give (item)===<br /> Gives an item to the player. Give understands the following special items: <br /> all - gives you everything <br /> health - gives you full health <br /> weapons - gives you every weapon <br /> ammo - gives you full ammo <br /> armor - gives you full armor <br /> keys - gives you every key <br /> It also understands the names of individual inventory items. Use the command dumpclasses inventory for a complete list of these. <br /> <br /> ===god===<br /> Toggles God (Degreelessness) mode on/off. While active, you cannot be hurt by normal attacks (although telefragging will still kill you). Also known as iddqd. <br /> <br /> ===iddqd===<br /> The same as god, except it also gives you 100 health.<br /> <br /> ===kill [monsters]===<br /> If used as &quot;kill monsters&quot;, will kill all monsters on the level. Otherwise, it will kill you instead. This command is broken in netgames, so don't use it unless you are playing a single player game. <br /> <br /> ===logfile [log-file]===<br /> If log-file is not specified, console logging will be stopped (if active). Otherwise, a file named log-file will be created on disk, and all console output will be recorded in it as well as on the screen. <br /> <br /> ===mdk===<br /> This cheat will kill whatever you are looking at.<br /> <br /> ===morphme===<br /> Transforms you into a chicken in Heretic and a pig in Hexen and Doom (The latter only happens if you have the releven graphics present).<br /> <br /> ===noclip===<br /> Toggles noclipping mode on/off. <br /> <br /> ===notarget===<br /> Toggles notarget mode on/off. While active, monsters will not target you unless you hurt them first. <br /> <br /> ===powerup===<br /> Powers you up in Heretic as if you had used a Tome of Power.<br /> <br /> ===turbo===<br /> float: 100&lt;br&gt;<br /> This cvar affects how quickly the player moves. A value of 100 will cause the player to move at normal speed, 200 will cause the player to move at 200% of normal speed, 50 will cause the player to move at 50% of normal speed, etc. Valid values range from 10 to 256.<br /> <br /> ==Display==<br /> * [[Display]]<br /> <br /> ==Renderer==<br /> * [[Renderer]]<br /> <br /> ==Video==<br /> * [[Video]]<br /> <br /> ==Bots==<br /> * [[Bots]]<br /> <br /> ==Automap==<br /> * [[AutoMap]]<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=424 2004-01-05T11:37:53Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, ect...<br /> <br /> you access the console by pressing &quot;~&quot; at any time<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. <br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward&lt;br&gt;<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;&lt;br&gt;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key—ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> <br /> ===addkeysection (menu-heading) (ini-section-name)&lt;br&gt;===<br /> This command does two things. First, it adds a new heading called menu-heading to the controls menu. You can use the addmenukey command to add your own custom keys beneath this heading. Second, it loads all the bindings from the corresponding ini-section-name section in zdoom.ini. You can use this command multiple times to create different sections in the menu and ini for different sets of commands. If you use a menu-heading that was already added to the menu, new controls added with addmenukey will appear at the end of that section, but the bindings will not be reloaded from the ini. <br /> <br /> ===addmenukey (description) (command)&lt;br&gt;===<br /> Adds a new control to the controls menu. Description is the name of this control in the menu, and command is a console command or alias to be executed when the control is pressed. New controls are added to the last section specified with addkeysection.<br /> <br /> ===addslot (slot) (weapon)===<br /> Adds a single weapon to the list of weapons in a weapon slot.<br /> <br /> ===alias (new-command) [command-string]===<br /> If specified with no parameters, will display a list of all current aliases. If only new-command is specified, it will be removed from the list of aliases. If command-string is also specified, it will be added to the list of aliases as new-command. For example, to create a new command to kill the monsters on the level, you can use the command: <br /> alias massacre &quot;kill monsters&quot;Then you can use the newly created massacre command to kill all the monsters on the level.<br /> <br /> ===archivecvar (cvar)===<br /> When you create a custom cvar with the set command, it will not normally be saved in the ini. You can use archivecvar after creating the cvar to indicate that the custom cvar's value should persist even after you quit.<br /> <br /> ===atexit [command]===<br /> If you specify a command, it will be added to a list of console commands to execute when the user quits the game. Commands are executed in the reverse order that they were added in. If you do not specify any arguments to atexit, then it will list the current set of commands that will execute when you quit.<br /> <br /> ===bind (key [command string])===<br /> If no parameters are specified, the entire list of bound keys will be printed to the console. If only [key] is specified, the binding for that specific key will be printed. If both [key] and [command string] are specified, [command string] will be bound to [key]. <br /> <br /> ===binddefaults===<br /> Binds all keys to their default commands. This will not unbind any keys that do not have any default bindings, so if you want to properly restore the default controls, you need to use unbindall first. <br /> defaultbind key command<br /> Binds command to the key if and only if key is not already bound and there are no keys already bound to command.<br /> <br /> ===doublebind (key [command string])===<br /> This command works just like bind, except it controls the action that occurs when a key is double-clicked. If a key does not have a doublebinding, then double-clicking it has the same result as pressing it twice. Otherwise, the first press will execute the normal command set with bind, and the second press of the double-click will execute the command set with doublebind. <br /> <br /> ===eval expression [variable]===<br /> Evaluates a mathematical expression and either prints it to the console or stores it in variable. Expressions are written using prefix notation instead of the more common infix notation. Basically, you first specify what you want to do (the operator) and then what you want to do it to (the operands). You must separate operators and operands with spaces. <br /> <br /> Examples: <br /> To compute 2+2: <br /> eval + 2 2To compute 5-3: <br /> eval - 5 3To compute 2+(5*6): <br /> eval + 2 * 5 6To decrease the number of screenblocks: <br /> eval - $screenblocks 1 screenblocksThe supported operators are:<br /> + a b Adds a and b. <br /> - a b Subtracts b from a. <br /> * a b Multiplies a and b. <br /> / a b Divides a by b. <br /> % a b Calculates the remainder of a/b. <br /> ^ a b Raises a to the b-th power . <br /> &lt; a b Produces 1 if a is less than b and 0 if not. <br /> &lt;= a b Produces 1 if a is less than or equal to b and 0 if not. <br /> &gt; a b Produces 1 if a is greater than b and 0 if not. <br /> &gt;= a b Produces 1 if a is greater than or equal to b and 0 if not. <br /> = a b Produces 1 if a is equal to b and 0 if not. <br /> == a b Produces 1 if a is equal to b and 0 if not. <br /> != a b Produces 1 if a is not equal to b and 0 if it is. <br /> &lt;&gt; a b Produces 1 if a is not equal to b and 0 if is. <br /> xor a b Calculates the bit-wise exclusive-or of a and b. <br /> &amp; a b Calculates the bit-wise and of a and b. <br /> | a b Calculates the bit-wise or of a and b. <br /> &amp;&amp; a b Calculates the logical and of a and b. <br /> || a b Calculates the logical or of a and b. <br /> <br /> ===exec (script-file)===<br /> Executes a series of commands stored in the script-file as if they had been typed in at the console directly. <br /> <br /> ===key value1 [value2]===<br /> Translates all parameters to the command into their corresponding key values which are used internally for command and alias lookup. Probably not very useful for the average user. <br /> <br /> ===puke (script [arguments])===<br /> Executes an ACS script on the current map, optionally passing it up to three numerical arguments. <br /> <br /> ===pullin (wadfile)===<br /> Loads a wadfile at startup. This command is only valid inside .cfg files that have been execed at startup.<br /> <br /> ===set (cvar) (value)===<br /> Sets cvar to value. If cvar does not exist, it will be created. <br /> <br /> ===rebind (binding)===<br /> Changes the binding for the key that caused the rebind command to execute. For obvious reasons, this command cannot be used at the console.<br /> <br /> Example: <br /> <br /> bind b &quot;echo setting 1; rebind \&quot;echo setting 2\&quot;&quot;<br /> <br /> This will cause the first press of b to echo &quot;setting 1&quot; to the console. All future presses of b will echo &quot;setting 2&quot; instead. <br /> <br /> ===unbind (key)===<br /> Removes a binding from the specified key.<br /> <br /> ===unbindall===<br /> Removes all bindings and doublebindings from every key. To restore the default bindings, you can use the binddefaults command. There is no way to restore any custom bindings after issuing this command except by retyping each bind command or using the controls setup menu.<br /> <br /> ===undoublebind (key)===<br /> Removes a doublebinding from the specified key.<br /> <br /> ===unset (cvar)===<br /> Undefines a user-created cvar.<br /> <br /> ==Screenshots==<br /> <br /> ===png_gamma===<br /> float: 0&lt;br&gt;<br /> Controls the gamma level stored in PNG screenshots. If this is 0, then your current gamma setting will be used.<br /> <br /> ===png_level===<br /> integer: 5&lt;br&gt;<br /> This is the level of compression to use for PNG screenshots. 0 is no compression at all, 1 is minimal compression (fastest), 9 is maximum compression (slowest), and intermediate values offer intermediate compression. 5 is offers a decent trade-of between file size and compression time. An uncompressed image will not neccessarily save faster than a compressed image, because the extra time needed to write out a complete uncompressed image may be longer than the time required to compress the image. If you need to create screenshots as quickly as possible, consider setting screenshot_type to &quot;pcx&quot;. <br /> <br /> ===screenshot [file]===<br /> Dumps a copy of the screen to disk as a PNG or PCX file. If file is not specified, the screenshot will be saved to the directory the game was run from with a name of the form doom????.png. <br /> <br /> ===screenshot_quiet===<br /> boolean: false&lt;br&gt;<br /> Setting this to true will suppress the messages informing you what file a screenshot was saved to.<br /> <br /> ===screenshot_type===<br /> string: &quot;png&quot;&lt;br&gt;<br /> Determines the type of screenshots that will be saved. This can be either &quot;png&quot; or &quot;pcx&quot;. In my empirical studies, PNG screenshots are about half the size of pcx screenshots. PCX screenshots have the advantage that they require less time to create so are most useful for rapid screenshot generation. The following sequence of console commands will take a screenshot every frame. You can use an external program to assemble these into a video, if desired. <br /> <br /> screenshot_type &quot;png&quot;&lt;br&gt;<br /> screenshot_quiet true&lt;br&gt;<br /> alias autoshot &quot;screenshot; wait 1; autoshot&quot;&lt;br&gt;<br /> autoshot&lt;br&gt;<br /> <br /> If you use the autoshot alias, the command alias autoshot will stop automatic screenshot taking before you hit 10000 screenshots (approximately 4 minutes, 45 seconds).<br /> <br /> ===storesavepic===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will produce smaller savegames (by about 14k typically) by not storing a screenshot inside the savegame.<br /> <br /> ==Chatting==<br /> <br /> ===chat_substitution===<br /> boolean: false&lt;br&gt;<br /> Set this to true if you want to chat using special keywords that will be replaced with appropriate text when your messages are sent. The supported keywords are:<br /> <br /> $health &lt;br&gt;<br /> Replaced by your current health. &lt;br&gt;<br /> $weapon &lt;br&gt;<br /> Replaced by the name of your current weapon. &lt;br&gt;<br /> $armor &lt;br&gt;<br /> Replaced by your current armor count. &lt;br&gt;<br /> $ammocount &lt;br&gt;<br /> Replaced by your current ammo count. &lt;br&gt;<br /> $ammo &lt;br&gt;<br /> Replaced by the name of your current ammo.<br /> <br /> As an example, if you just started a new game of Doom and have chat substitution turned on, when you send the message &quot;My health is $health, and I am using a $weapon&quot;, the message that is actually sent will be &quot;My health is 100, and I am using a Pistol&quot;.<br /> <br /> chatmacro0&lt;br&gt;<br /> chatmacro1&lt;br&gt;<br /> chatmacro2&lt;br&gt;<br /> chatmacro3&lt;br&gt;<br /> chatmacro4&lt;br&gt;<br /> chatmacro5&lt;br&gt;<br /> chatmacro6&lt;br&gt;<br /> chatmacro7&lt;br&gt;<br /> chatmacro8&lt;br&gt;<br /> chatmacro9&lt;br&gt;<br /> string&lt;br&gt;<br /> These are all strings that can be assigned to hotkeys in chat mode. To use these, enter chat mode and then hold down Alt and press one of the number keys. The string stored in the corresponding chatmacro cvar will be sent as if you had typed it yourself. <br /> <br /> ===messagemode===<br /> Enters message entry mode. Anything typed while in this mode will be sent to everyone else as if you had used the say command once you press enter. <br /> <br /> ===messagemode2===<br /> This is just like messagemode except that the message is only sent to other members of your team. If teamplay is false or you don't have a team, then this command will work just like messagemode and send the message to everyone. <br /> <br /> ===say (message)===<br /> Sends a message to everyone playing. If your message begins with &quot;/me&quot; then &quot;/me&quot; will be replaced by your name ala IRC. <br /> <br /> ===say_team (message)===<br /> This is just like say except it only sends a message to your teammates. If teamplay is inactive, then this command will act exactly like say and send the message to everyone.<br /> <br /> ==Cheating==<br /> * [[Cheating]]<br /> <br /> ==Display==<br /> * [[Display]]<br /> <br /> ==Renderer==<br /> * [[Renderer]]<br /> <br /> ==Video==<br /> * [[Video]]<br /> <br /> ==Bots==<br /> * [[Bots]]<br /> <br /> ==Automap==<br /> * [[AutoMap]]<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=423 2004-01-05T11:36:28Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, ect...<br /> <br /> you access the console by pressing &quot;~&quot; at any time<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. <br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward&lt;br&gt;<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;&lt;br&gt;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key—ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> <br /> ===addkeysection (menu-heading) (ini-section-name)&lt;br&gt;===<br /> This command does two things. First, it adds a new heading called menu-heading to the controls menu. You can use the addmenukey command to add your own custom keys beneath this heading. Second, it loads all the bindings from the corresponding ini-section-name section in zdoom.ini. You can use this command multiple times to create different sections in the menu and ini for different sets of commands. If you use a menu-heading that was already added to the menu, new controls added with addmenukey will appear at the end of that section, but the bindings will not be reloaded from the ini. <br /> <br /> ===addmenukey (description) (command)&lt;br&gt;===<br /> Adds a new control to the controls menu. Description is the name of this control in the menu, and command is a console command or alias to be executed when the control is pressed. New controls are added to the last section specified with addkeysection.<br /> <br /> ===addslot (slot) (weapon)===<br /> Adds a single weapon to the list of weapons in a weapon slot.<br /> <br /> ===alias (new-command) [command-string]===<br /> If specified with no parameters, will display a list of all current aliases. If only new-command is specified, it will be removed from the list of aliases. If command-string is also specified, it will be added to the list of aliases as new-command. For example, to create a new command to kill the monsters on the level, you can use the command: <br /> alias massacre &quot;kill monsters&quot;Then you can use the newly created massacre command to kill all the monsters on the level.<br /> <br /> ===archivecvar (cvar)===<br /> When you create a custom cvar with the set command, it will not normally be saved in the ini. You can use archivecvar after creating the cvar to indicate that the custom cvar's value should persist even after you quit.<br /> <br /> ===atexit [command]===<br /> If you specify a command, it will be added to a list of console commands to execute when the user quits the game. Commands are executed in the reverse order that they were added in. If you do not specify any arguments to atexit, then it will list the current set of commands that will execute when you quit.<br /> <br /> ===bind (key [command string])===<br /> If no parameters are specified, the entire list of bound keys will be printed to the console. If only [key] is specified, the binding for that specific key will be printed. If both [key] and [command string] are specified, [command string] will be bound to [key]. <br /> <br /> ===binddefaults===<br /> Binds all keys to their default commands. This will not unbind any keys that do not have any default bindings, so if you want to properly restore the default controls, you need to use unbindall first. <br /> defaultbind key command<br /> Binds command to the key if and only if key is not already bound and there are no keys already bound to command.<br /> <br /> ===doublebind (key [command string])===<br /> This command works just like bind, except it controls the action that occurs when a key is double-clicked. If a key does not have a doublebinding, then double-clicking it has the same result as pressing it twice. Otherwise, the first press will execute the normal command set with bind, and the second press of the double-click will execute the command set with doublebind. <br /> <br /> ===eval expression [variable]===<br /> Evaluates a mathematical expression and either prints it to the console or stores it in variable. Expressions are written using prefix notation instead of the more common infix notation. Basically, you first specify what you want to do (the operator) and then what you want to do it to (the operands). You must separate operators and operands with spaces. <br /> <br /> Examples: <br /> To compute 2+2: <br /> eval + 2 2To compute 5-3: <br /> eval - 5 3To compute 2+(5*6): <br /> eval + 2 * 5 6To decrease the number of screenblocks: <br /> eval - $screenblocks 1 screenblocksThe supported operators are:<br /> + a b Adds a and b. <br /> - a b Subtracts b from a. <br /> * a b Multiplies a and b. <br /> / a b Divides a by b. <br /> % a b Calculates the remainder of a/b. <br /> ^ a b Raises a to the b-th power . <br /> &lt; a b Produces 1 if a is less than b and 0 if not. <br /> &lt;= a b Produces 1 if a is less than or equal to b and 0 if not. <br /> &gt; a b Produces 1 if a is greater than b and 0 if not. <br /> &gt;= a b Produces 1 if a is greater than or equal to b and 0 if not. <br /> = a b Produces 1 if a is equal to b and 0 if not. <br /> == a b Produces 1 if a is equal to b and 0 if not. <br /> != a b Produces 1 if a is not equal to b and 0 if it is. <br /> &lt;&gt; a b Produces 1 if a is not equal to b and 0 if is. <br /> xor a b Calculates the bit-wise exclusive-or of a and b. <br /> &amp; a b Calculates the bit-wise and of a and b. <br /> | a b Calculates the bit-wise or of a and b. <br /> &amp;&amp; a b Calculates the logical and of a and b. <br /> || a b Calculates the logical or of a and b. <br /> <br /> ===exec (script-file)===<br /> Executes a series of commands stored in the script-file as if they had been typed in at the console directly. <br /> <br /> ===key value1 [value2]===<br /> Translates all parameters to the command into their corresponding key values which are used internally for command and alias lookup. Probably not very useful for the average user. <br /> <br /> ===puke (script [arguments])===<br /> Executes an ACS script on the current map, optionally passing it up to three numerical arguments. <br /> <br /> ===pullin (wadfile)===<br /> Loads a wadfile at startup. This command is only valid inside .cfg files that have been execed at startup.<br /> <br /> ===set (cvar) (value)===<br /> Sets cvar to value. If cvar does not exist, it will be created. <br /> <br /> ===rebind (binding)===<br /> Changes the binding for the key that caused the rebind command to execute. For obvious reasons, this command cannot be used at the console.<br /> <br /> Example: <br /> <br /> bind b &quot;echo setting 1; rebind \&quot;echo setting 2\&quot;&quot;<br /> <br /> This will cause the first press of b to echo &quot;setting 1&quot; to the console. All future presses of b will echo &quot;setting 2&quot; instead. <br /> <br /> ===unbind (key)===<br /> Removes a binding from the specified key.<br /> <br /> ===unbindall===<br /> Removes all bindings and doublebindings from every key. To restore the default bindings, you can use the binddefaults command. There is no way to restore any custom bindings after issuing this command except by retyping each bind command or using the controls setup menu.<br /> <br /> ===undoublebind (key)===<br /> Removes a doublebinding from the specified key.<br /> <br /> ===unset (cvar)===<br /> Undefines a user-created cvar.<br /> <br /> ==Screenshots==<br /> <br /> ===png_gamma===<br /> float: 0&lt;br&gt;<br /> Controls the gamma level stored in PNG screenshots. If this is 0, then your current gamma setting will be used.<br /> <br /> ===png_level===<br /> integer: 5&lt;br&gt;<br /> This is the level of compression to use for PNG screenshots. 0 is no compression at all, 1 is minimal compression (fastest), 9 is maximum compression (slowest), and intermediate values offer intermediate compression. 5 is offers a decent trade-of between file size and compression time. An uncompressed image will not neccessarily save faster than a compressed image, because the extra time needed to write out a complete uncompressed image may be longer than the time required to compress the image. If you need to create screenshots as quickly as possible, consider setting screenshot_type to &quot;pcx&quot;. <br /> <br /> ===screenshot [file]===<br /> Dumps a copy of the screen to disk as a PNG or PCX file. If file is not specified, the screenshot will be saved to the directory the game was run from with a name of the form doom????.png. <br /> <br /> ===screenshot_quiet===<br /> boolean: false&lt;br&gt;<br /> Setting this to true will suppress the messages informing you what file a screenshot was saved to.<br /> <br /> ===screenshot_type===<br /> string: &quot;png&quot;&lt;br&gt;<br /> Determines the type of screenshots that will be saved. This can be either &quot;png&quot; or &quot;pcx&quot;. In my empirical studies, PNG screenshots are about half the size of pcx screenshots. PCX screenshots have the advantage that they require less time to create so are most useful for rapid screenshot generation. The following sequence of console commands will take a screenshot every frame. You can use an external program to assemble these into a video, if desired. <br /> <br /> screenshot_type &quot;png&quot;&lt;br&gt;<br /> screenshot_quiet true&lt;br&gt;<br /> alias autoshot &quot;screenshot; wait 1; autoshot&quot;&lt;br&gt;<br /> autoshot&lt;br&gt;<br /> <br /> If you use the autoshot alias, the command alias autoshot will stop automatic screenshot taking before you hit 10000 screenshots (approximately 4 minutes, 45 seconds).<br /> <br /> ===storesavepic===<br /> boolean: true&lt;br&gt;<br /> Setting this to false will produce smaller savegames (by about 14k typically) by not storing a screenshot inside the savegame.<br /> <br /> ==Chatting==<br /> * [[Chatting]]<br /> <br /> ==Cheating==<br /> * [[Cheating]]<br /> <br /> ==Display==<br /> * [[Display]]<br /> <br /> ==Renderer==<br /> * [[Renderer]]<br /> <br /> ==Video==<br /> * [[Video]]<br /> <br /> ==Bots==<br /> * [[Bots]]<br /> <br /> ==Automap==<br /> * [[AutoMap]]<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=422 2004-01-05T11:34:51Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, ect...<br /> <br /> you access the console by pressing &quot;~&quot; at any time<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. <br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward&lt;br&gt;<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;&lt;br&gt;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key—ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> <br /> ===addkeysection (menu-heading) (ini-section-name)&lt;br&gt;===<br /> This command does two things. First, it adds a new heading called menu-heading to the controls menu. You can use the addmenukey command to add your own custom keys beneath this heading. Second, it loads all the bindings from the corresponding ini-section-name section in zdoom.ini. You can use this command multiple times to create different sections in the menu and ini for different sets of commands. If you use a menu-heading that was already added to the menu, new controls added with addmenukey will appear at the end of that section, but the bindings will not be reloaded from the ini. <br /> <br /> ===addmenukey (description) (command)&lt;br&gt;===<br /> Adds a new control to the controls menu. Description is the name of this control in the menu, and command is a console command or alias to be executed when the control is pressed. New controls are added to the last section specified with addkeysection.<br /> <br /> ===addslot (slot) (weapon)===<br /> Adds a single weapon to the list of weapons in a weapon slot.<br /> <br /> ===alias (new-command) [command-string]===<br /> If specified with no parameters, will display a list of all current aliases. If only new-command is specified, it will be removed from the list of aliases. If command-string is also specified, it will be added to the list of aliases as new-command. For example, to create a new command to kill the monsters on the level, you can use the command: <br /> alias massacre &quot;kill monsters&quot;Then you can use the newly created massacre command to kill all the monsters on the level.<br /> <br /> ===archivecvar (cvar)===<br /> When you create a custom cvar with the set command, it will not normally be saved in the ini. You can use archivecvar after creating the cvar to indicate that the custom cvar's value should persist even after you quit.<br /> <br /> ===atexit [command]===<br /> If you specify a command, it will be added to a list of console commands to execute when the user quits the game. Commands are executed in the reverse order that they were added in. If you do not specify any arguments to atexit, then it will list the current set of commands that will execute when you quit.<br /> <br /> ===bind (key [command string])===<br /> If no parameters are specified, the entire list of bound keys will be printed to the console. If only [key] is specified, the binding for that specific key will be printed. If both [key] and [command string] are specified, [command string] will be bound to [key]. <br /> <br /> ===binddefaults===<br /> Binds all keys to their default commands. This will not unbind any keys that do not have any default bindings, so if you want to properly restore the default controls, you need to use unbindall first. <br /> defaultbind key command<br /> Binds command to the key if and only if key is not already bound and there are no keys already bound to command.<br /> <br /> ===doublebind (key [command string])===<br /> This command works just like bind, except it controls the action that occurs when a key is double-clicked. If a key does not have a doublebinding, then double-clicking it has the same result as pressing it twice. Otherwise, the first press will execute the normal command set with bind, and the second press of the double-click will execute the command set with doublebind. <br /> <br /> ===eval expression [variable]===<br /> Evaluates a mathematical expression and either prints it to the console or stores it in variable. Expressions are written using prefix notation instead of the more common infix notation. Basically, you first specify what you want to do (the operator) and then what you want to do it to (the operands). You must separate operators and operands with spaces. <br /> <br /> Examples: <br /> To compute 2+2: <br /> eval + 2 2To compute 5-3: <br /> eval - 5 3To compute 2+(5*6): <br /> eval + 2 * 5 6To decrease the number of screenblocks: <br /> eval - $screenblocks 1 screenblocksThe supported operators are:<br /> + a b Adds a and b. <br /> - a b Subtracts b from a. <br /> * a b Multiplies a and b. <br /> / a b Divides a by b. <br /> % a b Calculates the remainder of a/b. <br /> ^ a b Raises a to the b-th power . <br /> &lt; a b Produces 1 if a is less than b and 0 if not. <br /> &lt;= a b Produces 1 if a is less than or equal to b and 0 if not. <br /> &gt; a b Produces 1 if a is greater than b and 0 if not. <br /> &gt;= a b Produces 1 if a is greater than or equal to b and 0 if not. <br /> = a b Produces 1 if a is equal to b and 0 if not. <br /> == a b Produces 1 if a is equal to b and 0 if not. <br /> != a b Produces 1 if a is not equal to b and 0 if it is. <br /> &lt;&gt; a b Produces 1 if a is not equal to b and 0 if is. <br /> xor a b Calculates the bit-wise exclusive-or of a and b. <br /> &amp; a b Calculates the bit-wise and of a and b. <br /> | a b Calculates the bit-wise or of a and b. <br /> &amp;&amp; a b Calculates the logical and of a and b. <br /> || a b Calculates the logical or of a and b. <br /> <br /> ===exec (script-file)===<br /> Executes a series of commands stored in the script-file as if they had been typed in at the console directly. <br /> <br /> ===key value1 [value2]===<br /> Translates all parameters to the command into their corresponding key values which are used internally for command and alias lookup. Probably not very useful for the average user. <br /> <br /> ===puke (script [arguments])===<br /> Executes an ACS script on the current map, optionally passing it up to three numerical arguments. <br /> <br /> ===pullin (wadfile)===<br /> Loads a wadfile at startup. This command is only valid inside .cfg files that have been execed at startup.<br /> <br /> ===set (cvar) (value)===<br /> Sets cvar to value. If cvar does not exist, it will be created. <br /> <br /> ===rebind (binding)===<br /> Changes the binding for the key that caused the rebind command to execute. For obvious reasons, this command cannot be used at the console.<br /> <br /> Example: <br /> <br /> bind b &quot;echo setting 1; rebind \&quot;echo setting 2\&quot;&quot;<br /> <br /> This will cause the first press of b to echo &quot;setting 1&quot; to the console. All future presses of b will echo &quot;setting 2&quot; instead. <br /> <br /> ===unbind (key)===<br /> Removes a binding from the specified key.<br /> <br /> ===unbindall===<br /> Removes all bindings and doublebindings from every key. To restore the default bindings, you can use the binddefaults command. There is no way to restore any custom bindings after issuing this command except by retyping each bind command or using the controls setup menu.<br /> <br /> ===undoublebind (key)===<br /> Removes a doublebinding from the specified key.<br /> <br /> ===unset (cvar)===<br /> Undefines a user-created cvar.<br /> <br /> ==Screenshots==<br /> * [[Screenshots]]<br /> <br /> ==Chatting==<br /> * [[Chatting]]<br /> <br /> ==Cheating==<br /> * [[Cheating]]<br /> <br /> ==Display==<br /> * [[Display]]<br /> <br /> ==Renderer==<br /> * [[Renderer]]<br /> <br /> ==Video==<br /> * [[Video]]<br /> <br /> ==Bots==<br /> * [[Bots]]<br /> <br /> ==Automap==<br /> * [[AutoMap]]<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=421 2004-01-05T11:28:01Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, ect...<br /> <br /> you access the console by pressing &quot;~&quot; at any time<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. <br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward&lt;br&gt;<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;&lt;br&gt;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key—ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> * [[Customization]]<br /> <br /> ==Screenshots==<br /> * [[Screenshots]]<br /> <br /> ==Chatting==<br /> * [[Chatting]]<br /> <br /> ==Cheating==<br /> * [[Cheating]]<br /> <br /> ==Display==<br /> * [[Display]]<br /> <br /> ==Renderer==<br /> * [[Renderer]]<br /> <br /> ==Video==<br /> * [[Video]]<br /> <br /> ==Bots==<br /> * [[Bots]]<br /> <br /> ==Automap==<br /> * [[AutoMap]]<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=420 2004-01-05T11:27:06Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, ect...<br /> <br /> you access the console by pressing &quot;~&quot; at any time<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. <br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> <br /> Button commands are commands that represent buttons and come in pairs. Each &quot;button&quot; has a command prefixed by a + and another corresponding command prefixed by a -. The + version of the command simulates pushing the button, and the - version of the command simulates releasing the button.<br /> <br /> When you bind a command that begins with + to a key, releasing the key will automatically execute the same command with the + replaced by a -. Note that this works for aliases as well as the commands listed here. This provides a useful way to bind multiple actions to a single key. Suppose you want the normal Doom behavior of moving forward and using when you double click the right mouse button. If you use the commands <br /> <br /> bind mouse2 +forward&lt;br&gt;<br /> doublebind mouse2 +use<br /> <br /> ZDoom will move you forward when you press the right mouse button. When you double click it, you will press use, but you will not move forward. To simulate the standard Doom behavior, you can replace the doublebind command with these three commands instead: <br /> <br /> alias +useforward &quot;+use; +forward&quot;&lt;br&gt;<br /> alias -useforward &quot;-use; -forward&quot;<br /> <br /> doublebind mouse2 +useforward<br /> <br /> Now when you double click the right mouse button, the +useforward alias will be executed. Because +useforward's name begins with a + releasing the right mouse button will execute the -useforward alias (whether or not -useforward is defined). <br /> <br /> This behavior of executing a - command when a key is released applies only to the first command or alias bound to the key. If you bind a key to &quot;+forward; +right&quot;, releasing the key will execute the command &quot;-forward; +right&quot; and not &quot;-forward; -right&quot;. As shown above, you can use aliases to get the correct behavior. <br /> <br /> Another trick you can do with aliases is to create a key that only executes the + command without executing the - command. If you wanted a key that will make you move forward when you press it, and will keep you moving forward even after releasing it, you can use an alias like this:<br /> <br /> alias go &quot;+forward&quot;<br /> <br /> Then instead of binding +forward to a key, you bind go to the key instead. This works because go does not begin with a + so nothing will happen when you release the key—ZDoom only looks at the command actually bound to the key to determine if it should execute a - command when the key is released; it does not look inside aliases. <br /> <br /> === Standard buttons ===<br /> <br /> +attack Use your weapon.&lt;br&gt;<br /> -attack Stop using your weapon. <br /> &lt;br&gt;&lt;br&gt; <br /> +use Start trying to use anything in front of you.&lt;br&gt;<br /> -use Stop trying to use anything in front of you. <br /> &lt;br&gt;&lt;br&gt; <br /> +back Move backward.&lt;br&gt;<br /> -back Stop moving backward.<br /> &lt;br&gt;&lt;br&gt; <br /> +forward Move forward.&lt;br&gt;<br /> -forward Stop moving forward. <br /> &lt;br&gt;&lt;br&gt; <br /> +jump Start jumping.&lt;br&gt;<br /> -jump Stop jumping.<br /> &lt;br&gt;&lt;br&gt; <br /> +left Start turning left.&lt;br&gt;<br /> -left Stop turning left. <br /> &lt;br&gt;&lt;br&gt; <br /> +right Start turning right.&lt;br&gt;<br /> -right Stop turning right. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveleft Start strafing left.&lt;br&gt;<br /> -moveleft Stop strafing left. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveright Start strafing right.&lt;br&gt;<br /> -moveright Stop strafing right. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookdown Start lowering your view.&lt;br&gt;<br /> -lookdown Stop lowering your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +lookup Start raising your view.&lt;br&gt;<br /> -lookup Stop raising your view. <br /> &lt;br&gt;&lt;br&gt; <br /> +movedown Start moving down if swimming or flying.&lt;br&gt;<br /> -movedown Stop moving down. <br /> &lt;br&gt;&lt;br&gt; <br /> +moveup Start moving up if swimming or flying.&lt;br&gt;<br /> -moveup Stop moving up if swimming or flying. <br /> &lt;br&gt;&lt;br&gt; <br /> +strafe Causes +left and +right to behave like +moveleft and +moveright;&lt;br&gt;<br /> -strafe Returns +left and +right to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +klook Causes +forward and +back to act like +lookup and +lookdown instead.&lt;br&gt;<br /> -klook Returns +forward and +back to their normal behavior. <br /> &lt;br&gt;&lt;br&gt; <br /> +mlook Moving the mouse up and down will make you look up and down.&lt;br&gt;<br /> -mlook Moving the mouse up and down will make you move forward and backward. However, if freelook is true, then moving the mouse up and down will still change your view instead of moving you. <br /> &lt;br&gt;&lt;br&gt;<br /> +showscores Display a scorelist for deathmatch games.&lt;br&gt;<br /> -showscores Hide the deathmatch scorelist. <br /> &lt;br&gt;&lt;br&gt; <br /> +speed Start running.&lt;br&gt;<br /> -speed Start walking.<br /> <br /> ==Customization==<br /> * [[Customization]]<br /> <br /> ==Screenshots==<br /> * [[Screenshots]]<br /> <br /> ==Chatting==<br /> * [[Chatting]]<br /> <br /> ==Cheating==<br /> * [[Cheating]]<br /> <br /> ==Display==<br /> * [[Display]]<br /> <br /> ==Renderer==<br /> * [[Renderer]]<br /> <br /> ==Video==<br /> * [[Video]]<br /> <br /> ==Bots==<br /> * [[Bots]]<br /> <br /> ==Automap==<br /> * [[AutoMap]]<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=419 2004-01-05T11:25:37Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, ect...<br /> <br /> you access the console by pressing &quot;~&quot; at any time<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. <br /> <br /> === flag ===<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> * [[Button Commands]]<br /> <br /> ==Customization==<br /> * [[Customization]]<br /> <br /> ==Screenshots==<br /> * [[Screenshots]]<br /> <br /> ==Chatting==<br /> * [[Chatting]]<br /> <br /> ==Cheating==<br /> * [[Cheating]]<br /> <br /> ==Display==<br /> * [[Display]]<br /> <br /> ==Renderer==<br /> * [[Renderer]]<br /> <br /> ==Video==<br /> * [[Video]]<br /> <br /> ==Bots==<br /> * [[Bots]]<br /> <br /> ==Automap==<br /> * [[AutoMap]]<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=418 2004-01-05T11:25:16Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, ect...<br /> <br /> you access the console by pressing &quot;~&quot; at any time<br /> <br /> ==Console variable types==<br /> <br /> There are six types of cvars: Boolean, Integer, Float, String, Colour and Flag.<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> === integer ===<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> === float ===<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> === string ===<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> === colour ===<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. <br /> <br /> === flag ==<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> ==Button Commands==<br /> * [[Button Commands]]<br /> <br /> ==Customization==<br /> * [[Customization]]<br /> <br /> ==Screenshots==<br /> * [[Screenshots]]<br /> <br /> ==Chatting==<br /> * [[Chatting]]<br /> <br /> ==Cheating==<br /> * [[Cheating]]<br /> <br /> ==Display==<br /> * [[Display]]<br /> <br /> ==Renderer==<br /> * [[Renderer]]<br /> <br /> ==Video==<br /> * [[Video]]<br /> <br /> ==Bots==<br /> * [[Bots]]<br /> <br /> ==Automap==<br /> * [[AutoMap]]<br /> <br /> ==Player Settings==<br /> * [[Player Settings]]<br /> <br /> ==Debugging==<br /> * [[Debugging]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Console_commands&diff=417 2004-01-05T11:18:37Z

<p>Lexus Alyus: </p> <hr /> <div>Console Commands are used to alter the way ZDoom does something, such as changing the sound volume, changing DMflags, ect...<br /> <br /> you access the console by pressing &quot;~&quot; at any time<br /> <br /> ==Console variable types==<br /> <br /> There are five types of cvars:<br /> <br /> === boolean ===<br /> <br /> This type of variable represents a yes/no or on/off value. It can only be set to true or false. As shorthand, setting a boolean variable to 0 will set it to false, and setting it to anything non-zero will set it to true. <br /> <br /> == integer ==<br /> <br /> This is an ordinary number without a decimal point. For example, 1 is an integer, but 1.2 is not. <br /> <br /> == float ==<br /> <br /> This is an ordinary number that can have a decimal point. <br /> <br /> == string ==<br /> <br /> This is a series of text characters enclosed in quotes: For example, &quot;Felix loitered lecherously on the lot&quot; is a string. If you removed the quotes around it, then it would not be a string. <br /> If you need to use quotes inside a string, preface it with a backslash.<br /> <br /> Are you &quot;The One&quot; of old?<br /> <br /> would be written like this as a string: <br /> <br /> &quot;Are you \&quot;The One\&quot; of old?&quot;<br /> <br /> == color ==<br /> <br /> This type of variable is a series of three hexadecimal numbers representing the amounts of red, green, and blue (in that order) in a color. For example, pure red would be represented as &quot;ff 00 00&quot;. As a shorthand, you can set a color variable with one of several color names, and the RGB values will be set for you. <br /> <br /> == flag ==<br /> <br /> This type of variable mirrors a setting in dmflags or dmflags2. Setting its value will set the corresponding value in one of those variables, and getting its value will get the corresponding value from one of the other two variables. This is designed to make using dmflags easier, because you don't have to memorize any numbers.<br /> <br /> * [[Button Commands]]<br /> <br /> * [[Customization]]<br /> <br /> * [[Screenshots]]<br /> <br /> * [[Chatting]]<br /> <br /> * [[Cheating]]<br /> <br /> * [[Display]]<br /> <br /> * [[Renderer]]<br /> <br /> * [[Video]]<br /> <br /> * [[Bots]]<br /> <br /> * [[AutoMap]]<br /> <br /> * [[Player Settings]]<br /> <br /> * [[Debugging]]<br /> <br /> This really needs to be cleaned up... so somebody that is more anal than i should fiddle around with it...</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Main_Page&diff=429 2004-01-05T11:14:06Z

<p>Lexus Alyus: </p> <hr /> <div>== Welcome to the ZDoom Wiki ==<br /> <br /> The software currently running the [[ZDoom]] [[Wiki]] is [[MediaWiki]]. Its installation procedure assumes that it will be installed by a user with root access to the server, so I had to make some changes to the installation script to install it on [[zdoom.org]]. For this reason, it is currently considered experimental. I think everything is working, but please test it by writing some pages. If something should work but doesn't, write about it on the [[ZDoom:Bug reports|Bug reports]] page. <br /> <br /> Here's a tentative list of topics for the Main Page, none of which have much content yet: <br /> <br /> * [[ACS]]<br /> * [[Console Commands]]<br /> * [[Level Editing]]<br /> * [[Special Lumps]]<br /> * [[WADs created for ZDoom]]<br /> * [[ZDoom documentation project]]<br /> * [[ZDoom wads in progress]]<br /> <br /> Note: This is here for the sheer purpose of helping out fellow Zdoomers and has no benifit to Randy, therefore it is our responsibility to keep it relevent and safe. The whole purpose of this is so that Randy doesn't have to think about the documentation so he can spend more time perfecting Zdoom. This wiki is for our benifit and it is our responsibility to prevent people from defacing it. We have been given this responsibility, we should respect this and help protect this wiki.<br /> <br /> Happy Zdooming.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Main_Page&diff=300 2004-01-04T15:22:09Z

<p>Lexus Alyus: </p> <hr /> <div>== Welcome to the ZDoom Wiki ==<br /> <br /> The software currently running the [[ZDoom]] [[Wiki]] is [[MediaWiki]]. Its installation procedure assumes that it will be installed by a user with root access to the server, so I had to make some changes to the installation script to install it on [[zdoom.org]]. For this reason, it is currently considered experimental. I think everything is working, but please test it by writing some pages. If something should work but doesn't, write about it on the [[ZDoom:Bug reports|Bug reports]] page.<br /> <br /> Here's a tentative list of topics for the Main Page, which are starting to get lots of content ;-):<br /> * [[ACS]]<br /> * [[Level Editing]]<br /> * [[Special Lumps]]<br /> * [[WADs created for ZDoom]]<br /> * [[ZDoom wads in progress]]</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Talk:Special_lumps&diff=5001 2004-01-04T15:15:43Z

<p>Lexus Alyus: </p> <hr /> <div>Okay, the mapinfo is up. That should be everything. I would have added the rest (apart from decorate) but I feel like I've exhausted myself today (Well, I have added almost all of the line types and specials...).<br /> <br /> Hope somebody else can do these... I just got all of my stuff from the refrence...<br /> <br /> -Lexus Alyus 4/1/2004</div>

Lexus Alyus https://zdoom.org/w/index.php?title=MAPINFO&diff=140 2004-01-04T15:10:56Z

<p>Lexus Alyus: </p> <hr /> <div>ZDoom supports a special MAPINFO lump that can be used to define special characteristics for the different maps in a wad. This lump contains two types of entries: map definitions and cluster definitions which are indicated by the keywords &quot;map&quot; and &quot;clusterdef&quot; respectively. Everything following one of these keywords up until the next &quot;map&quot; or &quot;clusterdef&quot; is considered to be part of the definition for a specific map or cluster. <br /> <br /> ==Map definitions==<br /> <br /> A map definition begins with the word &quot;map&quot;. You can also specify standard characteristics for later map definitons by using the word &quot;defaultmap&quot; instead (and leaving &lt;maplump&gt; and &lt;nice name&gt; blank): <br /> <br /> ===map &lt;maplump&gt; &lt;nice name&gt;===<br /> ====defaultmap====<br /> Substitute the name of the map in the wad for &lt;maplump&gt;, and the map's nice name (shown in the automap) for &lt;nice name&gt;. If &lt;nice name&gt; contains spaces, it must be enclosed in quotation marks (&quot;). &lt;Maplump&gt; can be *any* lump in the wad, but since most editing utilities will only recognize maps of the form MAP?? or E?M?, you should probably stick to those if you want to be able to edit the levels easily. <br /> <br /> After the map (or defaultmap) line, the following properties can be specified: <br /> <br /> ====levelnum &lt;levelnum&gt;==== <br /> This is the map's identification number that is used to identify it to the Teleport_NewMap special. If the map's name is of the form MAPxx, then it will automatically have a levelnum of xx unless you specify differently. (i.e. MAP23's levelnum will be 23 unless you set it to something else.) <br /> <br /> ====next &lt;maplump&gt;==== <br /> &lt;maplump&gt; is the name of the map to move to when the normal exit (Exit_Normal special) is used. This is also the map to travel to when the timelimit or fraglimit is hit in a deathmatch game. This should be the name of the map in the wad and not the map's nice name. <br /> <br /> ====secretnext &lt;maplump&gt;==== <br /> &lt;maplump&gt; is the name of the map to move to when the secret exit is used. This should be the name of the map in the wad and not the map's nice name. <br /> Next and secretnext also accept the special EndGame? names that indicate that ZDoom should end the game instead of continuing to another level. These are: <br /> EndGameC = The cast finale for Doom II <br /> EndGame1 = Displays the picture used after episode 1 <br /> EndGame2 = Displays the picture used after episode 2 <br /> EndGame3 = The bunny scroller after episode 3 <br /> EndGame4 = Displays the picture used after episode 4 <br /> Note that using these will not display any text. To do that, use an &quot;exittext&quot; for this level's cluster. (See clusterdef below.) <br /> <br /> ====cluster &lt;number&gt;====<br /> &lt;number&gt; is the cluster that this map belongs to. See cluster definitions below for more details. <br /> <br /> ====doublesky==== <br /> Specifies that both sky textures are drawn, with sky1 in front of sky2. Sky2 will show through wherever sky1 is color 0 (*not* cyan). <br /> <br /> ====sky1 &lt;texture&gt; &lt;scrollspeed&gt;==== <br /> &lt;texture&gt; is the name of the texture to use for the sky. &lt;scrollspeed&gt; is the rate at which the sky moves left or right (useful for clouds on windy maps). To keep the sky from moving, use a value of 0.0; to move it left, use a positive value; and to move it right, use a negative value. This is the number of steps that the sky moves each tic. <br /> <br /> ====sky2 &lt;texture&gt; &lt;scrollspeed&gt;====<br /> Used the same as sky1, except it selects the properties for the background sky layer (if doublesky is used) or an alternate sky image that can be shown in selected sectors. <br /> <br /> ====fade &lt;color&gt;====<br /> &lt;color&gt; is the color that things fade to the further away or &quot;darker&quot; they are. Normally, this is black, so that things seem darker as they get further away. To simulate fog (ala Hexen), set this to a gray instead. Other colors are also supported, but may not necessarily look very good. &lt;color&gt; can be either the name of a color (such as red or cyan) or a color descriptor of the form &quot;RR GG BB&quot;. For example, to set the fade to red, both of the following will work: <br /> fade red<br /> fade &quot;ff 00 00&quot;<br /> To find a good fade within the game, you can use the testfade console command. <br /> <br /> ====outsidefog &lt;color&gt;==== <br /> This is like fade except that the &lt;color&gt; fade is only applied to sectors with a sky ceiling and not all sectors on the map. <br /> <br /> ====titlepatch &lt;patch&gt;==== <br /> This is the name of a graphic to display on the intermission screen for this level (such as CWILV00). It should contain the name of the level. If this is omitted, the intermission screen will create a graphic for. <br /> <br /> ====par &lt;partime&gt;====<br /> Partime is the number of seconds shown as the level's par in the intermission screen. <br /> <br /> ====music &lt;musiclump&gt;==== <br /> &lt;musiclump&gt; is the name of the song to play while the player is playing the level. <br /> <br /> ====nointermission==== <br /> This indicates that when the current level is finished, ZDoom should continue immediately to the next level without showing the intermission screen. <br /> <br /> ====nosoundclipping==== <br /> This indicates that sounds should not be clipped on the current level no matter how far away they are. I can't say that it's terribly useful, but it is the behavior Doom used on maps E1M8, E2M8, E3M8, and E4M8. <br /> allowmonstertelefrags <br /> This indicates that monsters can telefrag each other or the player on the level. Normally, monsters will never telefrag anything. <br /> <br /> ====map07special==== <br /> This level wants the special feature of Doom II MAP07. In this case, when every mancubus on the level dies, any sectors tagged 666 will have their floors lower to the next lowest floor, and when every arachnotron on the level is dead, any sectors tagged 667 will have their floors raised by the height of their lower textures. <br /> <br /> ====baronspecial==== <br /> After every Baron of Hell on this level has died, a special action will be triggered. <br /> <br /> ====cyberdemonspecial==== <br /> After every Cyber Demon on this level has died, a special action will be triggered. <br /> <br /> ====spidermastermindspecial==== <br /> After every Spider Mastermind on this level has died, a special action will be triggered. <br /> <br /> The above three specials should also be used with one of the following <br /> three special actions: <br /> <br /> ====specialaction_exitlevel==== <br /> Exits the level after all of the specified monsters have died. <br /> <br /> ====specialaction_opendoor==== <br /> After all of the specified monsters have died, opens any doors tagged 666 with blazing speed. <br /> <br /> ====specialaction_lowerfloor====<br /> After all of the specified monsters have died, lowers the floors of all sectors tagged 666 to the next lowest floor. <br /> <br /> ====lightning==== <br /> Creates lightning in the map.<br /> <br /> ====fadetable &lt;colormap&gt;==== <br /> Included for Hexen compatibility. Please don't use it. Right now, it does what it's supposed to (specify a default colormap to use instead of the regular COLORMAP lump), but in the future it will probably just act like a fadeto line. <br /> <br /> ====evenlighting==== (I don't know if this is still valid) <br /> Specifies that lighting should be applied to walls evenly no matter what their orientation. DOOM would use different light levels for walls that were vertical, horizontal, or diagonal (when viewed from above). While this gives better definition to corners, it looks dumb if you have a rotating polyobject because the polyobject's lighting will vary as it rotates. You can disable that behavior by specifying this. <br /> <br /> ====forcenoskystretch==== <br /> If you have a sky graphic that looks fine whether it tiles or not, you can use this, and the sky will never be stretched on this level, regardless of the value of r_stretchsky. <br /> <br /> ====noautosequences==== <br /> By default, the sound sequence played in a sector when it moves is determined by the special used to activate it. If you specify this, whatever sound sequence has ID 0 will be used by default instead. In either case, placing a sound sequence thing (1400-1409) in a sector will cause the sound assigned to that thing to be played. <br /> <br /> ==Cluster definitions==<br /> <br /> A cluster definition begins with the word &quot;clusterdef&quot;. For purposes of ZDoom, clusters are used to displays messages when moving between maps and to optionally group different levels into a hub. <br /> <br /> ===clusterdef &lt;cluster&gt;===<br /> &lt;Cluster&gt; is the cluster that this clusterdef defines. A cluster of 0 is used internally to mean &quot;no cluster&quot; and should be avoided. <br /> <br /> After clusterdef, the following properties are valid: <br /> <br /> ====entertext &lt;message&gt;==== <br /> &lt;message&gt; is a message to be displayed when the player has just finished a level in another cluster and is entering a level in this cluster. <br /> <br /> ====exittext &lt;message&gt;====<br /> &lt;message&gt; is a message to be displayed when the player has just finished a level in a different cluster from the next one. If the next level's cluster has an entertext defined, then it will be shown instead of this cluster's exittext. <br /> <br /> ====music &lt;musiclump&gt;==== <br /> This is the music to play while either the entertext or exittext of this cluster is displayed. For Doom I, this is normally D_VICTOR, and for Doom II, this is normally D_READ_M. <br /> <br /> ====flat &lt;flatlump&gt;==== <br /> This is the name of the flat to use as a background while this cluster's entertext or exittext is displayed. <br /> <br /> ====hub====<br /> Indicates that this cluster is a hub. When leaving a hub, the game will remember the contents of the level when the player left it and restore the level to that state when the player returns to it. Moving to a different cluster will cause the game to forget the state of the levels in this hub in order to save memory. Each level a player visits in a hub uses memory (about 20k for a typical level), so it's probably a good idea not to have too many levels in a single hub. Just how many is &quot;too many&quot; is arbitrary. Unless you use very large levels, you could probably use 50 levels in a hub, and only about 1 meg would be required to keep track of the state of each level. <br /> <br /> ==New features for Zdoom's mapinfo since v1.22 are:==<br /> (Note: the '-' means that i don't know what it does, but i'#m sure some nice person can fill in the gaps ;-) ).<br /> <br /> ====fallingdamage==== <br /> Enables falling damage on the level. This is set permanently meaning that you can't disable it.<br /> <br /> ====nofallingdamage====<br /> Disables falling damage. This also can not be re-enabled if set in the mapinfo lump.<br /> <br /> ====cdtrack====<br /> You can now set tracks from a Cd as music for Zdoom. -<br /> <br /> ====cdid====<br /> -<br /> <br /> ====vertwallshade====<br /> This controls the Vertical wall shading. -<br /> <br /> ====horizwallshade====<br /> This controls the horizontal wall shading. -<br /> <br /> ====gravity====<br /> Gravity is now accessible through the mapinfo lump. Set this for the amount of gravity.<br /> <br /> ====aircontrol====<br /> -<br /> <br /> ====filterstarts====<br /> This filters out player starts based on skill and gametype settings.<br /> <br /> ====NoInventoryBar====<br /> This prevents the inventory bar from ever being drawn in a doom map.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Generic_Stairs&diff=108 2004-01-04T14:34:35Z

<p>Lexus Alyus: </p> <hr /> <div>204:Generic_Stairs (tag, speed, height, flags, reset)<br /> <br /> tag: Tag of first sector in staircase <br /> speed: How quickly the steps move <br /> height: Height of each step <br /> flags: controls direction and ignorance of floor textures <br /> reset: Tics until the stairs return to their original heights (0 if never) <br /> <br /> This special encapsulates BOOM's generalized stairs. The sectors of the staircase are determined as they are in BOOM. If bit 0 of flags is set (0x01), the stairs are built up, otherwise they build down. If bit 1 is set (0x02), then the determination of stair sectors ignores differences floor textures. If a line activates this special, and the line is marked as repeatable, then the direction the stairs build will alternate between up and down each time the special is activated.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Generic_Lift&diff=716 2004-01-04T14:34:08Z

<p>Lexus Alyus: </p> <hr /> <div>203:Generic_Lift (tag, speed, delay, type, height)<br /> <br /> tag: Tag of affected sector <br /> speed: Speed of move <br /> delay: Tics before reversing direction <br /> type: Specifies what type of plat this is <br /> height: Distance to move if target is 0. <br /> <br /> This special encapsulates BOOM's generalized lifts. Type can be one of the following values: <br /> <br /> Value Target <br /> 0 Plat_UpByValue <br /> 1 Plat_DownWaitUpStay <br /> 2 Plat_DownToNearestFloor <br /> 3 Plat_DownToLowestCeiling <br /> 4 Plat_PerpetualRaise</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Generic_Door&diff=272 2004-01-04T14:33:31Z

<p>Lexus Alyus: </p> <hr /> <div>202:Generic_Door (tag, speed, kind, delay, lock)<br /> <br /> tag: Tag of affected sector <br /> speed: How quickly the door moves <br /> kind: What type of door this is <br /> delay: Octics until door is automatically closed/opened <br /> lock: Required key, if any (see key types) <br /> <br /> This special encapsulates BOOM's generalized doors. Kind can be one of four values: <br /> <br /> Kind Meaning <br /> 0 Raise door and close it after delay octics <br /> 1 Open door and leave it open <br /> 2 Close door and open it after delay octics <br /> 3 Close door and leave it closed <br /> <br /> If tag is 0, then the sector on the line's back side is used.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Generic_Crusher&diff=270 2004-01-04T14:32:58Z

<p>Lexus Alyus: </p> <hr /> <div>205:Generic_Crusher (tag, dspeed, uspeed, silent, crush)<br /> <br /> tag: Tag of affected sector <br /> dspeed: How quickly the ceiling lowers <br /> uspeed: How quickly the ceiling raises <br /> silent: Set this to 1 to prevent the crusher from making noise <br /> crush: Amount of damage to apply <br /> <br /> This special encapsulates BOOM's generalized crushers. It is the same as Ceiling_CrushAndRaiseA except that it takes an argument to control the &quot;noisiness&quot; of the crusher.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Generic_Ceiling&diff=273 2004-01-04T14:32:32Z

<p>Lexus Alyus: </p> <hr /> <div>201:Generic_Ceiling (tag, speed, height, target, flag)<br /> <br /> tag: Tag of affected sector <br /> speed: How quickly the ceiling moves <br /> height: Height of the move (for types that use it) <br /> target: How to determine the ceiling's destination height <br /> flags: Flags for the move <br /> <br /> This special encapsulates BOOM's generalized ceilings. Flags are: <br /> <br /> Value Meaning <br /> 0 (0x00) No change <br /> 1 (0x01) Zero sector's special <br /> 2 (0x02) Change sector's ceiling picture <br /> 3 (0x03) Change sector's special <br /> 4 (0x04) Use numeric model if set, trigger model if not <br /> 8 (0x08) Raise ceiling if set, lower it if not <br /> 16 (0x10) Cause crushing damage if set <br /> <br /> Target can be one of the following: <br /> <br /> Value Target <br /> 0 Height units above/below current height <br /> 1 Highest surrounding ceiling <br /> 2 Lowest surrounding ceiling <br /> 3 Nearest surrounding ceiling <br /> 4 Highest surrounding floor <br /> 5 This sector's floor <br /> 6 Height units determined by shortest upper texture on sector <br /> <br /> If tag is 0, then the sector on the line's back side is used.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Generic_Floor&diff=274 2004-01-04T14:31:36Z

<p>Lexus Alyus: </p> <hr /> <div>200:Generic_Floor (tag, speed, height, target, flags)<br /> <br /> tag: Tag of affected sector <br /> speed: How quickly the floor moves <br /> height: Height of the move (for types that use it) <br /> target: How to determine the floor's destination height <br /> flags: Flags for the move <br /> <br /> This special encapsulates BOOM's generalized floors. Flags are: <br /> <br /> Value Meaning <br /> 0 (0x00) No change <br /> 1 (0x01) Zero sector's special <br /> 2 (0x02) Change sector's floor picture <br /> 3 (0x03) Change sector's special <br /> 4 (0x04) Use numeric model if set, trigger model if not <br /> 8 (0x08) Raise floor if set, lower it if not <br /> 16 (0x10) Cause crushing damage if set <br /> <br /> Target can be one of the following: <br /> <br /> Value Target <br /> 0 Height units above/below current height <br /> 1 Highest surrounding floor <br /> 2 Lowest surrounding floor <br /> 3 Nearest surrounding floor <br /> 4 Lowest surrounding ceiling <br /> 5 This sector's ceiling <br /> 6 Height units determined by shortest lower texture on sector <br /> <br /> If tag is 0, then the sector on the line's back side is used.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=SetPlayerProperty&diff=288 2004-01-04T14:27:54Z

<p>Lexus Alyus: </p> <hr /> <div>191:SetPlayerProperty (who, set, which)<br /> <br /> who: Set to 1 to effect all players, 0 for just the one who activated the special <br /> set: Set to 1 to turn on the property or 0 to turn it off <br /> which: Which property to change <br /> <br /> Sets a property for a player. There are more, but I don't know them...<br /> <br /> 0 PROP_FROZEN The player cannot move <br /> 1 PROP_NOTARGET Monsters ignore the player (unless they have already seen him)</div>

Lexus Alyus https://zdoom.org/w/index.php?title=SetPlayerProperty&diff=101 2004-01-04T14:27:14Z

<p>Lexus Alyus: </p> <hr /> <div>191:SetPlayerProperty (who, set, which)<br /> <br /> who: Set to 1 to effect all players, 0 for just the one who activated the special <br /> set: Set to 1 to turn on the property or 0 to turn it off <br /> which: Which property to change <br /> <br /> Sets a property for a player. Currently, there are two: <br /> <br /> 0 PROP_FROZEN The player cannot move <br /> 1 PROP_NOTARGET Monsters ignore the player (unless they have already seen him)</div>

Lexus Alyus https://zdoom.org/w/index.php?title=SetPlayerProperty&diff=100 2004-01-04T14:27:01Z

<p>Lexus Alyus: </p> <hr /> <div>191:SetPlayerProperty (who, set, which)<br /> <br /> who: Set to 1 to effect all players, 0 for just the one who activated the special <br /> set: Set to 1 to turn on the property or 0 to turn it off <br /> which: Which property to change <br /> <br /> Sets a property for a player. Currently, there are two: <br /> <br /> 0 PROP_FROZEN The player cannot move <br /> 1 PROP_NOTARGET Monsters ignore the player (unless they have already seen him)</div>

Lexus Alyus https://zdoom.org/w/index.php?title=ChangeCamera&diff=286 2004-01-04T14:26:30Z

<p>Lexus Alyus: </p> <hr /> <div>237:ChangeCamera (tid, who, revert)<br /> <br /> tid: Thing ID of the camera to use (0 for normal player's view) <br /> who: Set to 1 if the view change should effect all players <br /> revert: Set to 1 if movement should cancel the special <br /> <br /> Causes a player's view to move to a camera. If tid is 0, then the player's view is restored to a spot inside his head. If who is 0, only the player who activated the special has his view changed, otherwise, everyone's view changes. <br /> <br /> If revert is 1, then if a player moves, his view will be returned to his body automatically. This behavior makes this special more suitable for such things as security cameras.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=PointPush_SetForce&diff=287 2004-01-04T14:26:06Z

<p>Lexus Alyus: </p> <hr /> <div>227:PointPush_SetForce (tag, tid, amount, useline)<br /> <br /> tag: Tag of sector containing the point pusher/puller <br /> tid: Thing ID of the point pusher/puller <br /> amount: Strength of the point pusher/puller <br /> useline: Set to 1 to use the line's length to determine strength <br /> <br /> Only valid during initialization. Sets the amount of force for a point pusher or puller. If tag is non-zero it looks for point pusher/pullers in the tagged sectors. Otherwise, it looks for them by their tids. If useline is 1, then the amount of force is determined by the length of the linedef. Otherwise, the amount parameter is used.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Radius_Quake&diff=282 2004-01-04T14:25:40Z

<p>Lexus Alyus: </p> <hr /> <div>120:Radius_Quake (intensity, duration, damrad, tremrad, tid)<br /> <br /> intensity: Strength of earthquake [1..9] <br /> duration: Duration in tics <br /> damrad: Radius of damage in 64x64 cells <br /> tremrad: Radius of tremor in 64x64 cells <br /> tid: Thing ID of map thing(s) for quake foci <br /> <br /> Creates an earthquake at the specified foci (map spots).</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Transfer_CeilingLight&diff=275 2004-01-04T14:25:08Z

<p>Lexus Alyus: </p> <hr /> <div>211:Transfer_CeilingLight (tag)<br /> <br /> tag: Tag of affected sector <br /> <br /> The amount of lighting on the tagged sector's ceiling will be the same as the lighting in the sector that this line faces.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Transfer_FloorLight&diff=276 2004-01-04T14:24:49Z

<p>Lexus Alyus: </p> <hr /> <div>210:Transfer_FloorLight (tag)<br /> <br /> tag: Tag of affected sector <br /> <br /> The amount of lighting on the tagged sector's floor will be the same as the lighting in the sector that this line faces.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Transfer_Heights&diff=277 2004-01-04T14:24:26Z

<p>Lexus Alyus: </p> <hr /> <div>209:Transfer_Heights (tag, when)<br /> <br /> tag: Tag of affected sector <br /> when: When the effect should be visible <br /> <br /> This is BOOM's 242 linedef. It is used to divide a sector into upper, lower, and middle regions. The drawn heights of the tagged sector's floor and ceiling come from the heights of the sector on the line's front side. The line's texture names can be used to specify a specify a special color map or palette blend to be used in those ranges. Palette blends are of the form &quot;AARRGGBB&quot;. You can use the testblend command to find a good blend from inside the game. <br /> <br /> The when parameter determines when this special's effect is visible. If set to 0, there will be situations when the sector's real ceiling and floor heights will be used instead of the fake heights. (This is the way BOOM does it.) When set to 1, the fake ceiling and floor heights will always be used. <br /> <br /> The following description is excerpted from boomref.txt: <br /> <br /> <br /> This allows the tagged sector to have two levels — an actual floor and ceiling, and another floor or ceiling where more flats are rendered. Things will stand on the actual floor or hang from the actual ceiling, while this function provides another rendered floor and ceiling at the heights of the sector on the first sidedef of the linedef. Typical use is &quot;deep water&quot; that can be over the player's head. [Note: See the waterzone thing (9045)] <br /> <br /> ---------------------------------- &lt; real sector's ceiling height<br /> | real ceiling | &lt; control sector's ceiling texture<br /> | |<br /> | | &lt; control sector's lightlevel<br /> | A |<br /> | | &lt; upper texture as colormap<br /> | |<br /> | | &lt; control sector's floor texture<br /> ---------------------------------- &lt; control sector's ceiling height<br /> | fake ceiling | &lt; real sector's ceiling texture<br /> | |<br /> | | &lt; real sector's lightlevel<br /> | B |<br /> | | &lt; normal texture as colormap<br /> | |<br /> | fake floor | &lt; real sector's floor texture<br /> ---------------------------------- &lt; control sector's floor height<br /> | | &lt; control sector's ceiling texture<br /> | |<br /> | | &lt; control sector's lightlevel<br /> | C |<br /> | | &lt; lower texture as colormap<br /> | |<br /> | real floor | &lt; control sector's floor texture<br /> ---------------------------------- &lt; real sector's floor height<br /> <br /> Boom sectors controlled by a 242 linedef are partitioned into 3 spaces. The viewer's xyz coordinates uniquely determine which space they are in. <br /> <br /> If they are in space B (normal space), then the floor and ceiling textures and lightlevel from the real sector are used, and the colormap from the 242 linedef's first sidedef's normal texture is used (COLORMAP is used if it's invalid or missing). The floor and ceiling are rendered at the control sector's heights. <br /> <br /> If they are in space C (&quot;underwater&quot;), then the floor and ceiling textures and lightlevel from the control sector are used, and the lower texture in the 242 linedef's first sidedef is used as the colormap. <br /> <br /> If they are in space A (&quot;head over ceiling&quot;), then the floor and ceiling textures and lightlevel from the control sector are used, and the upper texture in the 242 linedef's first sidedef is used as the colormap. <br /> <br /> If only two of these adjacent partitions in z-space are used, such as underwater and normal space, one has complete control over floor textures, ceiling textures, light level, and colormaps, in each of the two partitions. The control sector determines the textures and lighting in the more &quot;unusual&quot; case (e.g. underwater). <br /> <br /> It's also possible for the fake floor to extend below the real floor, in which case an invisible platform / stair effect is created. In that case, the picture looks like this (barring any ceiling effects too): <br /> <br /> <br /> ---------------------------------- &lt; real sector's ceiling texture<br /> | real ceiling = fake ceiling |<br /> | |<br /> | |<br /> | B | &lt; real sector's lightlevel<br /> | | &lt; normal texture's colormap<br /> | |<br /> | real floor |<br /> ---------------------------------- &lt; invisible, no texture drawn<br /> | |<br /> | |<br /> | | &lt; real sector's lightlevel<br /> | C | &lt; normal texture's colormap<br /> | |<br /> | |<br /> | fake floor | &lt; real sector's floor texture<br /> ---------------------------------- &lt; fake sector's floor height<br /> <br /> In this case, since the viewer is always at or above the fake floor, no colormap/lighting/texture changes occur — the fake floor just gets drawn at the control sector's height, but at the real sector's lighting and texture, while objects stand on the higher height of the real floor. <br /> <br /> It's the viewer's position relative to the fake floor and/or fake ceiling which determines whether the control sector's lighting and textures should be used, and which colormap should be used. If the viewer is always between the fake floor and fake ceiling, then no colormap, lighting, or texture changes occur, and the view just sees the real sector's textures and light level drawn at possibly different heights. <br /> <br /> If the viewer is below the fake floor height set by the control sector, or is above the fake ceiling height set by the control sector, then the corresponding colormap is used (lower or upper texture name), and the textures and lighting are taken from the control sector rather than the real sector. They are still stacked vertically in standard order — the control sector's ceiling is always drawn above the viewer, and the control sector's floor is always drawn below the viewer. <br /> <br /> The kaleidescope effect only occurs when F_SKY1 is used as the control sector's floor or ceiling. If F_SKY1 is used as the control sector's ceiling texture, then under water, only the control sector's floor appears, but it &quot;envelops&quot; the viewer. Similarly, if F_SKY1 is used as the control sector's floor texture, then when the player's head is over a fake ceiling, the control sector's ceiling is used throughout. <br /> <br /> F_SKY1 causes HOM when used as a fake ceiling between the viewer and normal space. Since there is no other good use for it, this kaleidescope is an option turned on by F_SKY1. Note that this does not preclude the use of sky REAL ceilings over deep water — this is the control sector's ceiling, the one displayed when the viewer is underwater, not the real one. <br /> <br /> A colormap has the same size and format as Doom's COLORMAP. Extra colormaps may defined in Boom by adding them between C_START and C_END markers in wads. Colormaps between C_START and C_END are automatically merged by Boom with any previously defined colormaps. <br /> <br /> <br /> <br /> <br /> Ceiling bleeding may occur if required upper textures are not used.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Scroll_Texture_Both&diff=249 2004-01-04T14:22:09Z

<p>Lexus Alyus: </p> <hr /> <div>221:Scroll_Texture_Both (lineid, left, right, down, up)<br /> <br /> lineid: Line ID of line to scroll (must be 0 for now) <br /> left: Speed to scroll left <br /> right: Speed to scroll right <br /> down: Speed to scroll down <br /> up: Speed to scroll up <br /> <br /> Scrolls a texture both horizotally and vertically. If the lineid is 0, this special will affect the speed of the texture scrolling on the line it is placed on. The other four parameters determine how quickly the texture scrolls in each direction. <br /> <br /> If you use a non-zero lineid, you can change the scrolling of the specified lines when this special is activated (either directly or in a script). A positive lineid changes the scrolling on the front of the line, and a negative lineid changes the scrolling on the back of the line.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Scroll_Texture_Down&diff=248 2004-01-04T14:21:43Z

<p>Lexus Alyus: </p> <hr /> <div>103:Scroll_Texture_Down (speed)<br /> <br /> speed: Speed to scroll<br /> <br /> Scrolls a texture in down.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Scroll_Texture_Up&diff=247 2004-01-04T14:21:20Z

<p>Lexus Alyus: </p> <hr /> <div>102:Scroll_Texture_Up (speed)<br /> <br /> speed: Speed to scroll<br /> <br /> Scrolls a texture in up.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Scroll_Texture_Right&diff=246 2004-01-04T14:20:57Z

<p>Lexus Alyus: </p> <hr /> <div>101:Scroll_Texture_Right (speed)<br /> <br /> speed: Speed to scroll<br /> <br /> Scrolls a texture in right.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Scroll_Texture_Left&diff=245 2004-01-04T14:20:36Z

<p>Lexus Alyus: </p> <hr /> <div>100:Scroll_Texture_Left (speed)<br /> <br /> speed: Speed to scroll<br /> <br /> Scrolls a texture in left.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=Scroll_Texture_Left&diff=99 2004-01-04T14:20:10Z

<p>Lexus Alyus: </p> <hr /> <div>100:Scroll_Texture_Left (speed)<br /> <br /> speed: Spped to scroll<br /> <br /> Scrolls a texture in left.</div>

Lexus Alyus https://zdoom.org/w/index.php?title=TranslucentLine&diff=244 2004-01-04T14:19:23Z

<p>Lexus Alyus: </p> <hr /> <div>208:TranslucentLine (lineid, amount)<br /> <br /> lineid: Line ID of lines to make translucent (0 for this line) <br /> amount: How translucent the line should be [0..255]. <br /> <br /> Sets the amount of translucency for all matching lines (including itself). If lineid is 0, it only sets the translucency of the line it is on. Like Line_SetIdentification, this special sets the line's id. Amount controls how opaque the line is. 0 is nearly invisible. 255 is opaque. Intermediate values are somewhere in between. <br /> <br /> You can also use this special in an ACS script to change the translucency for lines whose ids match lineid.</div>

Lexus Alyus