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

Move Viper and VTOL to collapsed section #81

Merged
merged 1 commit into from
Jul 29, 2024

Conversation

GeckoEidechse
Copy link
Member

@GeckoEidechse GeckoEidechse commented Jul 27, 2024

This IMO might be a controversial change given that I wrote FlightCore but there has a been a common sentiment over the last few months that out of FlightCore, VTOL, and Viper, FlightCore is the installer/mod-manager that causes the least issues with end-users.

It's not without reason that #48 exists. Further showing 4 different installation options confuses end-usersbased on feedback on Discord and it makes sense to highlight a mod-manager that is developed by someone closely associated with Northstar development.

At the same time I'm well aware of the improvements @0neGal made to Viper in the last few weeks and that VTOL also still sees development whenever @BigSpice is able to work on it.

So I struggle whether to merge this change or not and would highly appreciate any feedback on this <3

Rendered:

Screencast.from.2024-07-27.19-42-31.mp4

Supersedes #48
Sorta supersedes #64

@BigSpice
Copy link

Understood honestly.
I've been very mia , and can't excuse that.

Agree with the changes.

Im back starting in 2 weeks and will be sure to bring VTOL back to current release standard.

❤️🫡.

@0neGal
Copy link
Contributor

0neGal commented Jul 27, 2024

I honestly think any opinion I would give on a PR like this would be biased, so I would honestly just let it be up to you, even if it may also be biased for you. I do however think adding support links directly on the website alongside with possibly just redirecting users automatically in tickets may help a lot, or well, move the issues from the NS Helpers over to the actual mod manager developer(s), which I wouldn't particularly mind...

@EM4Volts
Copy link
Contributor

EM4Volts commented Jul 28, 2024

honestly think any opinion I would give on a PR like this would be biased, so I would honestly just let it be up to you, even if it may also be biased for you. I do however think adding support links directly on the website alongside with possibly just redirecting users automatically in tickets may help a lot, or well, move the issues from the NS Helpers over to the actual mod manager developer(s), which I wouldn't particularly mind...

no regular user wants to make a github issue, even if u give them a link, tickets are already done by mods/helpers/contributors/modders alike. there is nothing to "move"

@GeckoEidechse
Copy link
Member Author

I do however think adding support links directly on the website [...]

I like that idea. Feel free to make a PR to this repo to add ^^

[...] alongside with possibly just redirecting users automatically in tickets may help a lot, or well, move the issues from the NS Helpers over to the actual mod manager developer(s), which I wouldn't particularly mind...

We could maybe have Spectre (the Discord bot @itscynxx wrote) check for keywords like "Viper" in tickets and post a message with a link to the Viper GitHub repo. Just keep in mind that the majority of players have no clue how GitHub works or have an account, hence me making majority of recent Viper GitHub issues in their place.

@GeckoEidechse
Copy link
Member Author

Aight, Imma just say we give this a shot, see if it has a positive impact in terms of tickets and reducing player confusion and if it doesn't we can always revert.

Also like, feel free to PR any changes if dislike this decision or want to adjust the description or want to add your own mod-manager etc ^^

I cannot stress enough how important open communication and discussion is and want to encourage everyone to reach out ASAP if anything is unclear or feels unfair. We always want to find the solution that fits everyone and that only works if everyone participates in the discussion and reaches out <3

@GeckoEidechse GeckoEidechse merged commit b5ae577 into main Jul 29, 2024
@GeckoEidechse GeckoEidechse deleted the feat/move-installers-submenu branch July 29, 2024 16:10
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.

4 participants