Don't hardcode animation names

[mrwonko]

I believe the animation names (BOTH_STAND1 etc.) are hardcoded. That's why there's BOTH_CIN* for level-specific cinematic animations. It would be nice if the names were not hardcoded, and you could just add a new one by listing it in animation.cfg.

The .ibi format does not need to be changed, the animation names are saved as strings in there anyway. It's not until ingame that they're presumably turned into an enum.

[eezstreet]

I concur.

Sent from my Windows Phone

---

From: Willi Schinmeyermailto:[email protected]
Sent: ‎4/‎12/‎2013 7:53 AM
To: Razish/OpenJKmailto:[email protected]
Subject: [OpenJK] Don't hardcode animation names (#92)

I believe the animation names (BOTH_STAND1 etc.) are hardcoded. That's why there's BOTH_CIN* for level-specific cinematic animations. It would be nice if the names were not hardcoded, and you could just add a new one by listing it in animation.cfg.

The .ibi format does not need to be changed, the animation names are saved as strings in there anyway. It's not until ingame that they're presumably turned into an enum.

---

Reply to this email directly or view it on GitHub:
#92

[dusty22]

Would this mean you could add new animations without having to code new slots?!

[eezstreet]

Yes.

Date: Fri, 12 Apr 2013 14:54:08 -0700
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [OpenJK] Don't hardcode animation names (#92)

Would this mean you could add new animations without having to code new slots?!

—
Reply to this email directly or view it on GitHub.

[mrwonko]

Though without coding they could only be used in Cutscenes.