This has been around for a while too. How do you expect this to be backward compatible if it screws up their enemies?
Quests built in older versions of ZC's enemies are still screwed up
Which versions? Which quests? Which enemies?
http://www.armageddongames.net/forums//thread/96342/
this "may" be of interest.
Dark Nation wrote:Which versions? Which quests? Which enemies?
Since there were newer enemies added, the position of enemies changed.
Let's say that Gel is Enemy15 and Goriya is Enemy16. Since the Gel2 was added into ZQuest and placed immediately after the Gel, it became Enemy16 and the Goriya became Enemy17. So, if you used the Goriya (Enemy 16) in 2.10, then playing the quest in 2.11b16c (or such) places there a Gel2 (Enemy 16).
This could be solved with a code, so ZCplayer will recognize that this is an older quest and applies older enemy positions (Goriya will be Enemy 16 again). Or the newer enemies could be added AFTER the older ones, instead of the alphabet order.
However, I don't think any of these will be done: the previous may be hard, the second would be ugly and would destroy the compatibility between the newer betas and the stable 2.5. (especially in the same way which I already mentioned with the Gel-Goriya example)
Send me a quest that does this.
Uhh.... I could dig up my last version of Adventure in Mysteria, if you'd like. Last time I edited it in a 2.11 beta with Save as 2.10 in it, when I checked the enemies, they had changed....
Does this *only* happen when you do "Save as 2.10"? If so, I know what the problem is.
Let me check....
Nope. It does it from the start. I had about 4 or 6 Blue Lynels in a certain screen in Adventure in Mysteria. In 2.11/2.5, they get turned into Bubbles of the Temporary Item-disabling kind.
Same happens when you want to play a 2.10 quest in 2.11b16c or higher. Logically it happens since the first added enemy. Just read my post again (#3 in this thread). Why would this hapen only when saving as 2.10? The enemy placements are other in the newer betas/alphas, but the game places enemies according to enemy number, not enemy name. The game doesn't care that Enemy 16 isn't the same in 2.10 and 2.11/2.5.
I will now play various 2.10 quests in 2.5b142.
EDIT: Confusion! I played 2.10 and older version quests in 2.5b142 and the enemies were right! I don't know how... Rocksfan mentioned once that he had found 3 big circle patras in a certain low level dungeon... In "Fall uh de Honky Pig" I found there 3 blue darknuts. Later he realized that he had been playing in a newer beta. No logic in the world... fortunately.
So, what's the current verdict?
After more research, I have found that build 219 WILL play older quests enemies correctly.
The problem lies with saving as a 2.10 quest. When I saved one of my quests as such, all the enemies were messed up.
CastChaos, it was when I was playing something in beta 16c, which is long since been replaced.
Fixed in the next beta.