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

Time and weather implementation #96

Closed
wants to merge 1 commit into from
Closed

Time and weather implementation #96

wants to merge 1 commit into from

Conversation

AsgardXIV
Copy link
Contributor

@AsgardXIV AsgardXIV commented Jan 8, 2023

Implements time and weather changing.

WorldHooks in this case is actually doing a bit more than hooking and the general vars it exposes might be better suited to some other more generic 'Service' but there doesn't seem to be a model for that in Ktisis currently, unless I missed it.

Also not crazy about how it's grabbing the territory/weather info from Lumina (The animation stuff has a similar issue), so that's another area where an official way to do that kind of work might be nice in future.

Copy link
Member

@Fayti1703 Fayti1703 left a comment

Choose a reason for hiding this comment

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

Looks good overall; there's just two things I'd like to see changed here, see below.

It might also be worth contributing the fields in ExtendedFramework upstream to FFXIVClientStructs (though this isn't a requirement for merging).

Ktisis/Interface/Components/WeatherControls.cs Outdated Show resolved Hide resolved
Ktisis/Interop/Hooks/WorldHooks.cs Outdated Show resolved Hide resolved
@Fayti1703
Copy link
Member

Relations:

(This is for internal tracking. Conflicts need not be resolved prior to merging.)

@AsgardXIV
Copy link
Contributor Author

Fixes are up, and I do intend to push the changes back to ClientStructs so we can drop ExtendedFramework once that makes it back upstream.

@AsgardXIV AsgardXIV changed the base branch from main to feature/extend-i18n January 11, 2023 21:47
@AsgardXIV AsgardXIV changed the base branch from feature/extend-i18n to main January 11, 2023 21:47
@AsgardXIV
Copy link
Contributor Author

Update for 6.3

@Fayti1703
Copy link
Member

It looks like you merged your old and new histories rather than force-pushing, which is making the commit history look a bit wierd.
I could fix that if you want, but I'd rather not force-push someone else's branch without their permission.

@AsgardXIV
Copy link
Contributor Author

Should be resolved

@AsgardXIV AsgardXIV closed this Feb 2, 2023
@chirpxiv
Copy link
Member

chirpxiv commented Feb 2, 2023

Confused why these (#96, #97, #98) got closed, is something wrong?

@AsgardXIV
Copy link
Contributor Author

Yes, as per my twitter and posts on discord, I am taking a break from the FFXIV dev community and won't be actively contributing to any projects at present. The code is still there in the PR if you want to use it, I just won't be shepherding it through the process.

I'm happy to discuss it privately if you have any questions, a GitHub issue is not the right forum.

@chirpxiv
Copy link
Member

chirpxiv commented Feb 2, 2023

Okay. These can stay open though, we'll make any adjustments as needed.

@chirpxiv chirpxiv reopened this Feb 2, 2023
@chirpxiv
Copy link
Member

chirpxiv commented Feb 2, 2023

I'm happy to discuss it privately if you have any questions, a GitHub issue is not the right forum.

Side note regarding this - I'd prefer that any communication regarding Ktisis stays public for the sake of transparency, for users, contributors, and the rest of the team. If you don't want to discuss it in a GitHub issue, then the Discord has the #ktisis-dev channel for that.

@AsgardXIV
Copy link
Contributor Author

Side note regarding this - I'd prefer that any communication regarding Ktisis stays public for the sake of transparency, for users, contributors, and the rest of the team. If you don't want to discuss it in a GitHub issue, then the Discord has the #ktisis-dev channel for that.

In the interests of transparency then.

The very serious accusations of copying and theft, as well as the vile abuse I've received in DMs on both Discord and Twitter have been from people claiming or implying they are acting on behalf of the Ktisis dev team, without being willing to use anything more than a socketpuppet account and immediately lock down the account or delete the tweets/account in question.
I certainly hope that isn't actually the case and that these are trolls or people white knighting for you without your knowledge.

Regardless, it's clear that this has turned into some perverse, childish, toxic competition between Ktisis/Brio/Anamnesis and if that's going to be the case, I don't want to be involved in posing development for the foreseeable future. I did this for the fun of it and in pursuit of knowledge that would benefit all 3 projects, and to be attacked, called homophobic names and abused is not my idea of fun.

@Fayti1703
Copy link
Member

I'm really sorry to hear that. I completely understand you wanting to take a break if that's what you've had to deal with.

We were genuinely unaware of any harassment. We did not and do not direct others to abuse you or other developers; nor did or will we use alt accounts to hurt other people.
Whoever sent you those messages is not affiliated with us and acted without our consent or knowledge.

Speaking for myself, I realize I may come off as harsh or abrasive while critiquing something on a technical level, but that is not meant as a personal attack in any way.

Regardless, we respect your decision and wish you the best.

@AsgardXIV
Copy link
Contributor Author

We were genuinely unaware of any harassment. We did not and do not direct others to abuse you or other developers; nor did or will we use alt accounts to hurt other people. Whoever sent you those messages is not affiliated with us and acted without our consent or knowledge.

I'm glad to hear that, and I believed it to be the case, but the confirmation is a comfort.

Speaking for myself, I realize I may come off as harsh or abrasive while critiquing something on a technical level, but that is not meant as a personal attack in any way.

I have no problems with anything you've said to me personally or our interactions, discussion of code quality is healthy and normal.

Regardless, we respect your decision and wish you the best.

I wish you the best as well, perhaps in the future when things have calmed down, we'll be able to collab again.

@chirpxiv chirpxiv closed this Feb 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants