1.21.5 - Some functionallity

[litetex]

This is a PoC showcasing some work that I did to get some basic functionality (connected textures) working with 1.21.5.
It might help with updating the complete mod to 1.21.5.

Please note that I'm not committed to implement the still missing functionality, so don't wait for this PR to be finished.

What is NOT working / still needs to be done

• Emissive textures (1.21.5 changed a lot of the corresponding code)
• Some optimizations can likely be done. For example there are no longer any block-states used. The code for this can be removed and caching may be applied.
• FallingBlockEntityRendererMixin is incompatible with Fabric-API's version of it. Currently the relevant code was copied over.

Already done

• Updated various (dependency) versions
• Connected textures
  Screenshot

  
  

Download

Pre-built JARs are available from: https://github.com/litetex/Continuity/actions/workflows/build.yml?query=branch%3A1.21.5%2Fdev

Direct download link

Use at your own risk.

[PepperCode1]

Thanks for your efforts, but most relevant changes in this pull request I have already made locally since I made a test build for the Discord a few days ago.

However, I am interested by what you mean by

Some optimizations can likely be done. For example there are no longer any block-states used. The code for this can be removed and caching may be applied.

[litetex]

@PepperCode1
Thank you for the quick response.

Thanks for your efforts, but most relevant changes in this pull request I have already made locally since I made a test build for the Discord a few days ago.

Okay, I was not aware of this.

How about using the Git repo instead?

• That way also your PC can exploded and your work is still saved (one of the main points why Git is used in the first place)
• GitHub Actions can build the code automatically and so it's not a "trust me" JAR from Discord

However, I am interested by what you mean by

Some optimizations can likely be done...

So for example:

• https://github.com/PepperCode1/Continuity/pull/645/files#diff-413e203ad3519ef987a373121f566e2882f64e4b63deaf769dcfef04679f9569R80-R90
  Called the cache directly when it was not the default blockstate - this might need some additional attention.
• Dead/Unused code can likely be cleaned up once the overall functionality has been implemented

[PepperCode1]

I agree using Git even for WIP code would be better. I'll try to do that more going forward.

The default state and default slice func system exist to make that path run faster than accessing the global cache every time, since the default state is used almost all the time. However, edge cases are possible when the model is invoked by another model with a different state or the block has a custom appearance. The state will not match the default state in these cases, so the slice func for the current state should be retrieved from the global cache. I don't see how 1.21.5 changes the need for this system.