Amidweiz, now that's what I'd like to see more - fully designed feature request with explanation how it should work internally. If you upload a sample stage that could be used for tests (with stageIntroCtrlID already set and BGCtrl coded to display something before the characters have statedef 5900 assigned and internal lifebar counter starts) I think I will be able to handle the implementation.

As for the second part I think the more flexible approach would be treating stage somewhat like a character, so that it can use CNS, AIR, SND files referenced in stage DEF file, which would open gate for proper stage interactivity:

Code:

[Files]
st      = somename.cns           ;States
anim    = somename.air           ;Animation
sound   = somename.snd           ;Sound

With this in place it would be a matter of controlling actual characters behavior via stage cns code instead of depending on fightfx air and tons of new stage parameters. For example if stage has stageIntro = 1 parameter set than characters are not forced into statedef 5900 at the start of the round - they wait for stage to control them and change their state to 5900. Should be doable with my current understanding of the engine (I hope)

K4thos said, June 13, 2018, 04:24:45 pm

Amidweiz, now that's what I'd like to see more - fully designed feature request with explanation how it should work internally. If you upload a sample stage that could be used for tests (with stageIntroCtrlID already set and BGCtrl coded to display something before the characters have statedef 5900 assigned and internal lifebar counter starts) I think I will be able to handle the implementation.

As for the second part I think the more flexible approach would be treating stage somewhat like a character, so that it can use CNS, AIR, SND files referenced in stage DEF file, which would open gate for proper stage interactivity:

Code:

[Files]
st      = somename.cns           ;States
anim    = somename.air           ;Animation
sound   = somename.snd           ;Sound

With this in place it would be a matter of controlling actual characters behavior via stage cns code instead of depending on fightfx air and tons of new stage parameters. For example if stage has stageIntro = 1 parameter set than characters are not forced into statedef 5900 at the start of the round - they wait for stage to control them and change their state to 5900. Should be doable with my current understanding of the engine (I hope)

Sounds good, I'm going to send you the stage that was shown MangeX's video and the one I initially shown (CVS Pro Train stage and KOF 95 Garou stage). The Train stage for the stage intro (It's not the best example of a stage intro but it is one) and the Garou stage for the water effects and possibly the movement (as shown in the video I first showed for the request https://youtu.be/lTMwD9ybSAQ?t=9m2s ) here is the link to them two http://www.mediafire.com/file/2hj6lnnk7hpihag/stages.rar . I'll see if I can make a mock implementation for the other requests later

		if err := c.paramValue(is, sc, "anim",
			stateDef_anim, VT_Int, 1, false); err != nil {
			return err
		}

More Arcade stuff as I wait for the SP support.

Spoiler, click to toggle visibilty

[youtube]https://www.youtube.com/watch?v=PmwwK9PmVEE[/youtube]

 ; - 1, 2, 3, ... (rivals)
 ;   IKEMEN feature: The parameter alters standard arcade order system and other
 ;   default match settings, allowing to force pre-defined matches along the
 ;   way. paramname refers to arcade match number (for example 4 = 4th match).
 ;   paramvalue, enclosed in {} brackets, follows the same syntax as adding a
 ;   new character with optional stage assignment and accepts following optional
 ;   char parameters: music, musicalt, musiclife, zoom, ai, winscreen, rounds,
 ;   time, lifebar, onlyme. If 'onlyme' parameter is not set and you're playing
 ;   in team mode the referenced character becomes the opposite team leader, and
 ;   other characters follows order settings. Chars and stages referenced here,
 ;   if not already present in [Characters] and [ExtraStages] sections as
 ;   separate entries, won't be selectable in select screen.
 ;
 ; - maxmatches
 ;   IKEMEN feature: This parameter makes the character ignore default
 ;   *.maxmatches settings under [Options] section and assign different ones
 ;   instead, allowing you to set up custom maximum number of matches to fight
 ;   before game ends in arcade mode, as well as order priority. paramvalue is
 ;   used as a prefix to the original names of these settings, followed by dot,
 ;   so the new entries added under [Options] section should look like this:
 ;   'paramvalue.arcade.maxmatches', 'paramvalue.team.maxmatches'.

The dialogue stuff can't be done like that anyway, as I want the characters to share the palette they are using, so it must be within the character.

rival1 = "1, 1, 1, {Geese Howard. What is your connection with Shadoldo? How are you affiliated with Bison. I'm taking you in for questioning.}, 2, 1, 1, {Geese reply}"

[State 190, vs Geese]
type = rivalquote
trigger1 = enemy, name = "Geese"
value = 1