Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 1.5 #28

Merged
merged 69 commits into from
Mar 23, 2023
Merged

Version 1.5 #28

merged 69 commits into from
Mar 23, 2023

Conversation

TureBentzin
Copy link
Member

  • bugfixes
  • setIfAbsent for Configurations
  • Create ObjectHashtableToStringHashtableMapper.java
  • further steps for the CoreCacheAPI
  • Breaking: Minigames now autostart!! (Experimental)
  • fixed Stackwalker for MiniGame error logging
  • some experiments with error-prone

@TureBentzin
Copy link
Member Author

I'm currently thinking about giving the MiniGame the ability to set a "startType" of some sort to make it easier to build MiniGames that are powered by a "LobbyPhase" and such ones that are running all the time and need to be started directly after the MiniGame was successfully loaded.

Currently the MiniGameAPI is not used over a wide range of projects, so it would be possible to make a breaking change.

Also i need to rethink the direct native integration of TimoCloud into the MiniGameAPI, maybe there should be a better way to integrate own and custom cloud systems into the communication and state providing service that is handled and managed by the MiniGame API. The API has currently only limited information about the MiniGame (There should be improvements). It should be possible to access the MiniGame and control it, also if the controller does not implement or know the (or a) MiniGameAPI.

If further support for different CloudSystems is implemented native into the Core (what is unlikely) then CloudNet2 and CloudNet3 need a native implementation. Other CloudSystems would need more research on their users and their features to allow them to be implemented into the Communication and State Provider Technology that is used by the MiniGameAPI to inform other Servers, Services and the Players about the current "state" the MiniGame is in.

Copy link
Member Author

@TureBentzin TureBentzin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added some additional information for the review process

Copy link
Contributor

@Bommels05 Bommels05 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you by now know what I would write here... Good Work and a few things to fix

* @param section the section
* @return an OfflineConfiguration. Changes to this will not affect root
*/
@ApiStatus.AvailableSince("1.5")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is in testing I would add a @ Experimental Annotation

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not only for testing, but also for storing data temporarily or working with a local dataset. There are a lot of possibilities!

@TureBentzin TureBentzin requested a review from Bommels05 March 22, 2023 16:01
Copy link
Contributor

@Bommels05 Bommels05 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@TureBentzin TureBentzin merged commit 2873eea into main Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bStats This is related to the collection of data with bStats Configuration Feature Removed This PR will remove a feature MessageSystem New Feature New Version This PR will update a version Paper Priority: High Waiting for review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants