Even better!
Even better!
Avatar: Just who the SPAAAACE do you think I am?
Nice mock up *b*. That would work great.
That looks like it would work well!
it should say at the top... play which quest... and give you a choice of original, custom, cancel
Computer specifications:
Windows 10 Pro x64 | Intel Core i7 @ 2.66GHZ | Asus P6T Motherboard | 6GB DDR3 RAM | Integrated Sound | Nvidia Geforce 560 Ti 2048MB PCI-E | Corsair AX760 Power Supply | Thermaltake Armor+ MX case
We've talked about that actually; there are three disadvantages:
1) Quest size. The ZC executable and data files would have to be embedded in the quest.
2) Portability. Currently, all quests can be played on Windows, OS X, Linux, and anywhere else we are able to port ZC. If we have ZQuest publish quests as executables, it would be up to each quest author to generate an executable for every supported platform; I fear most authors would be lazy and OS X and Linux users would get screwed.
3) More files for quest authors to manage. If a quest author wanted to update a quest, he could no longer just download it from a qdb; he'd have to keep the editable version of the quest on his harddrive, and if he loses this version, he's screwed.
Of course an executable quest also has many advantages, so making such a change is worth discussing as a future plan.
How about an option in ag.cfg so that all slots autoload a certain quest file? To the end user, it would appear to be an embedded quest (no need to manually load a custom quest, it becomes the default).
a) add a command line switch so we can load quests straight away
b) config option for default quest
c) new screen as depicted (corrected by me) by *b*
Computer specifications:
Windows 10 Pro x64 | Intel Core i7 @ 2.66GHZ | Asus P6T Motherboard | 6GB DDR3 RAM | Integrated Sound | Nvidia Geforce 560 Ti 2048MB PCI-E | Corsair AX760 Power Supply | Thermaltake Armor+ MX case
There are currently 1 users browsing this thread. (0 members and 1 guests)