New features (last update 8.8.2005)

Post by **Graf Zahl** » Wed Jun 22, 2005 12:14 pm

The HUD sprites can't be doubled yet. That code uses a special scaling logic which I have to fully understand before altering it. But that wasn't something I wanted to delay this version for.

Daniel · Post by **Daniel** » Wed Jun 22, 2005 12:14 pm

Nice work Grubber and Graf, I just downloaded the new EXE mod. Unfortunately, seems that something is happening:

1) When using A_DropInventory in USE state, it removes one item from the inventory. But the USE state also drop one inventory just for the using action, so what is happening: When you drop a inventory, you lost 2 of them, and only one is spawned.

This leads to another bugs for me:

2) I want to drop the BFGCircuit, which has a maxinventory of 1. When using it, the USE state also removes it, so it can't be dropped because any inventory remained. I think you could fix the USE state to take ammo after all the commands were done, if don't, all inventories with one ammo left will have this same problem. How about make a new end command like Stop or Fail, called "Remove" or something? It takes one inventory ammo, so it will fix that.

3) The A_DropInventory doesn't drop non-inventory actors, so it coudn't fix the AutoDetectMine problem.

4) I tried to use A_Jiggle(x offset, y offset) on a weapon, it didn't work.

Now, the good news

1) The rocket splash and the +FRIENDLY problem is fixed

2) Could you explain to me how these contepointers work?
A_CheckSight
A_ExtChase
A_SpawnDebris
A_Recoil

I'll make some tests here, hope I can help you to fix some problems.

Post by **Graf Zahl** » Wed Jun 22, 2005 12:40 pm

Daniel wrote:Nice work Grubber and Graf, I just downloaded the new EXE mod. Unfortunately, seems that something is happening:

1) When using A_DropInventory in USE state, it removes one item from the inventory. But the USE state also drop one inventory just for the using action, so what is happening: When you drop a inventory, you lost 2 of them, and only one is spawned.

This leads to another bugs for me:

2) I want to drop the BFGCircuit, which has a maxinventory of 1. When using it, the USE state also removes it, so it can't be dropped because any inventory remained. I think you could fix the USE state to take ammo after all the commands were done, if don't, all inventories with one ammo left will have this same problem. How about make a new end command like Stop or Fail, called "Remove" or something? It takes one inventory ammo, so it will fix that.

Ok, that means the function is useless in its current form. I'll look for a way to fix it.

3) The A_DropInventory doesn't drop non-inventory actors, so it coudn't fix the AutoDetectMine problem.

No, it doesn't. After all it's called A_DropInventory!

4) I tried to use A_Jiggle(x offset, y offset) on a weapon, it didn't work.

The one function I haven't tested...

Daniel · Post by **Daniel** » Wed Jun 22, 2005 12:44 pm

Btw, A_Jiggle must have a time in TICs to make the effect. I thought that the frame time would be this time.

But how de we can make a safe way to drop anything that aren't inventories? Maybe some kind of A_DropActor is required (I think the unique restriction for the actor is that he can't be +SOLID)...

Another idea: in Strife, we have inventories that don't change its ammount when you change a level (in the opposite for Heretic). Is there a flag to avoid this effect? (I saw HUBPOWER in the EXE file, but it didn't nothing)

dennisj1 · Post by **dennisj1** » Wed Jun 22, 2005 1:23 pm

I see my request for more than 6 keys is in, but now NO keys (not even the original 6) appear in the status bar anymore.

Post by **Graf Zahl** » Wed Jun 22, 2005 1:30 pm

Daniel wrote: Another idea: in Strife, we have inventories that don't change its ammount when you change a level (in the opposite for Heretic). Is there a flag to avoid this effect? (I saw HUBPOWER in the EXE file, but it didn't nothing)

That's automatic for hubs. If you want it in a game with normal level transitions you have to declare each one a separate hub. But yes, I agree. This should be a MAPINFO option instead of being decided by the way a WAD is organized.

Post by **Graf Zahl** » Wed Jun 22, 2005 1:32 pm

dennisj1 wrote:I see my request for more than 6 keys is in, but now NO keys (not even the original 6) appear in the status bar anymore.

Ooops! I think that's a bug. A clear result of me not using the status bar. But this should be easily fixable. I'll look into it ASAP.

Daniel · Post by **Daniel** » Wed Jun 22, 2005 1:44 pm

Graf: remember the bug I said to you, if you use A_FireCustomMissile for drop an inventory, and get too close from a wall? It is fixed if you use A_ThrowGrenade.

I'll review all the inventory items I was working on. I'm using a dropper actor to drop the inventories, since there is no safe command for dropping it yet.

Btw, when you use A_SpawnItem without specify any distance or height, the item is not dropped into the same place of the dropper, so it doesn't obbey the logic...

Post by **Bio Hazard** » Wed Jun 22, 2005 1:50 pm

What is this "custom keys" thing you want so bad graf? Can't you just make a key item with decorate and script your locked door? I'm sure you could write an open-ended script to use for almost any door.

*working on locked door script*

Post by **Graf Zahl** » Wed Jun 22, 2005 2:03 pm

The key code has been fixed. I just didn't handle the assignment of key numbers correctly. Grubber, please update!

Post by **Graf Zahl** » Wed Jun 22, 2005 2:07 pm

Bio Hazard wrote:What is this "custom keys" thing you want so bad graf?

Just a simple means of assigning keys to locks. Look at the LOCKDEFS lump in the .zip to see what I mean.

Can't you just make a key item with decorate and script your locked door? I'm sure you could write an open-ended script to use for almost any door.

*working on locked door script*

Save the work. The key handling is complete, now that I have fixed the status bar bug.

Sure, you could do a lot of stuff in ACS. But why does it always have to be the complicated method? This works fine if you need just one key but the possibilities of the existing locking mechanism should be used IMO.

Post by **Graf Zahl** » Wed Jun 22, 2005 2:12 pm

Daniel wrote: Btw, when you use A_SpawnItem without specify any distance or height, the item is not dropped into the same place of the dropper, so it doesn't obbey the logic...

No, if you don't specify a distance the item is placed so that it doesn't intersect with the dropper. Just use a distance of 1 to get what you want. The minimal deviation won't be noticed.

Daniel · Post by **Daniel** » Wed Jun 22, 2005 2:18 pm

@Graf: yes, it was I'm doing right now.

The problem of the friendly monster into an empty room still continues, but I edited it to a minimal chance of the object listen to a player shot:

Spawn:
ADTM AAAA 1 A_Look
ADTM A -1
Stop

Lemonzest · Post by **Lemonzest** » Wed Jun 22, 2005 2:36 pm

Graf Zahl wrote:The HUD sprites can't be doubled yet. That code uses a special scaling logic which I have to fully understand before altering it. But that wasn't something I wanted to delay this version for.

Thanks, understood.

Anakin S. · Post by **Anakin S.** » Wed Jun 22, 2005 4:40 pm

Sorry Graf, but it seems that A_JumpIfCloser still doesn't work with weapons. It looks great for the most part. Can't wait to try out all the new functions.

EDIT: Nevermind. It was something else when I was testing it with the most recent build. I put 0 for the horizontal and vertical spreads for A_FireBullets. I'll try A_JumpIfCloser with my other wads to see if it works.

EDIT2: I tried it with the same wad again and it doesn't work.

Is it possible to make a range limit for hitscan attacks?