Jump to content

Photo

New Quest 2003 is dead.


  • Please log in to reply
17 replies to this topic

#1 Nightmare

Nightmare

    Original ZC Tester

  • Members
  • Real Name:James
  • Location:Jackson, NJ

Posted 29 August 2017 - 08:51 AM

Unless you're running 1.92 B 182/3 or running DOSBox, New Quest 2003 is officially dead in 2.53.  The structural damage caught up and it just doesn't work, konks out in the first mini-dungeon.

 

Knew this day was coming.  Sorry Gleeok and other purists.

 

The 2013 and Rebuilt are your options for this quest going forward in 2.53.  Maybe if we get a special build or DOSBox working this will be functional again.

 

-James


  • Shane and Matthew like this

#2 Ryunaker

Ryunaker

    Junior

  • Members

Posted 29 August 2017 - 03:07 PM

I just wanted to know if you were aware of the following:
 

We would appreciate bug reports on any of the following:

  • Playing quests made in 1.92, 2.10, 2.50.x and reporting any compatibility bugs.

They may be willing to work with you on fixing the damage.  (Unless you've already tried this.)



#3 Nightmare

Nightmare

    Original ZC Tester

  • Members
  • Real Name:James
  • Location:Jackson, NJ

Posted 29 August 2017 - 03:25 PM

I just wanted to know if you were aware of the following:
 

We would appreciate bug reports on any of the following:

  • Playing quests made in 1.92, 2.10, 2.50.x and reporting any compatibility bugs.

They may be willing to work with you on fixing the damage.  (Unless you've already tried this.)

 

Are you "even on ZC development staff"?  Most of the staff is well aware of what I'm testing and 1.02 compatibility is not on the list at the current moment.  I'd consider this message rather trollish if you're not.

 

-James


Edited by Nightmare, 29 August 2017 - 03:25 PM.


#4 strike

strike

    life is fragile, temporary, and precious

  • Members
  • Real Name:Olórin

Posted 29 August 2017 - 03:56 PM

The guy is just trying to be helpful : P No reason to call him a troll. 


  • ShadowTiger, Anthus, nicklegends and 1 other like this

#5 TheRock

TheRock

    Go glitches

  • Members

Posted 29 August 2017 - 04:23 PM

Would it be possible to make a version to work in 2.5.3? I'm sure it's possible...



#6 Nightmare

Nightmare

    Original ZC Tester

  • Members
  • Real Name:James
  • Location:Jackson, NJ

Posted 29 August 2017 - 06:28 PM

The guy is just trying to be helpful : P No reason to call him a troll. 

I've put a lot of time into the backwards compatibility over the years, trying to get everything to work as smoothly as possible, updating versions, making sure 2.53 and DOSBox have a chance of working, etc.  Too many hours to count honestly.  I have also been in touch with the AGN Devs trying to get this to work.  If he's not a dev or using an alt, it's kinda like rent-a-modding, on something I've put hundreds of hours into.  Sorry if I'm short, but I found it disrespectful, and until 1.00+ compatibility is put in, it really can't be fixed without me directly saving it as in 2.50+,

 

 

Would it be possible to make a version to work in 2.5.3? I'm sure it's possible...

I updated New Quest 2013 if you're interested in that to an "as is" version and put the 1.92 B 182/3 version back up so it will work in that version.  I have no plans to convert the (1.02 to 1.84) or 2003 to 2.53, but I will test the new versions to try our best to get it compatible.

 

-James


Edited by Nightmare, 29 August 2017 - 06:31 PM.


#7 Timelord

Timelord

    The Timelord

  • Banned
  • Location:Prydon Academy

Posted 29 August 2017 - 07:23 PM

I just wanted to know if you were aware of the following:
 
We would appreciate bug reports on any of the following:

  • Playing quests made in 1.92, 2.10, 2.50.x and reporting any compatibility bugs.
They may be willing to work with you on fixing the damage.  (Unless you've already tried this.)

 
This falls into the realm of 'may be possible for 2.60+'. The lack of available source code for 1.84 is a roadblock, and the format of quests changed extensively since the 1.xx era. It may fall under the header of 'limited support', as a full conversion, even from 1.90 quests, to modern formats can introduce issues in the quests.
 
There has been some attempt to allow loading pre-1.90 quests in modern ZC, but it's hard to say what the end-result may be, or if it makes the cut for a release version. 1.84 and earlier had their own quest encryption format, too.
 
I did the barest bit of initial preparation work for a 1.xx Import function. if you want to compare the routines (to the 2.50.x branch, or the master branch on GitHub), here, have fun:
 
Spoiler

Edited by ZoriaRPG, 29 August 2017 - 08:09 PM.


#8 Evan20000

Evan20000

    P͏҉ę͟w͜� ̢͝!

  • Members
  • Real Name:B̵̴̡̕a҉̵̷ņ̢͘͢͜n̷̷ę́͢d̢̨͟͞
  • Location:B̕҉̶͘͝a̶̵҉͝ǹ̵̛͘n̵e̸͜͜͢d҉̶

Posted 29 August 2017 - 07:33 PM

I've put a lot of time into the backwards compatibility over the years, trying to get everything to work as smoothly as possible, updating versions, making sure 2.53 and DOSBox have a chance of working, etc.  Too many hours to count honestly.  I have also been in touch with the AGN Devs trying to get this to work.  If he's not a dev or using an alt, it's kinda like rent-a-modding, on something I've put hundreds of hours into.  Sorry if I'm short, but I found it disrespectful, and until 1.00+ compatibility is put in, it really can't be fixed without me directly saving it as in 2.50+,

 


-James

It's not at all like rent a modding. He was trying to help you save your project. Don't turn around and bite helping hands, no matter how irate you may be that your stuff doesn't work anymore. Best of luck salvaging what's usable from the wreckage. I'd suggest trying to export the maps in 2.5x and importing them in the newest version, for starters.


  • ShadowTiger, SofaKing and Demonlink like this

#9 Nightmare

Nightmare

    Original ZC Tester

  • Members
  • Real Name:James
  • Location:Jackson, NJ

Posted 29 August 2017 - 08:14 PM

It's not at all like rent a modding. He was trying to help you save your project. Don't turn around and bite helping hands, no matter how irate you may be that your stuff doesn't work anymore. Best of luck salvaging what's usable from the wreckage. I'd suggest trying to export the maps in 2.5x and importing them in the newest version, for starters.

 

Evan, it's not that.

 

1.  The devs and I have put a lot of time recently into doing this backwards compatibility issue.  We have gone over every little possibility, on some of the oldest (and debatably some of the hardest) quests on the database, when I have to beat these quests with barely any help, any guide,or anything.

 

2.  I have a lot of quests, and it's getting very, very hard to upgrade every single version and keep them working.  I update these things for a reason.  I know some people didn't particularly care for New Quest Rebuilt, but it had to be done.  Some flaws came out during the development of New Quest DLC version (which were cancelled) which made the 2013 version very unstable and was getting less so by the day.

 

Just a revisionist's history on New Quest's original engine version alone (and this doesn't include James Quest, Memorial Quest, New Quest 2, or discontinued quests):

 

1.  New Quest 1.02 - 1999

2.  New Quest 1.84 (conversion)

3.  New Quest 2003 - B182 - 2003/4

4.  New Quest 2.10 (conversion)

5.  New Quest 2.50 (conversion)

6.  New Quest 2013 - 2.50 - 2013

 

As each version upgraded, new flags got updated, and some of the cores got unstable.  I was expecting 2003 to die sometime soon, and in 2.53, it finally did.  It's totally unplayable.  2013 works for now, IDK for how long (2.54 could be it for that).  Rebuilt was made so that the quest would last into future ZC's and still work as the other versions die out.

 

It is to my understanding that a lot of people still love the 2003 version (especially older players), but sometimes developers (whether quests or coders) have reasons for what they do, and are privy to things that the players don't know.  It also takes a tremendous amount of time to update stuff, and I can't be doing it every 2 months for every little quest.  I have other things I need to do with my life, maybe move onto other projects?  The last thing I want to do is make another god damned remake of NQ 2003.  I am sorry if that offends people.

 

3,  Zoria stated a lot of the issues I'm having in his previous post.  This is why it's dead for now.  If something changes I will gladly let you know.  If someone is REALLY interested in porting New Quest 2003 to 2.53 without any changes, be my guest.  I'll playtest it and make sure everything works.  But I'd rather focus on the old versions being played on DOSBox emulator like Nintendo games are or on 1.92 B 183 Windows (which is still available) which would probably please the type of people looking for old versions (like speedrunners and absolute purists) more.

 

-James


Edited by Nightmare, 29 August 2017 - 08:40 PM.


#10 Timelord

Timelord

    The Timelord

  • Banned
  • Location:Prydon Academy

Posted 29 August 2017 - 08:32 PM

To clarify something, to everyone, the mapdata format also changed from 1.xx to 2.xx. You cannot import a map from< 1.90, into 2.50. Adding routines to permit this is something that is probably worth doing, but it is not a high priority because of both the relatively small sample size of quests for these old ZC versions, and the lack of source files.

(Doing data analysis on quest files, to figure out the size and distribution of bits is the last resort for this type of thing.)

Let's compare mapdata:

1.50
 
typedef struct mapscr150{
// 48-byte header
  byte valid,guy,str,room,        item,catchall,warptype,flags;
  byte warpx,warpy,stairx,stairy, itemx,itemy,color,enemyflags;
  byte door[4], warpdmap,warpscr,exitdir,flags2;
  byte enemy[10],pattern, warptype2,warpx2,warpy2,path[4];
  byte warpscr2,warpdmap2;
  word under;
  byte unused_data[2];
// 352 bytes of screen data
  word data[16*11];
// 400 bytes total
};



2.50



See the issue there? :P
 
All of the data in the quest files is stored in a linear manner, and must be extracted in precise order, and put into the correct memory locations. If it is off, by even one bit, the output is corrupted. making loaders for each format is not a trivial matter. hell, even now, 2.50 quest map export and import has bugs with its own format. :(

Edited by ZoriaRPG, 29 August 2017 - 08:33 PM.

  • Nightmare likes this

#11 Deedee

Deedee

    Bug Frog Dragon Girl

  • Moderators
  • Real Name:Deedee
  • Pronouns:She / Her, They / Them
  • Location:Canada

Posted 29 August 2017 - 10:04 PM

Are you "even on ZC development staff"?  Most of the staff is well aware of what I'm testing and 1.02 compatibility is not on the list at the current moment.  I'd consider this message rather trollish if you're not.

 

-James

Jeez, no need to be a dick about it. The guy was just trying to help.

Also, you aren't on the dev team either. 100% backwards compatibility is a fairly high-priority goal, and saying otherwise is just being dishonest.


  • KingPridenia likes this

#12 Nathaniel

Nathaniel

    Deified

  • Members

Posted 29 August 2017 - 10:14 PM

Jeez, no need to be a dick about it. The guy was just trying to help.

Also, you aren't on the dev team either. 100% backwards compatibility is a fairly high-priority goal, and saying otherwise is just being dishonest.

 

As much as I agree with others on Nightmare's attitude in this thread, the first part of your post, specifically the name calling, was unnecessary.  Others were already essentially telling him the same thing, only in more articulate ways.  There should be no intention here to dogpile.

 

As for anybody else who is tempted to do the same, let's try to keep this thread on the right track.


  • David likes this

#13 Timelord

Timelord

    The Timelord

  • Banned
  • Location:Prydon Academy

Posted 30 August 2017 - 12:47 AM

Jeez, no need to be a dick about it. The guy was just trying to help.

Also, you aren't on the dev team either. 100% backwards compatibility is a fairly high-priority goal, and saying otherwise is just being dishonest.


While this is certainly true, the spec is for 100% compatibility with 1.90, 1.92 (all major betas), 2.10, 2.10.1, 2.10.2, and 2.50.0->2.50.2.

1.84 and earlier, 2.50 betas, and some minor stuff that is specific to 2.50.3 was specifically not included in that specification, for various reasons. The most notable, is the lack of the original source code for these old builds from 1 years ago.

Those of you who have been around long enough, may remember that versions 1.0 through 1.84 all came out within the span of about one year. Phantom Menace produced v1.0 through v1.82, and retired in January 2001. War Lord took over from there, alone, and produced ZC until the 2.11 era. He was the only one with sources for versions between 1.83 and 1.90, and sources for 2.91 through 2.50.0 are still mostly unavailable. (I would like to see this resolved, too, and those sources handed to everyone involved.)

We never discussed 1.00, 1.50, 1.60, 1.7x, 1.82, 1.83, 1.84 or any of the interim releases from 2000. When PM stopped working on ZC (v1.82), the source passed to War Lord. At this time, he has no idea where that source would be, if it exists at all. That means that full compatibility with these versions would be very difficult, and probably spotty.

I would like to see 1.84 compatibility, at least, in the form of being able to import 1.84 quests in ZQ and save them. If 2.53->2.60 can play 1.84 quests, that is even better. I have the source for 1.00 and 1.50, and even with that, adding 1.00 and 1.50 quest loading is going to be a challenge.

One possible option, may be a standalone quest converter, that produces a new quest file for the most current version of ZQuest, but an issue with updating old quests in this manner, is that it may mean allowing anyone to edit them. I do not know how critical an issue that may be for the lot of you.

Really though, if you look at the 1.00 and 1.50 structs, and quest format, and if you consider that there are some packfile changes in allegro--remember, these old versions used allegro 1, 2, and 3--and that the password format was different, it's sort of a nightmare (no pun intended) to add this stuff.

At present, the highest priority is to sort out the bugs in 2.53, and make it rock solid, to use as a foundation for the next two or three interim releases until 2.60 is ready. The way this will work, is that features that are added to master that are known to be retained, will be backported to 2.50.x, producing new versions. The first of these, 2.54, will be the initial build to add truly new features.

2.54 will primarily be a ZScipt update, whereas 2.55 will likely be the one that adds new editor features. I'll be working on the specs for these in the autumn and early winter, but much of the new ZScript (in the extant pointers and classes) can begin migrating into this codebase.

Adding 1.xx quest importing might be possible along the way, but I will need cooperation and assistance across the board. THe fact that James is willing to spend a lot of time testing what versions can read old quest files, and what quest versions have bugs, and documenting the issues, goes a long way toward making this viable.

I'm not much of a fan of the banter on the subject though. I'd rather see constructive discussion on this topic, than to start ranting on it, accusing people, and devolving this into a long list of idiotic name calling. If adding this kind of feature--which is in fact, quite hard to do--amounts to no more than a huge bickerfest, then no-one is going to want to be involved.

All of us have limited time, and I;m no exception. I spent several hours today going over the 1.xx sources that I have, and examining the routines. I even went as far as to start piecing together a makeshift makefile to try to build 1.50, which is not something that I truly love doing, but it may be needed so that it is possible to create 1.50 quests to use as validation files foe an import function.

If any of you want to assist with this endeavour, that would be fantastic, but this topic is probably best removed to its own thread.

Edited by ZoriaRPG, 30 August 2017 - 12:49 AM.


#14 Ryunaker

Ryunaker

    Junior

  • Members

Posted 30 August 2017 - 09:43 AM

Just to let you know, I had not intended to 'rent-a-mod', or anything along those lines, nor was I trying to be a troll.  I was not aware that you were already working with the devs, and I wanted to make sure you were aware that they seemed to be interested in doing what they could to keep old projects alive.  I am sorry that my attempt to help seems to have been taken the wrong way.


  • strike likes this

#15 Nightmare

Nightmare

    Original ZC Tester

  • Members
  • Real Name:James
  • Location:Jackson, NJ

Posted 30 August 2017 - 10:28 AM

Just to let you know, I had not intended to 'rent-a-mod', or anything along those lines, nor was I trying to be a troll.  I was not aware that you were already working with the devs, and I wanted to make sure you were aware that they seemed to be interested in doing what they could to keep old projects alive.  I am sorry that my attempt to help seems to have been taken the wrong way.

Apology accepted.  Sorry for blowing up on you, just the time I've put into this is immense, and my frustration came out.

 

Maybe we'll get a one-time deal of 1.84 released stuff if this works well.  Let's hope.

 

-James


Edited by Nightmare, 30 August 2017 - 10:30 AM.

  • Nathaniel and Anthus like this


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users