The official "ZDoom on Wolfenstein 3D" thread. (aka ECWolf)

[NeuralStunner]

At the moment, only two things I can think of that I need:

• Next/Previous Weapon controls.
• Keypad scancode support (KP are unique keys).

Not to mention automap (with level stats!) but that's planned anyway.

[BlueFireZ88]

It seems a bit slow on the menu screens, especially at higher resolutions (the menu comes to a crawl when I put it at my default resolution 1600x900).

[Blzut3]

Yeah, eventually I need to rewrite the menus to be based on a constant game timer instead of steps.

At the moment, only two things I can think of that I need:

• Next/Previous Weapon controls.
• Keypad scancode support (KP are unique keys).

You might want to put these in the tracker.

[NeuralStunner]

It seems a bit slow on the menu screens, especially at higher resolutions (the menu comes to a crawl when I put it at my default resolution 1600x900).

I actually only noticed slowdowns in fullscreen mode, regardless of resolution. 1280x800 windowed runs fine (albeit partly offscreen).

You might want to put these in the tracker.

Done.

[Enjay]

• Next/Previous Weapon controls.

And mousewheelup/down binding support added (if it isn't already there).

[TheDarkArchon]

And mousewheelup/down binding support added (if it isn't already there).

It isn't. Posted it to the tracker.

[Blzut3]

News about Wolf3D patch and documentation.

[Sgt Dopey]

sorry for the bump but how do I make custom enemies and maps for this

[Blzut3]

For maps you use WDC, then export them, then insert them into a wad with two lumps. One is the map header and the other is a PLANES lump which will hold that data. Until you're ready to release, however, you can just use the gamemaps file directly.

For enemies you use DECORATE. The wiki should currently have a decent amount of information on that. You'll need to use a map translator to put your new enemies in the maps though. Copy the xlat/wolf3d.txt file for your base and refer to the wiki for basic syntax.

[Beefeater]

One of the things about Wolf3D that keeps grinding my gears are the controls.

Can I suggest that (besides improved mouse support) you implement an option for player inertia? It doesn't even have to be floaty Doom-style, Quake-style would be a massive improvement already.

Echo-ing the requests for an automap, too. That would improve the game massively.

Also, hi everyone, I'm new

[mallo]

A_Jump isn't working, i mean, I made:

Code: Select all

Spawn:
blah a 0 A_Jump(256, "Blurgh", "Bleargh")
Blurgh:
You stink
stop
Bleargh:
I hate you
stop

(or something similiar)
but it kept on going into "Blurgh". So out of curiousity i adden "stop" after Spawn and now nothing's appearing. Is something wrong with my code, or is it an error of A_Jump?

Sorry for my english.

[Woolie Wool]

It would be nice if you posted your actual code instead of code that is half nonsense. "Summarizing" code in such a manner just adds ambiguity.

[mallo]

Whoops, sorry.

Code: Select all

Actor MachineGunSpawner replaces MachineGun
{
	States
	{
	Spawn:
		TNT1 A 0 A_Jump(256, "Bootspork", "LargeZorcher")
		stop
	Bootspork:
		TNT1 A 1 A_SpawnItem("Bootspork",0,0,0,0)
		TNT1 A 0
	stop
	LargeZorcher:
		TNT1 A 1 A_SpawnItem("LargeZorcher",0,0,0,0)
		TNT1 A 0
	stop
	}
}

[Woolie Wool]

TNT1 A 0 A_Jump(256, "Bootspork", "LargeZorcher")

This may be the problem. Set the frame duration to 0.5 and see if that works.

Also you could simplify the jump like so:

Code: Select all

Actor MachineGunSpawner replaces MachineGun
{
   States
   {
   Spawn:
      TNT1 A 0.5 A_Jump(128, "LargeZorcher")
      TNT1 A 0.5 A_SpawnItem("Bootspork",0,0,0,0)
      TNT1 A 0
   stop
   LargeZorcher:
      TNT1 A 0.5 A_SpawnItem("LargeZorcher",0,0,0,0)
      TNT1 A 0
   stop
   }
}

[InsanityBringer]

does ecwolf inherit the doomism where the function in the first spawn state isn't executed? I have no idea.