when rafting from one dmap to another it triggers the "secrets" sound.
1099
rafting
You should be able to set that screens SFX from 27 to 0 right?
yea, probably.
just the first time it's ever done that.
These newer versions seem to have turned my quest into a bug infested piece of.....
many of the things that worked flawlessly are now screwed up, and it's taking building time away from it to go back and fix shit.
hell my timed jumps were perfect, now I had to go back and reset the timed warps to tweak them in again for some reason.
doesn't make any sense.
so I know I can fix a lot of this stuff but why hell did it get changed to do things like play the secret sound changing from one dmap to another, in the first place.... ya know?
I'm starting to remember why I quit, I just hate having to do those things over and over again.
All the new stuff in there is great, only problem is, it broke so many things that came before it and worked.
What version is your quest designed for? If it was for 2.10 or older then all you had to do was open the quest in a new version of Zquest, save it, open it in the player and see if anything is fucked. Repeat but without opening/saving in Zquest.
Freedom wrote:
so I know I can fix a lot of this stuff but why hell did it get changed to do things like play the secret sound changing from one dmap to another, in the first place.... ya know?I'm starting to remember why I quit, I just hate having to do those things over and over again.
All the new stuff in there is great, only problem is, it broke so many things that came before it and worked.
The problem is the never ending development time. Every so many builds something works different for a plethora of reasons and you just have to go through and update it. Everyone is is tired of doing this Freedom, not just you. I've had to fix various things half a dozen times now. We're at a point now where if you've been using the betas for a while you're inclined to just say "screw it". (I skipped the whole 800-1000 block because I didn't care to deal with that crap then. 😉 )
We're all in agreement about a feature-lock and a pending release. So what that means is technically the new build is 2.5 -plus some bugs and small issues that need to be dealt with. Updating at this point, as brutal as it may be,should now be a one time charge.
franpa wrote:What version is your quest designed for? If it was for 2.10 or older then all you had to do was open the quest in a new version of Zquest, save it, open it in the player and see if anything is fucked. Repeat but without opening/saving in Zquest.
I started this quest (SwanSong~Genesis) originally in the 211b10b, because the quest I was building at the time (Robinhood) got trashed going from 211b10b to beta 211b12 and I figured it would be easier to just start over than to try and repair everything.
I continued on through the years and worked up as far as 846 (I think)
Then recently decided to try again and upgraded it to the 1099.
so to answer your question... it was/is designed for whatever the latest build I trust using is.
Gleeok,
Ya I know all that all to well, that's why I've been so outspoken about a stable release that can be used to actually build and release quests with, once you get passed a certain point, like 211b10b was for me, there is no going back, and since there has been no stable version released since, then it seems there is no going forward either.
ALWAYS at some point going forward, you run the risk of losing all you've done in the past.
that's why everyone is quitting.