Skip to content

Celestial Events API - #115

Draft
Atilist wants to merge 9 commits into
ModificationStation:developfrom
Atilist:master
Draft

Celestial Events API#115
Atilist wants to merge 9 commits into
ModificationStation:developfrom
Atilist:master

Conversation

@Atilist

@Atilist Atilist commented May 24, 2024

Copy link
Copy Markdown

The Celestial Events API now has all the primary features needed to be considered functional. There is also a handful of different example usages in the test mod. This should be ready to be included into Station API

@calmilamsy calmilamsy left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can't comment on the actual logic, I only gave this a cursory look before heading off for the night.

Suggestion: A few javadoc comments on the API classes at least would help folk figure out what's going on with celestial events.

@Atilist

Atilist commented May 25, 2024

Copy link
Copy Markdown
Author

The recent commit should properly address the requested changes

@calmilamsy calmilamsy left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This looks fine aside from the fact it should be using a registry for tracking registered events. I'll help you with that when I get a moment.

Comment thread src/test/resources/assets/sltest/stationapi/lang/en_US.lang Outdated
@Atilist

Atilist commented Jun 24, 2024

Copy link
Copy Markdown
Author

About the registry: I was actually considering to use it but was not sure if it makes sense. Is it about preventing events from having identical names or something else entirely?

@Atilist

Atilist commented Jun 24, 2024

Copy link
Copy Markdown
Author

A potentially more significant issue I just realized is that I am trying to merge into the master branch while I should be merging into a different branch due to this being a new feature. Should I change the target branch if this needs to be done on my end?

@Atilist

Atilist commented Jun 24, 2024

Copy link
Copy Markdown
Author

The newline should be taken care of now

@calmilamsy
calmilamsy changed the base branch from master to 2.0-alpha.3 June 25, 2024 13:09
@calmilamsy
calmilamsy changed the base branch from 2.0-alpha.3 to master June 25, 2024 13:22
@calmilamsy
calmilamsy changed the base branch from master to 2.0-alpha.3 June 25, 2024 14:01
@calmilamsy
calmilamsy force-pushed the master branch 2 times, most recently from 3bfe7b5 to 560bb9c Compare July 16, 2024 18:13
@mineLdiver mineLdiver added the enhancement New feature or request label Jul 16, 2024
@mineLdiver mineLdiver added this to the 2.0-alpha.3 milestone Jul 16, 2024

@mineLdiver mineLdiver left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

First review. Got some thoughts on the overall design of the API.

* It is recommended to add the event to CelestialTimeManger for automatic management.
* Inheritance is possible to add custom logic.
*/
public class CelestialEvent {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Not the best name, considering Event suffix most likely indicates an UnsafeEvents event. Not sure what would be a good alternative though.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

I could replace the suffix with Interval which might actually be a better hint for what it is

@Atilist

Atilist commented Jul 17, 2024

Copy link
Copy Markdown
Author

Got my workspace fixed up, now I can continue work on the API

@calmilamsy

Copy link
Copy Markdown
Member

Only thing left as far as I'm concerned is to detach event registering from world load and instead moving it to game init.

@Atilist

Atilist commented Oct 11, 2024

Copy link
Copy Markdown
Author

I am glad this PR is being picked up again. Thank you for putting in the time and effort to get the biggest flaws sorted out

@calmilamsy
calmilamsy marked this pull request as draft November 29, 2024 16:05
@mineLdiver
mineLdiver deleted the branch ModificationStation:develop November 30, 2024 16:31
@mineLdiver mineLdiver closed this Nov 30, 2024
@mineLdiver mineLdiver reopened this Nov 30, 2024
@mineLdiver
mineLdiver changed the base branch from 2.0-alpha.3 to master November 30, 2024 16:42
@mineLdiver mineLdiver removed this from the 2.0-alpha.3 milestone Nov 30, 2024
@mineLdiver
mineLdiver changed the base branch from master to develop December 1, 2024 08:57
mineLdiver and others added 4 commits July 27, 2025 22:38
imagine not having proper handling for build metadata in maven and no proper handling of multiple identifiers in fabric loader, thus having no way of having different releases which are only different in the way they're built? crazy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants