ExileAPI Fork 3.11 Release

[Sychotix]

As mentioned earlier I am not supporting bot developement (or other private projects). The differences between the forks in the current state especially regardings the "API" are minimal .(read "API" as "the public method this project provides to the plugins", depending by which definition you go that is an API and I guess thats were the name is coming from).

Nevertheless this fork is staying public. How useful it will be in the future depends on the contribution of the community and most likely the way forward in TehCheats fork. As mentioned earlier the differences are quite small so it adds only a slight technical advantage to keep this fork (read my long post about the reasons why I want to keep this fork). Most plugins work in both forks, I have not seen any public plugin yet which is not working in my fork but in TehCheats. (I asked for them earlier, feel free to provide me a link, I am always interested in those).

The time this fork shines is when the other repository is going private again. Due to the answers in here I still think my previous though about this is valid: TehCheat repository may goes private at any time.
When this happens and the community is contributing as much as the last time, it will most likely only take a few days (if at all) to get this fork up and running again.

I believe that for any repo, if it goes private... forks do not disappear/go private themselves.

If TC's repo ever goes private, your last update from master will be preserved. From that point, you can make any updates wanted/needed (such as updating offsets/fixing patterns). If TC's repo ever goes public again, changes can be merged, or your fork can be rebased.

Up to you however you want to handle it, just a possibly less clunky suggestion. This way the forks stay as close as possible to make merging/pull request easier. That said, if TC ever decides to make his fork permanently private, it doesn't matter either way.

[stfufag]

that's not good

you guys should work together for the greater picture around the community of the PoEhud,

having two forks now creates problems for everyone, one might not be there, people might rely on one or another, one might just go private, then the other one might be on holidays not doing anything on league release etc.

bad and dividing

[TehCheat]

that's not good

you guys should work together for the greater picture around the community of the PoEhud,

having two forks now creates problems for everyone, one might not be there, people might rely on one or another, one might just go private, then the other one might be on holidays not doing anything on league release etc.

bad and dividing

I agree.

At this point I'm far more likely to shut my fork down and contribute (sparingly) to this fork (via pull requests), than I am to maintain a separate fork (which is what I was alluding to with the "one way or the other" statement in my previous post). That's essentially the position that I wanted to be in when I handed the project off to qvin in the first place (just before Blight league). I didn't intend to come back, but I did so out of necessity. 2 weeks into Metamorph (the 2nd league after the qvin hud switch) the offsets were still quite broken. I assumed the same would happen with Delirium and offered the community an alternative. And now we're here.

So I guess this settles it, plan on this being the main poehud fork next league. I'll archive mine at some point before the start of next league (and fork this one). We'll see if he's up to the task or not. I have my doubts, but I'll give him a chance to prove he can handle it.

[Queuete]

I believe that for any repo, if it goes private... forks do not disappear/go private themselves.

If TC's repo ever goes private, your last update from master will be preserved. From that point, you can make any updates wanted/needed (such as updating offsets/fixing patterns). If TC's repo ever goes public again, changes can be merged, or your fork can be rebased.

Up to you however you want to handle it, just a possibly less clunky suggestion. This way the forks stay as close as possible to make merging/pull request easier. That said, if TC ever decides to make his fork permanently private, it doesn't matter either way.

Thats exactly the current state, isnt it?
My fork wont be influenced by TC going private. Pull Requests/ Merges are possible, even through the Github UI.

having two forks now creates problems for everyone, one might not be there, people might rely on one or another, one might just go private, then the other one might be on holidays not doing anything on league release etc.

How is that problem solved by having one repository instead of two? If I close my fork and TehCheat is on Holdiay on league release there wont be any updates at all.

I agree.

