XML talk:StNA - Revision history

Iritscen: moving talk here from main page

2021-03-30T13:38:37Z

moving talk here from main page

← Older revision		Revision as of 13:38, 30 March 2021
Line 1:		Line 1:
			==Unused types==
			If unused types are still recognized by engine we could try to apply new animations to them. For example additional throws with Thrown9, Thrown14, and Thrown17.

			==Console_Punch==
			* KONOKOconsole_punch (35 frames) is a stretched KONCOMcomb_p clone (16 frames)
			* the game doesn't use this file so the type could be also considered as "unused"
			* the question remains what this animation was used for; Loser suggests that it was "probably meant to be used for [[XML:BINA/OBJC/CONS#tags\|''pushbutton'' type of consoles]]"

	==Anim types bound to user input==		==Anim types bound to user input==
	Stages of type assignment:		Stages of type assignment:

Paradox-01 at 09:05, 28 July 2019

2019-07-28T09:05:31Z

← Older revision		Revision as of 09:05, 28 July 2019
Line 1:		Line 1:
	==Anim types bound to user input==		==Anim types bound to user input==
	Stages of type ~~assinment~~:		Stages of type assignment:

	'''User input detection'''		'''User input detection'''

Paradox-01 at 08:51, 28 July 2019

2019-07-28T08:51:21Z

← Older revision		Revision as of 08:51, 28 July 2019
Line 81:		Line 81:
	Besides finishing this table, a further objective could be to create graphics with combo and state cycles, like running and walking cycles.		Besides finishing this table, a further objective could be to create graphics with combo and state cycles, like running and walking cycles.

	In theory visual representation of states cycles allows a modder to ~~diggest the~~ crucial information when he wants to create new animations and/or cycles.		In theory visual representation of states cycles allows a modder to quickly digest most crucial information when he wants to create new animations and/or cycles.

Paradox-01 at 08:37, 28 July 2019

2019-07-28T08:37:58Z

← Older revision		Revision as of 08:37, 28 July 2019
Line 72:		Line 72:
	\|Kick3		\|Kick3
	\|-		\|-
	\|fw (accumulated: k, k, k + fw)		\|k + fw (accumulated: k, k, k + fw)
	\|previous type within timeframe: Kick2		\|previous type within timeframe: Kick2
	\|Kick3Fw		\|Kick3Fw

Paradox-01 at 08:37, 28 July 2019

2019-07-28T08:37:21Z

← Older revision		Revision as of 08:37, 28 July 2019
Line 79:		Line 79:
	[...]		[...]

	An further objective could be to ~~finish this table for creating~~ graphics with combo and state cycles, like running and walking cycles.		Besides finishing this table, a further objective could be to create graphics with combo and state cycles, like running and walking cycles.

	In theory visual representation of states cycles allows a modder to diggest the crucial information when he wants to create new animations and/or cycles.		In theory visual representation of states cycles allows a modder to diggest the crucial information when he wants to create new animations and/or cycles.

Paradox-01 at 08:35, 28 July 2019

2019-07-28T08:35:30Z

← Older revision		Revision as of 08:35, 28 July 2019
Line 15:		Line 15:
	Since there are also some TRAM files for prone mode, sitting and hiding against a wall, we can assume some geometry awareness (edge detection) - at least during the game dev stage.		Since there are also some TRAM files for prone mode, sitting and hiding against a wall, we can assume some geometry awareness (edge detection) - at least during the game dev stage.

			For sit animations the Action event was probably used in FURN context as it belongs to CJBO just like the other interactive objects CHAR, CONS, DOOR, PWRU and WEAP.

	~~For sit animations the Action event was probably used in FURN context as it belongs to CJBO just like the other interactive objects CHAR, CONS, DOOR, PWRU and WEAP.~~

	;For anim types, the series of anims is hardcoded. This is usually important for combos.		;For anim types, the series of anims is hardcoded. This is usually important for combos.

Paradox-01: This table requires quite some diligence and research for less known types. However we don't have many active modders, making this a non-priority 'construction site'. For now, most "added value" was realizing that there is a "context check".

2019-07-28T08:34:24Z

This table requires quite some diligence and research for less known types. However we don't have many active modders, making this a non-priority 'construction site'. For now, most "added value" was realizing that there is a "context check".

@@ Line 1: / Line 1: @@
 ==Anim types bound to user input==
-For anim types, the series of anims is hardcoded. This is usually important for combos.
+Stages of type assinment:
 :mouse left - StandingTurnLeft
 :mouse left - CrouchTurnLeft (obsolete, because can be replaced by StandingTurnLeft and anim will still play)
-:...
-: p => Punch
-: p, p => Punch2
+: crouch => in air? => Flip
-: p, p, p => Punch3
+<Flags>InAir
-: p, p, k => PPK
+: none/space => <FromState>FlyingBack? => Fly
-: p, p, k, k => PPKK
+<Flags>InAir
-: p, p, k, k, k => PPKKK
-: p, p, k, k, k, k => PPKKKK
+-->

Paradox-01: Anim types bound to user input, WIP

2019-07-27T11:47:50Z

Anim types bound to user input, WIP

New page

==Anim types bound to user input==
For anim types, the series of anims is hardcoded. This is usually important for combos.

: key strokes => Type
:mouse left - StandingTurnLeft
:mouse left - CrouchTurnLeft (obsolete, because can be replaced by StandingTurnLeft and anim will still play)
:...
: p => Punch
: p, p => Punch2
: p, p, p => Punch3
: p, p, k => PPK
: p, p, k, k => PPKK
: p, p, k, k, k => PPKKK
: p, p, k, k, k, k => PPKKKK
: c => Kick
: c, c => Kick2
: c, c, c => Kick3
: k, k, fk => Kick3Fw
: ...