-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Suggestion] Block placement preview #8
Comments
I'm a little bit confused by this as vanilla shows an outline when bridging is not being used. Are you suggesting shifting that vanilla outline from the block you can break to the air gap where you can place? |
Ahh awesome. Adding that shouldn't be too bad then. Will consider fancy outlines for a later update but a simple box will do for now. Should be in the next update! :] |
- Not shown when colliding with the player - Can optionally respect crouching + bridging enabled/disabled rules - Has its own configuration for visibility (F3 + Normal) Signed-off-by: Will Scully <16578982+squeeglii@users.noreply.github.com>
Implemented with a few config options - it's off by default but the you can find the setting in the "Visual" category. Will be in v2.3.0. Thanks for the suggestion! |
Have you set the lines to full opacity? The colour |
yes im using |
Signed-off-by: Will Scully <16578982+squeeglii@users.noreply.github.com> Change how mappings work slightly to make sources more compatible Signed-off-by: Will Scully <16578982+squeeglii@users.noreply.github.com> Bump version & update readme with credit for translations. Removes versions from README as they end up falling out of sync anyway. Signed-off-by: Will Scully <16578982+squeeglii@users.noreply.github.com> Crosshair is now hidden when bridging is disabled Signed-off-by: Will Scully <16578982+squeeglii@users.noreply.github.com> Implement Suggestion #8 - Non-Bridging outlines are now shown. - Not shown when colliding with the player - Can optionally respect crouching + bridging enabled/disabled rules - Has its own configuration for visibility (F3 + Normal) Signed-off-by: Will Scully <16578982+squeeglii@users.noreply.github.com> Mexican Spanish translation Heyy just a small translation i made, hope it helps
Strange - it didn't look the same on my end. Are you using any mods that modify your graphics? |
Signed-off-by: Will Scully <16578982+squeeglii@users.noreply.github.com> Change how mappings work slightly to make sources more compatible Signed-off-by: Will Scully <16578982+squeeglii@users.noreply.github.com> Bump version & update readme with credit for translations. Removes versions from README as they end up falling out of sync anyway. Signed-off-by: Will Scully <16578982+squeeglii@users.noreply.github.com> Crosshair is now hidden when bridging is disabled Signed-off-by: Will Scully <16578982+squeeglii@users.noreply.github.com> Implement Suggestion #8 - Non-Bridging outlines are now shown. - Not shown when colliding with the player - Can optionally respect crouching + bridging enabled/disabled rules - Has its own configuration for visibility (F3 + Normal) Signed-off-by: Will Scully <16578982+squeeglii@users.noreply.github.com> Mexican Spanish translation Heyy just a small translation i made, hope it helps Signed-off-by: Will Scully <16578982+squeeglii@users.noreply.github.com>
okay it looks like its caused by Iris Shaders, even if no shader pack is currently being used. i could reproduce it with just the following mods:
as soon as i remove Iris Shaders, it works as intended. very strange. |
fuuuun, I love vague and mysterious graphical bugs. 💀 Will move this into a new issue. Not sure how long it'll take to fix as it's quite minor and doesn't have a clear cause, but I'll take a look either way. |
i really like the "Bridge-assist block outline" feature, and would like to suggest an option to always show a block placement preview, not just when bridging. this way we could use your mod as a general purpose block placement preview mod. it should of course respect the "Only use bridge-assist while crouching" setting.
The text was updated successfully, but these errors were encountered: