Repository navigation
2.1 Announcement #1369
maji-git
announced in
Announcements
Replies: 5 comments 4 replies
|
polytoria fell off… 😔 |
0 replies
|
again bro :O |
0 replies
|
Is 2.1 going to be backwards compatible with 2.0? |
2 replies
|
MAWJI YOU ARE BACK |
1 reply
|
yo |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
2.1 Announcement 📣
Hello everyone! mawji here (i'm back hooray). Me and the team is here to make an announcement of what's next for Polytoria 2.0. It's currently codenamed "Polytoria 2.1". Which is a major refactor of the 2.0 client, aimed at decoupling the datamodel (and related) from Godot.
What's the issue right now?
Due to the current architecture of the 2.0 source being tightly coupled to Godot. Lot of things are difficult to work with. For example: Optimizations with nodes, as every instances are required to have node attached, even if it weren't used. Having to fight with Godot for Dynamic transform calculations, having to workaround physics, impossible to test without Godot, etc. If you're already a contributor, you might know what's up with it... it's almost impossible to continue on this foundation.
What are we doing to fix that?
That's where 2.1 will come into play. It's a major refactor where a lot of the datamodel and related things (networking, Luau) will be rewritten. The main focus is:
We're also going to redo lot of axis mistakes and inconsistencies we had before, so this'll definitely be a breaking change.
What have been done so far?
Right now the member in the Polytoria Team & Internal beta team are discussing about how the new architecture should be planned. And the code itself is actively being worked on. We're looking to replicate the Datamodel from 2.0, then reuse the existing frontend code from 2.0.
Q&A Section
Q: When can I contribute?
A: We don't have a clear date set for 2.1 yet. However, it'll be open source before release to the official servers. We're currently carefully planning out the new architecture of the code overall. Once that has settled in, we'll open source it in the another branch for everyone.
Q: Why 2.1 and not 3.0?
A: We've considered internally about the naming of the versions. It's huge of a change and will definitely cause breaking changes. We decided to go with 2.1 mainly because it's still Godot for rendering and main application entry, and another reason: 2.1 to 3.0 would be too huge of a skip in a short time since 2.0 have only existed, not even a year yet, so. Alternatives we had in mind is the new version number scheme, like
generation.major.minor.patch. However this may change with more discussions going forward.Looking forward to hear from you all! 💖
All reactions