What's been added/fixed:
1. Fixed the bug where activating a trigger with a pushblock turned all infinite pushblocks on that screen (maybe everywhere on the DMap or possibly in the game, haven't checked yet) into push-once blocks.
2. Added the ability to have more than one trigger block so you have to activate all of them to activate a secret.
Currently being added/modified:
1. Pulling the CSet information out of the mapscreen data block and placing it in its own area. For those of you who are programmers out there, here's how the combo information is set up on map screens:
Each combo is a word (unsigned short, 2 bytes in size, 16 bits). Originally, the bits of the combo were set up in this fashion:
fffffssscccccccc
A long time ago, the first 5 bits (the f's) were the map flags. 2^5=32, so the maximum number of available map flags you could have were 32. As you know, we are now up to 60-something. This was accomplished by moving the map flag information into its own separate area. By giving the flags a full 8-bits (each flag now takes up one byte), you can have 255 flags (flag 0 is considered to not be a flag). So, we still have a setup like this:
xxxxxssscccccccc
The next 3 bits (the s's) are the CSet bits. 2^3=8, so you can theoretically use 8 different CSets on one map. Granted, ZC puts a restriction so there are only 6 available, but that takes up as much space as 8.
Now, by moving the CSet information into it's own area, that frees up those 3 bits. Plus, it gives the CSet information room to grow. So, in the future, one could theoretically have 256 CSets to choose from.
So, after moving the CSet information out of the combo data, we have the following setup:
xxxxxxxxcccccccc
So, you have 8 empty bits and 8 bits that are used for the actual combo data. When a combo is drawn, the combo page for that screen is multiplied by 256 and added to each combo number on the screen. Since the highest combo page we are offered is 63 and the highest combo number we can have is 255, the highest combo that would be drawn is 16383, which is the highest combo number in the full combo list.
Now, suppose we allowed you to set a combo page for each combo you place on the screen. We have the space for it, since the combo numbers currently only take up 6 bits. Now, programatically, storing the combo page in the first 6-8 bits of each combo is the same as doing away with combo pages altogether and just storing the full combo number in each combo.
This is what I am tyring to accomplish.
Currently, I am about half-done pulling the CSet information out and storing it in a different location. More than likely, I will compile Beta 133 (before any of the CSet extraction work began) and let all of you test it tomorrow morning while I try to get this feature working. If successful, this will be the single most important feature (in my opinion) since animated combos.
