Faithfully Vanilla

This is a BETA RELEASE!!!! WHILE THIS WILL NOT CRASH WE ARE TESTING TO SEE IF THE TEXTURE UPDATE ADHERES TO OUR VANILLA ONLY TEXTURES POLICY. PLEASE LOOK BELOW FOR WHAT IS CONSIDERED A VIOLATION OF OUR VANILLA ONLY TEXTURES POLICY. THIS WILL HELP YOU SPOT ISSUES WITH THE CHANGES MADE...

OUR POLICY ON VANILLA TEXTURES:

PREAMBLE

This article is only added to texture updates that change vanilla textures and must be

"community" reviewed. Anything that changes vanilla textures must be community reviewed.

in accordance to policy on keeping things vanilla.

RULE 1:

Anything that changes trees in a way that edits the way trees spawn

is considered a violation of our Vanilla Texture Policy. Anything vanilla cannot

edit spawning of trees in a way that either edits the blocks tied to them. Examples of this

would be something like RL Craft Textures! Those are NOT allowed.

ENDING STATEMENT:

We are strict on stuff like these. But as long as we are not trying to make things look like

"Fully Modded" modpacks, then we are good to go. This mainly explains why textures that change

pregenerated items, blocks, or changes loot tables, adds custom blocks, are NOT ALLOWED!!!

THIS CONCLUDES OUR OFFICIAL POLICY ON HOW WE HANDLE TEXTURE UPDATES

STARTING ON MARCH 4 2022. THIS POLICY IS TO BE ADDED TO EVERY UPDATE INVOLVING

TEXTURES. ANYTHING WE ADD MUST BE REVIEWED BY THE COMMUNITY. COMMUNITY REVIEW

CAN BE CLOSED AT MINIMUM 2 WEEKS AFTER COMMUNITY REVIEW UNLESS DEEMED OKAY BY

THE COMMUNITY BECAUSE OF A "NO RESPONSE" CASE. A "NO RESPONSE" CASE HAPPENS WHEN

THERE IS NO ONE GETTING INVOLVED IN THE COMMUNITY. THIS CAN ALSO BE TAKEN DOWN BY US

IF THE COMMUNITY SAYS IT VIOLATES THE ABOVE CASE OR IF THEY PROPOSE AND EXPLAIN A NEW

INSTANCE OF "NON VANILLA VIOLATIONS" ALSO WE ARE REQUIRED BY CURSEFORGE TO ADHERE TO OUR

ROJECT TAGS AND CHANGE THEM IF NECESSARY WHICH WILL NOT HAPPEN BECAUSE OF OUR

"PROJECT LEGACY"