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

Color Applicator: can't switch colors #3282

Closed
Xiaminou opened this Issue Dec 17, 2017 · 8 comments

Comments

Projects
None yet
4 participants
@Xiaminou

Xiaminou commented Dec 17, 2017

No description provided.

@yueh yueh closed this Dec 17, 2017

@gabor6505

This comment has been minimized.

Show comment
Hide comment
@gabor6505

gabor6505 Dec 21, 2017

I have the same issue, I am also using rv5-stable-3. Also tried without OptiFine.

gabor6505 commented Dec 21, 2017

I have the same issue, I am also using rv5-stable-3. Also tried without OptiFine.

@fscan

This comment has been minimized.

Show comment
Hide comment
@fscan

fscan Dec 21, 2017

Member

Please reproduce with only AE2.

Member

fscan commented Dec 21, 2017

Please reproduce with only AE2.

@fscan

This comment has been minimized.

Show comment
Hide comment
@fscan

fscan Dec 21, 2017

Member

I have no idea. I have a server with a fair amount of mods and never had this issue. Just do the usual stuff: remove half the mods - test - remove the other half - test - etc ... there's nothing "better" any of us can do.

Member

fscan commented Dec 21, 2017

I have no idea. I have a server with a fair amount of mods and never had this issue. Just do the usual stuff: remove half the mods - test - remove the other half - test - etc ... there's nothing "better" any of us can do.

@gabor6505

This comment has been minimized.

Show comment
Hide comment
@gabor6505

gabor6505 Dec 21, 2017

This is actually an AE2 issue, I have just tested this out with only AE2 and Forge 2531. It happens when there is more than 127 of the same paint ball in the Color Applicator. (Note that I have tested this with having 64 of all 16 types of the paint balls in it) So for example if I have more than 127 of brown paint ball, it closes everything else off and I can only select white, black, red and green.
https://youtu.be/L45OEaVQoKc

gabor6505 commented Dec 21, 2017

This is actually an AE2 issue, I have just tested this out with only AE2 and Forge 2531. It happens when there is more than 127 of the same paint ball in the Color Applicator. (Note that I have tested this with having 64 of all 16 types of the paint balls in it) So for example if I have more than 127 of brown paint ball, it closes everything else off and I can only select white, black, red and green.
https://youtu.be/L45OEaVQoKc

@fscan

This comment has been minimized.

Show comment
Hide comment
@fscan

fscan Dec 21, 2017

Member

Ok, i'll look into the issue

Member

fscan commented Dec 21, 2017

Ok, i'll look into the issue

@fscan fscan reopened this Dec 21, 2017

@yueh

This comment has been minimized.

Show comment
Hide comment
@yueh

yueh Dec 21, 2017

Member

Because the original issue did not contain any details besides "does not work". And no some random video does not count, because I won't waste time trying to deduce, if a slight change in the camera angle might indicate holding shift or just a mouse movement due to using the scroll wheel and accidentally moving the mouse.

These things are clearly stated in the readme as well as the issue ticket. They do not exist to annoy you, but to get as much information as possible without having to waits days for basic details.

Also you said, you won't waste 10 or more hours on a bug. So do not expect, that we have the time to do it. If it is a modpack, report it to their authors, they should know about incompatibilites. If you're the author, that's basically your task to do. If we know which mods cause it (or just a description to reproduce it), we will fix it. But we won't spend time on fetching every single one of your mod and debug your modpack.

Member

yueh commented Dec 21, 2017

Because the original issue did not contain any details besides "does not work". And no some random video does not count, because I won't waste time trying to deduce, if a slight change in the camera angle might indicate holding shift or just a mouse movement due to using the scroll wheel and accidentally moving the mouse.

These things are clearly stated in the readme as well as the issue ticket. They do not exist to annoy you, but to get as much information as possible without having to waits days for basic details.

Also you said, you won't waste 10 or more hours on a bug. So do not expect, that we have the time to do it. If it is a modpack, report it to their authors, they should know about incompatibilites. If you're the author, that's basically your task to do. If we know which mods cause it (or just a description to reproduce it), we will fix it. But we won't spend time on fetching every single one of your mod and debug your modpack.

@yueh

This comment has been minimized.

Show comment
Hide comment
@yueh

yueh Dec 21, 2017

Member

The other issues at least have some useful information. This was nothing but a video link. And a video simply does not hint about anything you did. E.g. you could assume that shift + right click does switch the colours. Or shift and the +/- key. We don't know it.

"Does not work" without any information are pretty much the only issues I immediately close, because there is absolutely no effort done by the reporter. So simply do not expect that I put more effort into it and waste half an hour to imagine most things you might have done wrong and put them into some reasonable questions.

Member

yueh commented Dec 21, 2017

The other issues at least have some useful information. This was nothing but a video link. And a video simply does not hint about anything you did. E.g. you could assume that shift + right click does switch the colours. Or shift and the +/- key. We don't know it.

"Does not work" without any information are pretty much the only issues I immediately close, because there is absolutely no effort done by the reporter. So simply do not expect that I put more effort into it and waste half an hour to imagine most things you might have done wrong and put them into some reasonable questions.

yueh added a commit that referenced this issue Dec 21, 2017

@fscan

This comment has been minimized.

Show comment
Hide comment
@fscan

fscan Dec 21, 2017

Member

We are generally thankful for bug report if they are well documented and ideally reproducible. Your original report was "There's something wrong, but it's not your fault .. help me fix it". A issue like this will get closed in every bug tracker i know of.
And remember that this is a community project. Nobody is getting paid or has a obligation to work on it. We like to do it and keep it as bug free as possible, but our time is limited and we cannot look at every issue in detail if there's not enough information attached to it.
As it turns out, thanks to @gabor6505 it was actually a bug on our end and got fixed in the end.

Member

fscan commented Dec 21, 2017

We are generally thankful for bug report if they are well documented and ideally reproducible. Your original report was "There's something wrong, but it's not your fault .. help me fix it". A issue like this will get closed in every bug tracker i know of.
And remember that this is a community project. Nobody is getting paid or has a obligation to work on it. We like to do it and keep it as bug free as possible, but our time is limited and we cannot look at every issue in detail if there's not enough information attached to it.
As it turns out, thanks to @gabor6505 it was actually a bug on our end and got fixed in the end.

@yueh yueh closed this in 50fad68 Dec 21, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment