How do i add a custom warning that uses my custom font?

[NiftyAC]

I want the warning to appear before you get to the title screen and just say that it has flashing lights but I don't know how to make it actually appear and work correctly. I'm not good with the redirects or putting any custom states, especially not before the title screen. I'm using the mods folder if that changes anthing.

[r6915ee]

I assume you're using the current version of Codename for this.

There's typically a flag in the modpack configuration for disabling the warning state that gets included when Codename generates the configuration under data/config/modpack.ini, listed under DISABLE_WARNING_SCREEN. You can simply set that to false to enable the warning state.

If I remember correctly, Codename includes a way to directly interact with the vanilla states instead of using custom ones using generic callbacks that may be of use to simplify the process. Do note that they're not the same as state redirects and function more like stage scripts:

	State Scripts	State Redirects
Description	Manipulate state data assigned, like a stage script	Point states to ModStates, instead of vanilla
Usage	Name a script under data/states/ the same filename as the state's class	Add a flag of the state name to the mod configuration and assign it a string literal, containing the filename of the script for the custom state

In modern Codename, the warning state has been renamed to WarningState as the state name. So, you should create a state script as stated above that is under the filename of WarningState.hx In Legacy, you would use BetaWarningState.hx instead, due to BetaWarningState being the state class name.

Using postCreate as the callback, you would modify the variables as you normally would using standard FlxText usage:

function postCreate() {
	disclaimer.text = "poo";
}

Do note, however:

• WarningState has no documentation, so in the extreme case, you would probably need to take a look at the respective Haxe file in the source code. See the (rather tiny) writeup below for the reasoning.
• Do note that the titleAlphabet property relies on the Alphabet interface, like with the Freeplay menu and such. If you want to also modify the font for that, then you need to change the alphabet used itself. Unfortunately, I don't really know how that works, since I haven't had the need to modify it.

WarningState documentation

Codename uses Haxe as its primary language. HScript, which is used for scripting in the engine, can be considered only a subset of Haxe as a programming language. Codename operates a fork of HScript that extends this subset, but it's not by too much.

Haxe is primarily an object-oriented language, in a similar style to C++, but, for those in a Lua-based language background, MoonScript. What I mean is that you don't get the same prototyping system you have as with Lua. You get the standard object-orientation mechanism.

This kind of object-orientation uses accessors or, in Haxe's case, access modifiers, which define how properties and methods can be accessed. By default, Haxe makes properties and methods without a visibility access modifier specified use the private access modifier, which makes it so that the respective property can only be used and modified by the class internally. The public access modifier allows usage of these properties from anywhere when referring to objects. The static access modifier has the function operate on the class itself instead of the object, but that's not relating to the problem.

The reason why the WarningState documentation is empty is because everything relies exclusively on the private access modifier. This makes it so that the program responsible for generating the documentation won't display these properties by default, due to that being the current configuration. Besides that, no documentation comments exist for these properties internally.

[NiftyAC]

I assume you're using the current version of Codename for this.

There's typically a flag in the modpack configuration for disabling the warning state that gets included when Codename generates the configuration under data/config/modpack.ini, listed under DISABLE_WARNING_SCREEN. You can simply set that to false to enable the warning state.

If I remember correctly, Codename includes a way to directly interact with the vanilla states instead of using custom ones using generic callbacks that may be of use to simplify the process. Do note that they're not the same as state redirects and function more like stage scripts:

State Scripts State Redirects
Description Manipulate state data assigned, like a stage script Point states to ModStates, instead of vanilla
Usage Name a script under data/states/ the same filename as the state's class Add a flag of the state name to the mod configuration and assign it a string literal, containing the filename of the script for the custom state
In modern Codename, the warning state has been renamed to WarningState as the state name. So, you should create a state script as stated above that is under the filename of WarningState.hx In Legacy, you would use BetaWarningState.hx instead, due to BetaWarningState being the state class name.

Using postCreate as the callback, you would modify the variables as you normally would using standard FlxText usage:

function postCreate() {
	disclaimer.text = "poo";
}

Do note, however:

• WarningState has no documentation, so in the extreme case, you would probably need to take a look at the respective Haxe file in the source code. See the (rather tiny) writeup below for the reasoning.
• Do note that the titleAlphabet property relies on the Alphabet interface, like with the Freeplay menu and such. If you want to also modify the font for that, then you need to change the alphabet used itself. Unfortunately, I don't really know how that works, since I haven't had the need to modify it.

WarningState documentation

Thank you. I got the state to work and the custom font isn't necessary at all so it works perfectly for what i need. It's sad that the modpack.ini was the last place i would've thought to check😭

[NiftyAC]

I'm getting a problem where after about 39 or 40 characters into the message it turns the text yellow and then turns it back after a certain point.

[r6915ee]

That might be because you're including hashtags (#) in the string literal, which are defined by the default markup used by Codename Engine to color the text yellow. Asterisks (*) in turn color the text red.

If you don't need to use the markup, then use the following to reset the formats applied to the markup in postCreate:

disclaimer.clearFormats();

[NiftyAC]

That might be because you're including hashtags (#) in the string literal, which are defined by the default markup used by Codename Engine to color the text yellow. Asterisks (*) in turn color the text red.

If you don't need to use the markup, then use the following to reset the formats applied to the markup in postCreate:

disclaimer.clearFormats();

Thank you. I was confused because I didn't have hashtags or asterisks anywhere in the WarningState. It works now.