This is it. No betas, no release candidates. See shardstorm.com (since build 1703) for changes since 2.50.1.
Downloads
Printable View
This is it. No betas, no release candidates. See shardstorm.com (since build 1703) for changes since 2.50.1.
Downloads
I just want to know if there's script or quest compatibility issues or if the old statue behavior can be re-enabled via a quest rule.
https://www.youtube.com/watch?v=_J6-3l3hCm0
Now if we can all just agree on what to do on encryption or those who disagree with the majority take a vow of silence we can finally open source this. "Provided we don't have a consensus yet."
Note that the text above is a joke, and I've received a PM confirming a general consensus yesterday.
That's nes behavior, so it will probably be found in NES Fixes
I can't say it occurred to me that it would be a compatibility issue. But I suppose the peahat thing was, too, somehow...Quote:
Originally Posted by Anarchy_Balsac
I guess I can add that. We can't put many more rules in 2.50.x, though. There's only one byte left for them.
Actually I'm currently brain storming on doing something rather interesting about this, 2.50.x can use the quest rules that no longer exist however, there's a slight problem and it's a pain in the ass.
Problem: Backwards Compatibility
Solution: We use the deprecated constants from the enum when we run out of room however these have a purpose as they configure how the quest works until you load it ZQuest 2.50.x. That being said they pretty much become worthless at that point and we have access to them as they serve no purpose in builds after they are removed.
The problem is that things like that can seriously screw with the quest makers ability to challenge players.
@Anarchy_Balsac
Provided this is directed at me and not saffith, actually you cannot activate the deprecated quest rules in 2.50.x. They only exist for backwards compatibilty. THe ones that gave us sparkles and disabled sword beams for example still exist in quest rules.
1. Check the quest's version number to enable old feature or new feature when loading it quest in player.
2. In the editor when a older quest is loaded it must be manually saved now, as it always should be. And it re-configures the quest rules and data for the quest. "Whether sparkles are set up not for example. that was a quest rule back in the day. Actually it was four"
3. We now have access to more bits for quest rules.
Note that will be a long a tiresome process, and I sure in hell ain't started on this until we get this stuff open-sourced. Shouldn't be too much longer though.
It was directed at Saffith, LOL. But from what I gather, there is not currently a way to re-enable the old statue behavior.
That rule should be called "Benevolent Statues". :P
Actually, it might be better as an enemy misc value.