At this point I'm far more likely to shut my fork down and contribute (sparingly) to this fork (via pull requests), than I am to maintain a separate fork (which is what I was alluding to with the "one way or the other" statement in my previous post). That's essentially the position that I wanted to be in when I handed the project off to qvin in the first place (just before Blight league). I didn't intend to come back, but I did so out of necessity. 2 weeks into Metamorph (the 2nd league after the qvin hud switch) the offsets were still quite broken. I assumed the same would happen with Delirium and offered the community an alternative. And now we're here.

So I guess this settles it, plan on this being the main poehud fork next league. I'll archive mine at some point before the start of next league (and fork this one). We'll see if he's up to the task or not. I have my doubts, but I'll give him a chance to prove he can handle it.

As mentioned earlier that decision is totally up to you. If you want to close your repository go ahead. I will still have this repository as a (fun) spare time project and go as fast as I want with it. Community contribution obviously increases this speed. If thats to slow for you or you dont like the direction this is heading, feel free to keep/get your own fork.

[TehCheat]

How is that problem solved by having one repository instead of two? If I close my fork and TehCheat is on Holdiay on league release there wont be any updates at all.

I'm not the only one that has direct access to my repo, so this doesn't really apply.

As mentioned earlier that decision is totally up to you.

As mentioned earlier, that decision is directly influenced by your decision to keep this fork.

[Queuete]

I'm not the only one that has direct access to my repo, so this doesn't really apply.

Thats quite out of context. I was answering someone arguing that 2 forks are bad in case someone is on holiday when a league starts. Which makes no sense at all, regardless of how many people have access to your repository.

As mentioned earlier, that decision is directly influenced by your decision to keep this fork.

Thats fine by me. I am currently getting quite confused by the other 92 public forks of Qvins ExileAPI or descendants. Even Sychotix has one. Luckily thats not pushing me to go private.

[stfufag]

well, get on discord so we can annoy you with requests then

i don't like this, have a bad feeling about the situation, next league will show

[TehCheat]

Thats quite out of context. I was answering someone arguing that 2 forks are bad in case someone is on holiday when a league starts. Which makes no sense at all, regardless of how many people have access to your repository.

I think his point was that if someone is on vacation, one fork won't work, and the other might. And the next league the opposite person may be on vacation and the other fork might be the one that works. This could potentially lead to confusion. I agree that having two forks doesn't really prevent things from getting updated, but I think his point was that it can lead to confusion. And that is certainly a valid point. We'd just be better off as a community with a single fork with multiple people having access to it. Which plays into my point, that my fork is far more likely to be stable as it has multiple people that can update it, and it's more resilient in the case that I'm on vacation.

Thats fine by me. I am currently getting quite confused by the other 92 public forks of Qvins ExileAPI or descendants. Even Sychotix has one. Luckily thats not pushing me to go private.

Multiple forks aren't pushing me to go private. Multiple forks being updated in different directions and being pushed to the forum here is what's pushing me to go private.

No one cares if you have a public/private repo that you do your own things to, which is what all of those other 92 forks are (or in a dormant, unmaintained state). But if you're going to push it on the community here and cause confusion, that's when people start caring.

[stfufag]

100% agree @TehCheat,

the vacation thing is just one example @Queuete, you can replace this with any other possibly scenario how this could go sideways.

Please start shaking hands and work together in one single repo with multiple people working together. That's he best for this community.

[Queuete]

well, get on discord so we can annoy you with requests then

i don't like this, have a bad feeling about the situation, next league will show

No thanks, feel free to start your own fork and get us a better situation for next league.

I think his point was that if someone is on vacation, one fork won't work, and the other might. And the next league the opposite person may be on vacation and the other fork might be the one that works. This could potentially lead to confusion. I agree that having two forks doesn't really prevent things from getting updated, but I think his point was that it can lead to confusion. And that is certainly a valid point. We'd just be better off as a community with a single fork with multiple people having access to it. Which plays into my point, that my fork is far more likely to be stable as it has multiple people that can update it, and it's more resilient in the case that I'm on vacation.


