Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

448 Arrow issue...

8 replies · 1,257 views · Started 08 July 2007

shooting any arrow, the arrow gets stuck and you can't shoot another one.
it never happened prior to this, I don't believe, but nothing is set to "BLOCK"
anything but the just stop when shot.

nevermind, found the issue, the bows power # had been somehow been set to
0 instead of it's default, but I never touched it to change it.

What version of ZQ did you use to save the quest before this corruption occurred? Do you still have a backup from that version?

not sure, i'd have to check, I know all was fine in 373.

I also think that even up to 429 was fine, I never played with arrows
from then until 448, i'll check my back-ups.

EDIT.
what I see in my 429 back-up it says....
Long Bow, power=2, and the defaults on 448 say power=3
but the last time I opened the quest the power on both bows were at 0
and I found that was why the arrows didn't shoot right.

the 434 build I checked and the Bows are set at Power=0
so somewhere between saves from 429 - 434 it happened

Sounds like maybe that tab issue that got me may have gotten him too, problems arose between the same versions.

actually it's not a ZC back-up, it was my own. I have been saving my own
back-ups, by copying & pasting then renaming the files. I really don't rely on
ZC to back me up, so that isn't the issue, it's within ZC itself. I just reopened
my old saved quests that were saved from prior builds.

opened a copy saved in 429, the bow was fine, opened up 434 and the item
properties were screwed up. and as I said, I never bothered them.

apparently the corruption happened as the quest was saving in the new
(434 +) build version. that's my guess anyhow, you would know better than I.

it's not a saved back-up, it's an actual saved quest, I didn't import anything.

all was working fine in build 429...........

I saved my quest in 429, I copied and pasted the quest then renamed it for a
back-up (not backed up by ZC, I don't use ZC's back-ups, I make my own)

replaced build 429 files with 434 + (never noticed the problem until 448, but
as I stated when I reopened my old saves, the file saved in build 429 was the
last one where the Bow was set right, and I checked each save from each
build after 434, everytime I use a new build I make a copy of my quest,
incase the new build screws up)

then I finally tested a room where I needed Arrows in build 448, and noticed
that the Arrows hung up when shot, after posting this bug I discovered that
the Bow's properties had been changed.

I save my own back-ups DD, I rename the file myself........
EXAMPLE:
"LOZ_OA_v5.9.qst" (copy then paste)
"Copy of LOZ_OA_v5.9.qst" (then I rename it)
"LOZ_OA_v5.9.b429", "LOZ_OA_v6.0.b434", "LOZ_OA_v6.0.b448"
for each build / quest version after, I replace the .qst filename, with the build number.

so it's not a back-up that's corrupted, it happened maybe when I saved
my quest in the 434 build.

I can post my 434 build save, if that would help, but I don't have any
back-ups generated by ZC itself.

That's fine; by "backup" I meant "any copy of the quest, be it generated automatically or by you."

Does loading the last uncorrupted copy, and saving, corrupt the arrows? If so, please post the uncorrupted copy.