Quote

1. Tag functions built into the engine
I feel that it would benefit to just have a SCTRL of this rather than have to fiddle around with uno tag (even though it's pretty good as it is) and such. Maybe have options upon how the tag works  like is it following tekken tag rules, (when a character gets KOed the team loses the round rather than the partner coming out) are the characters jumping in or running in, can they attack while tagging, do they have to be in a specific spot to tag in (Like Kizuna Encounter https://youtu.be/U77h27eSa8U?t=15s), etc.

Quote

1. Yes it's doable (I even said uno tag in my post so I know it's doable) but I feel it would be better as a dedicated SCTRL that could be just inserted into a common1 file or even a dedicated play mode rather then having a separate piece of code which requires patching and such.

All of this is already implemented in latest GO build.

1. Tag mode is selectable from select screen the same way as Single, Simul and Turns (if you add new teammenu.itemname.tag parameter to screenpack DEF file) which makes all the characters in your team being controlled by player (or in case of side controlled by CPU - not, obviously) and sets value for trigger.


2. There is a new TagMode trigger that you can use in CNS files to detect if the tag mode has been selected. Example use:

Code:

Root,TagMode=1
Enemy,TagMode=1

I don't know why you mentioned SCTRL. What should it do? If you mean hardcoding tag behaviour in source code than I don't think it's a good idea compared to leaving details that you have mentioned to cns code. If all this tag related stuff is handled via cns than mugen authors can easily distribute different systems.

3. 2 new buttons are supported that can be assigned for example for tagging if you don't want to use buttons combinations. They don't need to be declared in character's CMD file, since the declaration exists in the below mentioned common.cmd:

Code:

[Command]
name = "v"
command = v
time = 1

[Command]
name = "w"
command = w
time = 1

4. There are new common files for AIR and CMD. For CNS stuff common code can be added to the already existing common1.cns

5. Patching characters like in add004 and Uno is NOT needed. Ikemen GO Plus added 3 new negative states that works the same way as -1 (Command Control), -2 (Always), and -3 (Self) with higher priority than above ones, so all you need to do is adding Tag code to common1.cns
edit: unlike mugen, in Ikemen GO Plus you can now repeat -1, -2, -3 statedef declaration in common1.cns and those states will work even if character already has negative states declared in CNS files (they will be appended on top of character ones), so all you need to do is adding Tag code to common1.cns

6. As you can see in the above screen up to 4vs4 players in Tag mode is supported by default.

If there is something missing that would make coding Tag systems easier than we can think about it - but please, be specific, I don't know much about mugen CNS files. (I never created anything for mugen)

What is missing is the actual common1.cns Tag code that could be used as a base and distributed with the engine. For now add004 system is used (as mentioned characters don't need to be patched in order to work with it in Ikemen GO Plus), but in future we're planning to distribute simpler Tag code (without all lifebar related stuff and custom systems like dizzy etc. that exists in add004). JustNoPoint kindly offered to work on the cns tag code.

------------

I will answer other questions when I have more time.

edit:

Quote

2. Offical 3v3 and 4v4 simul support
Even though I am not a fan of this mode, plenty of people are and it would bring attraction towards this engine just becuase of that. Stages would have to have their own p3 and p4 triggers repectivly. (like p3startx = , p4startx =, etc) You could also apply this to the tag fuction above.

It's already supported by default for all team modes:

not sure if p3startx and p4startx stage parameters are needed considering they don't exists in mugen and yet 2vs2 matches (which means with p1, p2, p3 and p4 on screen) are a thing. Isn't there some other parameter that handles distance between players at the start of the match?