Add NetworkArea nodes as physics extras

[kumpmati]

Related to #437

Physics rollback messes with Area2/3D entered and exited signals, making them fire multiple times, especially with ping + CharacterBodies.

The NetworkArea2/3D helper nodes introduce rollback-aware versions of Area2/3D signals and methods with a rollback_ prefix.

TODO:

• Documentation
• Test with Jolt
• Test with Rapier (has issues)
• Test with Godot Physics
• Implement Area2/3D methods with rollback support

[Lonkman0403]

o

I will test this right now with godot physics stepping

[CardboardCarl]

I'll test this out with rapier when I get a second

[kumpmati]

I will test this right now with godot physics stepping

I'll test this out with rapier when I get a second

Thank you both! 🚀
If you haven't tested the code yet, here's an example repo I made to help test out issues with the different engines.

https://github.com/kumpmati/netfox-physics-rollback-test

[elementbound]

This runs in the tick loop, yet the signals emitted are labeled as rollback. Could you please clarify?

[elementbound]

@kumpmati is the example repo still up? I can't open it.

[kumpmati]

@kumpmati is the example repo still up? I can't open it.

Sorry I had made it private, it's now public again

[kumpmati]

Some things I should do still

[elementbound]

Some things I should do still

No worries @kumpmati, take your time! I think this will be another great addition to netfox's featureset, so I don't mind waiting a bit 😄 Let me know if there's anything I can help with, I'm happy to write the docs!

[kumpmati]

@elementbound Finally got around to updating this 🙂 From my understanding I should check for overlapping bodies/areas during _after_prepare_tick, since by then rollbacked nodes have their states set correctly?

[elementbound]

@kumpmati whoops, got distracted for a bit 😬 I think you are correct, you can also use the NetworkRollback.after_prepare_tick signal