Multiple forks aren't pushing me to go private. Multiple forks being updated in different directions and being pushed to the forum here is what's pushing me to go private.

No one cares if you have a public/private repo that you do your own things to, which is what all of those other 92 forks are (or in a dormant, unmaintained state). But if you're going to push it on the community here and cause confusion, that's when people start caring.

Lets talk about confusion.
- you serve compiled code in a github repository
- there is another repository with the source. When downloaded this does not include the static files. For those you need to get the compiled version at least once.
- your thread title is "... 3.10 ..."

Thats fine? But a different thread, with a another working version is confusing?

100% agree @TehCheat,

the vacation thing is just one example @Queuete, you can replace this with any other possibly scenario how this could go sideways.

Please start shaking hands and work together in one single repo with multiple people working together. That's he best for this community.

While I am not able to say with which intention TehCheat came into this thread to request it to get closed, but it was definitily not to get me to work with him. Or if it was he is extremly bad at it. (Hint: personal attacks are not very effective when you try to convince someone).
The whole "decision" to make is not wether I will work on TehCheats fork, it is wether I will work on ExileApi at all. And I will take the so called confusion as a negative compared to having only a single choice which may goes private at any time.
In terms of having a functional state of the project there is no scenario in which having those 2 forks is inferior to only TehCheats repository.

[TehCheat]

- you serve compiled code in a github repository

And? The whole reason I did that was because noobs didn't know how to compile qvin's source code. I gave the community an easy way to get compiled code. If you think this is some kind of bad thing, you're not paying much attention.

Also, I looked at your repo, you serve compiled code in a github repository. So congrats, whatever attack you were trying to make here applies equally to you.

- there is another repository with the source. When downloaded this does not include the static files. For those you need to get the compiled version at least once.

Yes, because qvin's didn't include this when I forked it. I haven't put in the time to fix it. I did just mention it on the discord that it's on my list of things to do.

- your thread title is "... 3.10 ..."

My thread didn't have a comment in it since 3.10... Try harder.

EDIT: I guess my poehelper thread says the same. You're probably too much of a noob (referring directly to your Dec 2019 join date) to realize it, but we had the same outdated poehud version in the thread title for like 5 years. It's not exactly common practice to replace the thread every 3 months, and I think the community has managed their way through it just fine. But I suppose you think it's confusing, so it's something to consider.

Thats fine? But a different thread, with a another working version is confusing?

Yes, another thread, with another repo, going in a different direction, that handles plugins differently is confusing. If you want to argue that it isn't confusing and the 3 bullet points above are confusing (one of which applies to your repo), then you're just going to look silly.

In terms of having a functional state of the project there is no scenario in which having those 2 forks is inferior to only TehCheats repository.

That is just laughably untrue. I'm not even sure how you could logically and reasonably argue otherwise. stridemann and I could both maintain forks separately, but we're (and the community as a whole is) certainly better off working together in virtually every imaginable scenario. VMV, zaafar, stridemann and myself all worked on hud at the same time back in the day, and evolved it into very much the project that it is today. If we all had separate branches, that wouldn't have happened. It would have been a mess and what rose from the ashes would have been a fraction of all the great features and UX/UI that it turned into.

[Illium]

TehCheat's suggestion is to merge the repos and access he's repository ... and be ready to make the repository payable for the community when the league starts.
Queuete considers it unacceptable to charge the repository. It's all.
I believe the dilemma is insoluble without concessions. In my opinion, paid access is not bad, but it is definitely annoying and reduces the motivation of the community to work on plugins.

[Queuete]

You seem to miss the point once again. The current state of your fork is a proof that "reduction of confusion" was none of you priorities in the recent past.

Yes I serve compiled shaders in separate "StaticResources" project, which is required to compile a full version from source without grabbing anything of an old build. To compare that with a repository which consists of the compiled version is a joke.

While I think no version number in the thread is not perfect its certainly better (less confusing) then having an outdated version number in there.

