 |
You can set a separate image with 'exitpic =' for the 'finished' screen. |
|
|
I already define exitpic for each map - exitpic defines what image to show behind the kill-count screen, and cant be used for what I requested. I'll try to explain it better. I'd like to be able to put together more links to the "chain" between two levels - say 1: Kill-count screen (exitpic) (player press use) 2: World map showing where you've been and where to go (enterpic) (player press use) 3: A Large image for the next map in line is displayed with the name of the map on top (enterpic) (player press use) 4: Story text for the next map is displayed (cluster entertext) (player press use) 5: Map start Currently 2 and 3 both use the same lump, and can't be combined. One can't extend the use within the lump to do more actions - and one can not define enterpic lump to jump to a second enterpic lump. I'd like to be able to do so (jump from enterpic lump to next with something like Link = ... just as you can when defining intermission's for the end-game. |
|
|
So you want an entirely new screen added into the sequence? I don't think I'll do that before exporting that entire module to scripting, but that may take a while. |
|
|
I don't know so much about the technicality behind it, but what I want is to be able to define two enterpics to come one after the other - so no "new" lump-type or so, but the ability to tell at the end of a enterpic-lump that it should jump to another enterpic-lump (in theory this would allow to go between many enterpic-lumps with different content before moving on to the next map.) From the above list I originaly have 1-3-4-5 - while after starting to produce the world-map I now have 1-2-4-5 since 2 and 3 needs the same lump and can't be combined inside the same lump. (they are both enterpic). The scripting what does it mean? it's the new zscript setup? Can it be combined with the old decorate/mapinfo etc.? or would it require a full rewrite of all lumps for me to implement it? Any finger in the air guess on how long a while is? 3 months - a year? :) Just good to know how I should plan progress - I'm hoping to be done by summer with the second episode for a release - but I hoped that last February also - so who knows :) |
|
|
It means that the code as written cannot do what you want, it would reqiure some major redesign. And I'm not going to do this unless the code for these screens has been completely ported to ZScript. |
|
|
Yes that makes sense to not do the same job twice when things are anyway going zscript. What I ment to ask is when the new zscript is up, and if this is then implemented - will it be compatible with the old stuff? Like can I use some lumps that use zscript, while all the old lumps I use is not zscript? :) (meaning I would not have to rewrite decorate etc. for zscript. |
|
|
With the scriptified version of the status screen this is now doable, but since the new screen you want to add doesn't even exist (and I have no idea what it should contain) you are mostly on your own here. The main trick will be that you need to add another state, so that the screen does not change immediately from CurState == StatCount to CurState == ShowNextLoc, but to an intermediate new one. This will amount to a non-trivial amount of coding, though, because it's entirely new functionality. |
|
|
Ah ok thanks :) I'm familiar with all the Decorate code (old code) but not at all with the new code which makes no sense to me at all, so I'll try to find an appropriate forum to see if I can find some help for that - or a place to learn what the code does. The line you just wrote means absolutely nothing to me at the current time =) |
- Anonymous
