
Shaderboard
A Minecraft mod that exposes client-side scoreboard values to post-effect shaders via named bindings.
Список изменений
This update brings in even more bindings that give post-effect shaders more information about the game environment.
A proper documentation is planned once I implemnet and release all the features I have planned (which I have not yet done).
Configuration system
This mod now has a dedicated configuration file with currently only one configurable property. To configure it, create the following file: [profile_dir]/config/shaderboard.json, and inside, write the following baseline JSON:
{
"client-logLoadingWarnings": true
}
More info will be made available once I finally write a proper documentation.
shaderboard:local_player_attribute
Exposes the entity attribute system to post-effect shaders. Please note that some attributes are entirely server-sided and thus reading them from client-sided post-effect shaders may produce unreliable results.
Example JSON:
{
"uniform_name": "u_MyChonkiness",
"type": "shaderboard:local_player_attribute"
"attribute": "minecraft:scale"
}
Example GLSL:
layout(std140) uniform u_MyChonkiness {
float baseValue;
float value;
};
shaderboard:local_player_status_effect
Lets post-effect shaders know if the local player has a specific status effect alongside how long it lasts and of what amplifier.
When duration reads 0 then the status effect is not present. When duration reads -1, then the status effect's duration is infinite. When duration is greater than 0, then the effect is present and lasts for a given amount of time.
Example JSON:
{
"uniform_name": "u_MyNightVision",
"type": "shaderboard:local_player_status_effect"
"effect": "minecraft:night_vision"
}
Example GLSL:
layout(std140) uniform u_MyNightVision {
int duration; //can be -1, and -1 means "infinite duration"
int amplifier;
int isInfinite; //0 = finite, 1 = infinite duration.
};
shaderboard:local_player_motion_state
Gives post-effect shaders general information about what the local player's character is currently doing movement-wise.
Example JSON:
{
"uniform_name": "u_MyMoves",
"type": "shaderboard:local_player_motion_state"
}
Example GLSL:
layout(std140) uniform u_MyMoves {
//these are integers posing as booleans; 0 = no, 1 = yes.
int isOnGround;
int isCrouching;
int isSprinting;
int isSwimming;
int isUnderwater;
int isFlying;
int isGliding;
int isRiding;
};