You should read my last passage again. I never said that teams are less productive then a single person (thats the whole point you are arguing). I talked directly about "those 2 forks" (yours and mine) vs only yours (without me working on it, because thats not an option for me anymore).

TehCheat's suggestion is to merge the repos and access he's repository ... and be ready to make the repository payable for the community when the league starts.
Queuete considers it unacceptable to charge the repository. It's all.
I believe the dilemma is insoluble without concessions. In my opinion, paid access is not bad, but it is definitely annoying and reduces the motivation of the community to work on plugins.

I have no clue what TehCheats intentions are. My code is open source he has access to it and can merge it at any given time. If he plans to go private and sell the version again (which I doubt) its obviously not so nice to have another public option.

Nevertheless this will be my last post on this matter I will ignore further posts about this topic in this thread.

My fork is going to stay online and public and worked on by me in my spare time as a fun project. That means the state and especially the speed of updates totally depends on my mood and the contributions of the community. This will not be influenced by TehCheat going private in either direction. Since his personal attacks in here I am not considering working more closely with TehCheat as an option.

This project is staying open source I encourage everyone to fork / merge my changes or to contribute to this fork.

[TehCheat]

You seem to miss the point once again.

I'm not missing the point, you're not making it. There's no point to miss.

The current state of your fork is a proof that "reduction of confusion" was none of you priorities in the recent past.

And yet you directly attacked one of the key points of my "reduction of confusion" as a confusing bullet point. Making a pre-compiled hud available was done directly to address a point of confusion in the community. And that's certainly not confusing for the vast majority of the community which uses it. And mind you THIS WAS THE FIRST QVIN HUD REPO I HAD. It existed solely to provide the community with a compiled version because qvin's version was difficult to compile out of the box and people couldn't use hud at all unless they were at least familiar with VS and managed to track down the instructions for compiling. And yet you somehow think that this repo that adds clarity to the community is a "confusing" repo. It's kind of hilarious from my vantage point.

Yes I serve compiled shaders in separate "StaticResources" project, which is required to compile a full version from source without grabbing anything of an old build. To compare that with a repository which consists of the compiled version is a joke.

That's not the only compiled code your repo is hosting. And again, there's nothing wrong with a github repo hosting compiled code. I'd wager that a majority do, whether it be in the releases or directly in the project (as yours has in multiple locations). I don't know why you think it's an insult, but it's hilarious that you're making excuses for your repo (and missing a large chunk of the compiled code that you're hosting in defense of your own "insult").

While I think no version number in the thread is not perfect its certainly better (less confusing) then having an outdated version number in there.

And like I said, that certainly can be improved, but it's not like the community is so stupid they can't figure it out.

You should read my last passage again. I never said that teams are less productive then a single person (thats the whole point you are arguing). I talked directly about "those 2 forks" (yours and mine) vs only yours (without me working on it, because thats not an option for me anymore).

I didn't misread it. I showed 2 examples of how multiple forks would have had a worse outcome than just 1. And you being you and refusing to work together doesn't change those scenarios.

But I'll go another step further, I'd argue that stridemann OR myself maintaining a single hud would be better for the community than both of us maintaining separate huds. For the exact reasons I don't think your fork should be pushed here alongside mine. It just makes a mess. It makes things confusing. Things work one way in one spot and another way in another spot. That's just awful.

Also, if you think I've made any personal attacks in any of these posts, I've gone out of my way to avoid them. Feel free to point any out.

[Sithylis]

well, get on discord so we can annoy you with requests then

i don't like this, have a bad feeling about the situation, next league will show

I agree, i can send an invite link to @Queuete if he wants to join.

Having 2x repos will be bad, it wont be much now but it will be chaos in a year or so with 2x repos going in 2x different directions.

@TehCheat doesnt care what happens, he just wants all people working on the same repo (and so do the devs in the discord...) whether that be one or the other is a non issue.