ZDoom

Whiteace wrote:I am not really keen to asking people this especially on Doom forums since I have a pretty bad experience but, I would like to know if there's anyway to store a variable based on where the player spawns, okay so here's the scenario, I have Randomplayerstarts defined in mapinfo for 1 map I have player starts I need to utilise ACS in order to A. At the start of the game store a variable that tells it which spawn the player has spawned B. Use that variable with an if statement to determine if it should remove certain line blocking

I actually only need that A part, everything is smooth sailing from there but I just can't seem to wrap my head around how to do it even though it should be 100% possible.

I did a quick test:
1. drop a mapspot on every player start and give each mapspot a tag;
2. in the ENTER script compare GetActorX(0) with GetActorX of the tags and check which one is equal.

(don't know if you really need to store a variable because you could act immediately when you have a match)

how do i remove all the unused textures out of a WAD automatically using doombuilder (or whatever). i remember someone talking about it but i never saw a use for it until right now.


EDIT: if anyone else is curious about this, please see this link. great app. https://www.doomworld.com/vb/doom-editi ... optimizer/

new question.

whats the best way to organize textures in slade so that they show up in "folders" in doom builder?

as in a door texture showing up in the "doors" folder.

cortlong50 wrote:new question.

whats the best way to organize textures in slade so that they show up in "folders" in doom builder?

as in a door texture showing up in the "doors" folder.

Just put them into sub-folders inside the textured folder. they will the show up in GZDoomBuilder under textures/yourFolder(/...)

Cherno wrote:

cortlong50 wrote:new question.

whats the best way to organize textures in slade so that they show up in "folders" in doom builder?

as in a door texture showing up in the "doors" folder.

Just put them into sub-folders inside the textured folder. they will the show up in GZDoomBuilder under textures/yourFolder(/...)

thanks for the reply, im actually building the map pack under a .wad right now. is there any way to organize as a .wad? or should i convert to PK3?

If you're putting maps into a .pk3 file, they will each need to be packaged in individual .wad files and stored in the "Maps" folder.

DoomKrakken wrote:If you're putting maps into a .pk3 file, they will each need to be packaged in individual .wad files and stored in the "Maps" folder.

But I’m not using a .PK3.

Right now the map pack is a .wad.

So...with the map pack being in .wad format
How would I organize the (let’s use doors as an example) door textures to show in the “doors” folder?

cortlong50 wrote: So...with the map pack being in .wad format
How would I organize the (let’s use doors as an example) door textures to show in the “doors” folder?

Since a wad file does not have a folder structure per se, you could sort
the textures into headings like this within TX_ headers

Spoiler:

---

TX_START
========
WALLS
|
|
========
FLOORS
|
|
========
DOORS
|
|
========
SCENERY
|
|
TX_END

This gives some Invalid data indications, but the game will work

Texman.Init: Init texture manager.
Invalid data encountered for texture jumps.wad:WALLS
Invalid data encountered for texture jumps.wad:FLOORS
Invalid data encountered for texture jumps.wad:DOORS
Invalid data encountered for texture jumps.wad:========

And the editor complains about the extra lumps.

so, maybe the next approach is better

Or preface the textures with an identifier, eg

Spoiler:

---

TX_START
WL_
FL_
DR_
SC_
TX_END

or whatever.

Here's the problem I'm currently facing.
A mapset defines a monster, and a mod defines a different monster with the same name. I'm making a compatibility patch that modifies (replaces) the mapset's custom monsters, but in this case I'm stumped.

I've thought about using the same editor number instead of the replace keyword. However, I don't know if that's going to work.

I try make monster with custom hitbox area.
Why? Because demon walk through hot magma field, forbidden cybernetics augmentations and unstable trans-dimensional portals just to die from one shot from rusty shootgun, who saw how Hannibal walk to the gates of Rome? I dont think so...
Besides, it make him more dangerous.
How? Well, you shoot him arm? He slowly retreat and still fight back, but not so accurate as before.
Shoot his leg? He fall at ground and lose abytily to walk, just crawl like worm, but gain much smaller hitbox.
Shoot his head? He start pulsing gush with arterial blood from neck stump shooting in every direction indiscriminately.
Pinned him to wall? "Just a flesh wound"
Fill his torso with bullet/holes? He start stain all around with blood and slowly lose hitpoint, accuracy and reaction/walking/shooting/etc. speed.

Now I almost finished pairs of such monsters, but I stuck in process of assembly all head/hand/foot/torso/hoof/horns and other chaingun with rocket launcher in one pile.
The problem is that actor which embody parts of body much smaller than hitbox of desired monster, say imp. I must, and wish, insert all body part inside of hitbox that imp, which make it completely unreachable for attacking, since all attack blocks by hitbox of that imp.

I try add to imp flag "spectral". It works, but now imp can not be reached by its body part, when it try to say/put in inventory token which means "you lost you arm/head" or damage him to imitate pain state.
I try make imp hitbox selectively skip only projectail, melee and hitscan via zscript. I get how make projectile fly through, hitscan and melee stil stuck in imp-master.
I try make infinitesimal hitbox for imp-master. It works as I want, but now imp can literally seep through closed doors/walls/other actors like true ghost, due his size of blocking. I dont know how make it stop do such thing when a_warp of his body part is impossible because of lack of space.
I even try act in the forehead, go over with brute force through all available combinations of flag, actor property and zscript cancollidewith in hope that I miss somethng or dont get. I spare 6 hours without any result.


So, anyone have any ideas how insert actor with smaller hitbox into actor with larger hitbox and make smaller actor shootable/reachable for/with projectile, hitscan and melee attack?

gwHero wrote: I did a quick test:
1. drop a mapspot on every player start and give each mapspot a tag;
2. in the ENTER script compare GetActorX(0) with GetActorX of the tags and check which one is equal.

(don't know if you really need to store a variable because you could act immediately when you have a match)

Thank you, that should definitely work, I've got it all sorted out in my head now you don't know how much this has helped me.

I have a bit of a problem. I have a weapon that fires and reloads right after firing (the SSG) and I am trying to add a good pitch change to it with A_SetPitch to simulate recoil. I just realized that there's a problem where the pitch won't get restored to center if you manage to fire the last two shells and have mouselook off, leaving your view skewed. Removing the pitch changes after A_CheckReload and then modifying the pitch changes before it works and is indeed a solution, however now the effect is much quicker and I don't have room to spread it out. Suggestions?

How about modifying Deselect? Since that's where A_CheckReload goes if you have no ammo.

Is it possible to put a camera texture inside another texture?

worldendDominator wrote:How about modifying Deselect? Since that's where A_CheckReload goes if you have no ammo.

That would work except you can also deselect at any time without being empty, which if not empty, would make it go down more than it should and would still end up being skewed. I think I might just have to go with the faster pitch change because I don't see any other options.