Jump to content
copygirl

Official issue tracker on GitHub

Recommended Posts

Hey everyone! I've suggested to @Tyron the possibility of using a public GitHub repository to track bugs and feature requests. He was so nice to give me the opportunity to create one and I already submitted a couple of issues myself. The upside over the forums is that it feels a little more leight-weight and focused, and some people, especially modders, might already have a GitHub account. Issues can be closed and re-opened, categorized, assigned to developers and milestones, even referenced to in other GitHub repositories.

[ GitHub: anegostudios / VintageStory-Issues ]

You're welcome to post pretty much anything:

  • Report bugs, glitches, crashes
  • Report performance issues
  • Suggest gameplay additions and changes
  • Suggest creative & server admin tools
  • Suggest modding API additions & improvements
  • Request documentation addition & clarification
  • Questions & discussions, preferably on the topic of modding

Feel free to open or move your issues there if you want, but you can also continue using the forums, Discord, or whichever way you preferred to so far. I might go as far as to mirror issues from the forums and Discord to the public issue tracker to have a single place for all our tracking needs, but - one thing after another.

If you have any questions, suggestions or concerns, please let me know and I'll try to get back to you, if someone else doesn't already in the meantime :)

Share this post


Link to post
Share on other sites

I think only reports and not suggestions, requests, and questions should go on the tracker. We don't want to replace the forums. Just want to see a list of all known issues and an idea of how soon it might be fixed.

Share this post


Link to post
Share on other sites
6 hours ago, Stroam said:

I think only reports and not suggestions, requests, and questions should go on the tracker. We don't want to replace the forums. Just want to see a list of all known issues and an idea of how soon it might be fixed.

I somewhat agree, but on the other hand, blanket-banning something that could possibly open an interesting and deep discussion would be unfortunate. Tyron said we could just file it under "let's wait and see". If gameplay suggestions become unmanagable on the tracker, we can always take it back.

Share this post


Link to post
Share on other sites

Hmm, it is still unclear if I should move all my suggestions to the tracker or not. Also some of the suggestions are additions to suggestions from others ...

And what to do with huge suggestion discussions, like ore / prospecting?

Maybe I should move only ones if Tyron explicitly says in forum thread "ok, I like it, I will do this some day"?

  • Confused 1

Share this post


Link to post
Share on other sites
36 minutes ago, heptagonrus said:

Hmm, it is still unclear if I should move all my suggestions to the tracker or not. Also some of the suggestions are additions to suggestions from others ...

And what to do with huge suggestion discussions, like ore / prospecting?

Maybe I should move only ones if Tyron explicitly says in forum thread "ok, I like it, I will do this some day"?

How about concrete small changes/feature requests can go on the issue tracker, whereas bigger changes/additions to the games mechanics on which there is no consensus on it's exact and complete implementation stays on the forum?

  • Like 1

Share this post


Link to post
Share on other sites

@Quentin Preik Yes, thank you for taking the time!

Two tips for next time you report something:

  • Check if another recent issue already has a similar error message or describes a similar issue.
  • If you enclose the error message with triple backticks (```) on a separate line before and after, it will put it in a code-block.
    This way, it won't look all strange from GitHub trying to format the contents of the error message. Other people also miss this.
  • Like 1

Share this post


Link to post
Share on other sites

GitHub terrifies me but I've just tried adding an issue there. I couldn't figure out how to add labels, though. Not sure if that's the best/most efficient place to post issues or if I'd be better off writing here on the forum.

Share this post


Link to post
Share on other sites

@Aira Labels can only be changed by those with access to the repository (as in, the team / developers). In general it's best to go with one of the templates I provided for now as a base, they come with default labels, and I usually go and adjust them if needed. "Bug report" for anything that seems unintentional and "Feature request" for suggestions, enhancements, even feedback I suppose.

The developers generally look at any place you leave feedback, so I don't think there's a best place to do so necessarily. I personally prefer the GitHub issue tracker, but to each their own! If an issue ever appears to get overlooked, you can always bump the thread / issue or poke the team directly on Discord.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.