Devlog 2024-05-1w
[h2]Hut[/h2]
The first version of the hut is finished
[hr][/hr]
[h2]UI[/h2]
A window for settings for sound, video, and input was created.
I don’t like assemble UI :)
[hr][/hr]
[h2]Crossplay[/h2]
This weekend there was just a hot in the 'Helldivers 2' community (this story is related to the mandatory linking to the PSN account). It's very good that Sony rolled back their demand.
I don't like it when a game requires an account from another ecosystem. You buy a game on Steam, which means that the game should only require a Steam account. I understand that there are rare cases when you will need an additional registration in the developer ecosystem, but I really don't like it.
Now, regarding crossplay in Medieval Towns and future plans.
Using the EOS (Epic Online Services) for crossplay involves link an existing EGS account or creating a proxy-account in the EGS, which the player can, if desired, convert into a full-fledged one. Now, after conducting crossplay tests, the Steam player connects to the EOS session completely transparently: no questions or requests for creating a proxy-account occur, and no requests to link an account are issued. Apparently, the proxy-account is never created, and the Epic documentation is outdated (this is not uncommon for them). Or maybe it is created, but it is completely transparent to the player.
In general, if some service will require the player to create/link an account outside the native ecosystem, then I will not use such a service. And I can create my own crossplay, without creating my own accounts at all. Or abandon crossplay altogether.
The first version of the hut is finished
[hr][/hr]
[h2]UI[/h2]
A window for settings for sound, video, and input was created.
I don’t like assemble UI :)
[hr][/hr]
[h2]Crossplay[/h2]
This weekend there was just a hot in the 'Helldivers 2' community (this story is related to the mandatory linking to the PSN account). It's very good that Sony rolled back their demand.
I don't like it when a game requires an account from another ecosystem. You buy a game on Steam, which means that the game should only require a Steam account. I understand that there are rare cases when you will need an additional registration in the developer ecosystem, but I really don't like it.
Now, regarding crossplay in Medieval Towns and future plans.
Using the EOS (Epic Online Services) for crossplay involves link an existing EGS account or creating a proxy-account in the EGS, which the player can, if desired, convert into a full-fledged one. Now, after conducting crossplay tests, the Steam player connects to the EOS session completely transparently: no questions or requests for creating a proxy-account occur, and no requests to link an account are issued. Apparently, the proxy-account is never created, and the Epic documentation is outdated (this is not uncommon for them). Or maybe it is created, but it is completely transparent to the player.
In general, if some service will require the player to create/link an account outside the native ecosystem, then I will not use such a service. And I can create my own crossplay, without creating my own accounts at all. Or abandon crossplay altogether.