Is this project still alive? #196
Comments
Friendly0Fire
added
help wanted
|
I hope it is still alive! |
|
Doesn't seem like it. The 403 error issue has gone from an issue that you can get around by running as admin, to an issue that happens every time regardless. The mod manager is now 100% unusable for me. Hope its resolved at some point. Going to have to rely on manually installing addons for the foreseeable future. |
|
A 403 error means you need to stop and wait, it has absolutely nothing to do with running as admin. |
I read in passed posts that it happens when you try to open the manager too many times. However, it occured the first time I opened the manager in 2 months. Before you could get passed this issue by running the manager in admin mode. Now it happens regardless of running in admit, first time every time, and no matter how long you wait. I posted a bug report highlighting that it was not a waiting issue, but it was deleted because it was too close to another generic 403 post. |
|
You can think or claim whatever you want, we don't make up the error code, we pass it along from Github. Github doesn't care about you running as admin, it can't even know that, and if it says you've hit the Github API too many times, it'll block you. Nothing we can do about it other than to tell people to wait, since the primary reason for a 403 is that the manager was opened too often/recently. |
I'm not posting to argue with you, and I am not implying you made anything up. I am simply informing you that the error is being given despite opening the program for the first time. And maybe it was good timing, but running in admit was seemingly bypassing this issue. The last two patches of the game gave me Error 403 on the very first opening. The first occurrence, after not being able to figure it out, I was told to try running in admin mode. I did, and it either worked or was very well timed. The next patch, I opened the AOM for the first time since, and again, Error 403. Admin mode (seemingly) immediately bypassed it. Now 403 error occurs first time upon opening as usual, only admin mode no (seemingly) longer fixes it. Whether or not the admin mode bypass is a placebo fix or not, the 403 error occurring on the first start up is very real. Whether its an issue with the AOM or with github itself, I am sure you know better then me. Just stating that it is happening, and its currently rendered the AOM unusable. Its the first time I have experienced any problems like this since I started using it 2 years ago, but if nothing can be done about it, than it is what it is. Just going to have to manually install for now and try back again later. I don't know enough to understand whats causing it. Github, or an issue on my computer. All I know is that it IS happening on the first start up for some reason. |
|
Arguments aside, is the project still being maintained? |
|
bump I'm having problems with using arcdps using GW2UAOM, I don't know whether GW2UAOM is to blame but idk whether to continue use of this tool if it's not maintained anymore. |
|
Clearly 403 can happen on actual first open. What the user should do when they encounter this is wait and try again. Personally I've had it work ~10 or so minutes later but YMMV and longer is better I'm sure. To cut down on these complaints this should probably be on the main page. |
|
Ok so assuming the answer to the question in the title of this issue is "no", possibly a safe assumption given that the issue was posted just under 4 months ago with no response from any of the developers, does anyone know of any alternatives to GW2UAOM? |
Ok tried once, ran it normal, failed. Waited 10 minutes. Tried running as Admin, failed again, here is the error: [Log Entry] |
This appears to be a limitation of github that is then (possibly) combined with how the application is trying to reach github. The only way I've found to fix this is to use a vpn when I get this error. |
|
@Friendly0Fire I see you added the |
|
Someone is needed to carry the redesign to the finish line, essentially. It's already in large parts complete, but the transition to a stateless system was never finished. I would not recommend forking due to the interconnected nature of the app and its various projects. PRs are welcome. |
|
I've been getting this issue every single launch when trying to launch from the start menu. But if I try to launch the exe directly from the directory I extracted it from, it works fine. What would cause launching from the start menu to break it like this? |
If someone is willing to take the time to show me how to update just which mod files it's calling to (as a PR), I would be happy to update it at least this time, and I'll try to write up the notes I take for others to do the same, so it could be updated more often. I'm pretty sure the crash issue I'm having right now is due to it calling for an older arcdps version (or an older version of arcdps-related addons). I've not really done PRs before, but I think I could handle this. |
|
@Friendly0Fire I did some work on the redesign on my fork. Some minor things are to be done, yet. But it seems to work so far. Are there any open points I should have a look on? Maybe you can have a look? |
|
2000 lines of formatting are hard to read. Next time please split out formatting and actual changes into separate commits. |
and others
There's a lot of issues and PR still opened for this project, the latest build released like 10 months ago, is there anyone working on fork to solve these issues?
The text was updated successfully, but these errors were encountered: