//Starting with a ValidatedInt, which characters map easily to, we define validation that bounds the int to the valid character range
//Then using map, we map the int to and from a Char, just like Codec mapping.
//This provides a ValidatedField<Char>, so calling get() will provide a character!
ValidatedField<Character> validatedCharacter = new ValidatedInt(0, Character.MAX_VALUE, Character.MIN_VALUE).map(
    i -> (char)i,
    c -> Character.getNumericValue(c)
);

	// conditions should supply live values. Validated fields are a convenient mechanism to do that. A plain boolean won't update in-GUI until changes are applied.
	ValidatedBoolean validatedBooleanGate = new ValidatedBoolean();

	//create a conditional validation with toCondition. Note that the type is no longer ValidatedInt directly.
	ValidatedCondition<Int> validatedConditionInt = (new ValidatedInt(5, 100, 0)).toCondition(validatedBooleanGate, Text.literal("Gate must be true"), () -> 0);

	//We can add more conditions and set up a "fail title" once we have the initial condition
	ValidatedCondition<Int> validatedConditionInt = (new ValidatedInt(5, 100, 0))
            .toCondition(validatedBooleanGate, Text.literal("Gate must be true"), () -> 0)
            .withCondition(Text.literal("This also must be true"), () -> mySecondCheck())
            .withFailTitle(Text.literal("Condition not met"), Text.literal("Conditions not net")); //you can add both a singular and plural of your fail message, useful if you have more than one condition

	//boolean with an attached listener that setups some system when the setting is flipped to true.
    ValidatedBoolean listenerBoolean = (new ValidatedBoolean(false)).withListener(lb -> {
      if (lb.get()) 
		  setupSomething
    });

    //the below example has two booleans that toggle each other on/off, providing a sort of "cross-linked" setting where only one can be active at a time.
    //it's important to note the usage of validateAndSetFlagged here, which lets the partner setting be updated "quietly", otherwise you will deadlock and stack overflow
    //QUIET = no listeners applied
    //UPDATE = applies updates to the config manager system, syncing/saving/etc any changes made by the listeners
    ValidatedBoolean aBool = (new ValidatedBoolean(false)).withListener(a -> {
      if (a.get())
        bBool.validateAndSetFlagged(false, EntryFlag.Flag.QUIET, EntryFlag.Flag.UPDATE);
    });
    ValidatedBoolean bBool = (new ValidatedBoolean(false)).withListener(b -> {
      if (b.get())
        aBool.validateAndSetFlagged(false, EntryFlag.Flag.QUIET, EntryFlag.Flag.UPDATE);
    });

	//this codec will parse integers, clamping the allowed value to 0 to 100.
    Codec<Int> intCodec = (new ValidatedInt(5, 100, 0)).codec();

ValidatedBoolean myField1 = ValidatedField
        //attach a custom translation provider to the setting. 
        //this example just echoes out the current value of the setting without any decoration
        .translationProvider(new ValidatedBoolean(), (value, translationKey) -> Text.literal(value.toString()));

ValidatedBoolean myField2 = ValidatedField
        //attach a custom description (tooltip) provider to the setting. 
        //this example attaches a simple literal string. Probably don't do this in practice (just use the lang file for this)
        .descriptionProvider(new ValidatedBoolean(), (value, translationKey) -> Text.literal("This setting controls the blahblah blah."));

ValidatedBoolean myField3 = ValidatedField
        //attach a widget title to the setting. This will appear as the label on the setting button in the GUI
        //this example replaces "True" and "False", the boolean setting widget labels, with "Enabled" and "Disabled"
        .attachProvider(new ValidatedBoolean(), Provider.getWIDGET_TITLE(), (bl, defaultText) -> {
            return bl ? Text.translatable("my.key.enabled") : Text.translatable("my.key.disabled"); //translate to "Enabled" and "Disabled"
        });