Health is on top of the second hotbar
Deykii opened this issue ยท 8 comments
I tried to use Double Hotbar 1.3.2.1, fabric version. There is still that problem....
Double hotbar version, modloader, and game version? This is a bug a found in earlier releases of the forge version of the mod. It should be resolved in the latest versions.
Double hotbar version, modloader, and game version? This is a bug a found in earlier releases of the forge version of the mod. It should be resolved in the latest versions.
Version: 1.3.1-1.20.1
Modloader: Fabric
Game version: 1.20.1
Are you using any other mods? When I initially saw this issue it reminded me of a forge issue I had recently but that was taking place in creative mode, so this is not the same bug. If you are in survival mode with default double hotbar settings and no other mods it should work right out of the box. Please try running with just double hotbar, fabric api, and cloth config installed with a new .minecraft folder. If the bug still persists then we can discuss what else it could be but between me and all play testers I've spoken with no one has had any issues with the status bars not moving in survival mode. If that is the case please reply with the version of the fabric loader, fabric api, cloth config, and double hotbar version so I can attempt to recreate the issue.
Are you using any other mods? When I initially saw this issue it reminded me of a forge issue I had recently but that was taking place in creative mode, so this is not the same bug. If you are in survival mode with default double hotbar settings and no other mods it should work right out of the box. Please try running with just double hotbar, fabric api, and cloth config installed with a new .minecraft folder. If the bug still persists then we can discuss what else it could be but between me and all play testers I've spoken with no one has had any issues with the status bars not moving in survival mode. If that is the case please reply with the version of the fabric loader, fabric api, cloth config, and double hotbar version so I can attempt to recreate the issue.
I also encountered the same problem, as shown below:
I tried to get the module to stop displaying the second line to fix the problem, but there was also a problem:
It is worth noting that when I enable the display second line shortcut bar, sometimes all the ICONS are in the correct position, and sometimes the problems I mentioned above occur.
My gaming environment is as follows:
Minecraft: 1.20.1
Fabric Loader: 0.15.11
JVM: graalvm-jdk-21.0.2+13.1
Here is the relevant information about the mods I have installed:
- adaptive-tooltips 1.3.0
- advancementinfo 1.20-fabric0.83.0-1.4
- appleskin 2.5.1+mc1.20
- architectury 9.2.14
- betterclouds 1.3.17+1.20.1
- betterpingdisplay 1.1.1
- bookshelf 20.1.11
- c2me 0.2.0+alpha.11.5
|-- c2me-base 0.2.0+alpha.11.5
|-- c2me-client-uncapvd 0.2.0+alpha.11.5
|-- c2me-fixes-chunkio-threading-issues 0.2.0+alpha.11.5
|-- c2me-fixes-general-threading-issues 0.2.0+alpha.11.5
|-- c2me-fixes-worldgen-threading-issues 0.2.0+alpha.11.5
|-- c2me-fixes-worldgen-vanilla-bugs 0.2.0+alpha.11.5
|-- c2me-notickvd 0.2.0+alpha.11.5
|-- c2me-opts-allocs 0.2.0+alpha.11.5
|-- c2me-opts-chunk-access 0.2.0+alpha.11.5
|-- c2me-opts-chunkio 0.2.0+alpha.11.5
|-- c2me-opts-math 0.2.0+alpha.11.5
|-- c2me-opts-scheduling 0.2.0+alpha.11.5
|-- c2me-opts-worldgen-general 0.2.0+alpha.11.5
|-- c2me-opts-worldgen-vanilla 0.2.0+alpha.11.5
|-- c2me-rewrites-chunk-serializer 0.2.0+alpha.11.5
|-- c2me-rewrites-chunkio 0.2.0+alpha.11.5
|-- c2me-server-utils 0.2.0+alpha.11.5
|-- c2me-threading-chunkio 0.2.0+alpha.11.5
|-- c2me-threading-lighting 0.2.0+alpha.11.5
|-- c2me-threading-worldgen 0.2.0+alpha.11.5
|-- com_electronwill_night-config_core 3.6.5
|-- com_electronwill_night-config_toml 3.6.5
|-- com_ibm_async_asyncutil 0.1.0
|-- net_objecthunter_exp4j 0.4.8
\-- org_threadly_threadly 7.0
- centered-crosshair 1.0.6+b2
- cloth-config 11.1.118
\-- cloth-basic-math 0.6.1
- completeconfig 2.5.0
|-- completeconfig-base 2.5.0
|-- completeconfig-gui-cloth 2.5.0
\-- completeconfig-gui-yacl 2.5.0
- constantmusic 1.0.1
\-- com_moandjiezana_toml_toml4j 0.7.2
- continuity 3.0.0-beta.5+1.20.1
- coroutil 1.20.1-1.3.7
\-- forgeconfigapiport 8.0.0
- dark-loading-screen 1.6.14
- debugify 1.20.1+2.0
- double_hotbar 1.3.1-mc1.20.1-fabric
- enchdesc 17.0.16
- enchlevel-langpatch 2.2.2
- enhancedblockentities 0.9+1.20
|-- advanced_runtime_resource_pack 0.6.7
\-- spruceui 5.0.0+1.20
- entityculling 1.6.5
- exordium 1.2.1-mc1.20.1
- explosiveenhancement 1.2.2-1.20.x
- fabric-api 0.92.2+1.20.1
|-- fabric-api-base 0.4.31+1802ada577
|-- fabric-api-lookup-api-v1 1.6.36+1802ada577
|-- fabric-biome-api-v1 13.0.13+1802ada577
|-- fabric-block-api-v1 1.0.11+1802ada577
|-- fabric-block-view-api-v2 1.0.1+1802ada577
|-- fabric-blockrenderlayer-v1 1.1.41+1802ada577
|-- fabric-client-tags-api-v1 1.1.2+1802ada577
|-- fabric-command-api-v1 1.2.34+f71b366f77
|-- fabric-command-api-v2 2.2.13+1802ada577
|-- fabric-commands-v0 0.2.51+df3654b377
|-- fabric-containers-v0 0.1.64+df3654b377
|-- fabric-content-registries-v0 4.0.11+1802ada577
|-- fabric-convention-tags-v1 1.5.5+1802ada577
|-- fabric-crash-report-info-v1 0.2.19+1802ada577
|-- fabric-data-attachment-api-v1 1.0.0+de0fd6d177
|-- fabric-data-generation-api-v1 12.3.4+1802ada577
|-- fabric-dimensions-v1 2.1.54+1802ada577
|-- fabric-entity-events-v1 1.6.0+1c78457f77
|-- fabric-events-interaction-v0 0.6.2+1802ada577
|-- fabric-events-lifecycle-v0 0.2.63+df3654b377
|-- fabric-game-rule-api-v1 1.0.40+1802ada577
|-- fabric-item-api-v1 2.1.28+1802ada577
|-- fabric-item-group-api-v1 4.0.12+1802ada577
|-- fabric-key-binding-api-v1 1.0.37+1802ada577
|-- fabric-keybindings-v0 0.2.35+df3654b377
|-- fabric-lifecycle-events-v1 2.2.22+1802ada577
|-- fabric-loot-api-v2 1.2.1+1802ada577
|-- fabric-loot-tables-v1 1.1.45+9e7660c677
|-- fabric-message-api-v1 5.1.9+1802ada577
|-- fabric-mining-level-api-v1 2.1.50+1802ada577
|-- fabric-model-loading-api-v1 1.0.3+1802ada577
|-- fabric-models-v0 0.4.2+9386d8a777
|-- fabric-networking-api-v1 1.3.11+1802ada577
|-- fabric-networking-v0 0.3.51+df3654b377
|-- fabric-object-builder-api-v1 11.1.3+1802ada577
|-- fabric-particles-v1 1.1.2+1802ada577
|-- fabric-recipe-api-v1 1.0.21+1802ada577
|-- fabric-registry-sync-v0 2.3.3+1802ada577
|-- fabric-renderer-api-v1 3.2.1+1802ada577
|-- fabric-renderer-indigo 1.5.2+85287f9f77
|-- fabric-renderer-registries-v1 3.2.46+df3654b377
|-- fabric-rendering-data-attachment-v1 0.3.37+92a0d36777
|-- fabric-rendering-fluids-v1 3.0.28+1802ada577
|-- fabric-rendering-v0 1.1.49+df3654b377
|-- fabric-rendering-v1 3.0.8+1802ada577
|-- fabric-resource-conditions-api-v1 2.3.8+1802ada577
|-- fabric-resource-loader-v0 0.11.10+1802ada577
|-- fabric-screen-api-v1 2.0.8+1802ada577
|-- fabric-screen-handler-api-v1 1.3.30+1802ada577
|-- fabric-sound-api-v1 1.0.13+1802ada577
|-- fabric-transfer-api-v1 3.3.5+8dd72ea377
\-- fabric-transitive-access-wideners-v1 4.3.1+1802ada577
- fabric-language-kotlin 1.11.0+kotlin.2.0.0
|-- org_jetbrains_kotlin_kotlin-reflect 2.0.0
|-- org_jetbrains_kotlin_kotlin-stdlib 2.0.0
|-- org_jetbrains_kotlin_kotlin-stdlib-jdk7 2.0.0
|-- org_jetbrains_kotlin_kotlin-stdlib-jdk8 2.0.0
|-- org_jetbrains_kotlinx_atomicfu-jvm 0.24.0
|-- org_jetbrains_kotlinx_kotlinx-coroutines-core-jvm 1.8.1
|-- org_jetbrains_kotlinx_kotlinx-coroutines-jdk8 1.8.1
|-- org_jetbrains_kotlinx_kotlinx-datetime-jvm 0.6.0
|-- org_jetbrains_kotlinx_kotlinx-serialization-cbor-jvm 1.6.3
|-- org_jetbrains_kotlinx_kotlinx-serialization-core-jvm 1.6.3
\-- org_jetbrains_kotlinx_kotlinx-serialization-json-jvm 1.6.3
- fabricloader 0.15.11
\-- mixinextras 0.3.5
- faster_entity_animations 1.6
- ferritecore 6.0.1
- fpsreducer 1.20-2.5
- i18nupdatemod 3.5.5
- icterine 1.3.0
- imblocker 4.0.5
- immediatelyfast 1.2.17+1.20.4
\-- net_lenni0451_reflect 1.3.3
- indium 1.0.30+mc1.20.4
- inventoryprofilesnext 1.10.10
- jade 11.9.2+fabric
- jadeaddons 5.2.5
- java 21
- ksyxis 1.3.1
- lambdynlights 2.3.2+1.20.1
|-- pride 1.2.0+1.19.4
\-- spruceui 5.0.0+1.20
- libipn 4.0.2
- litematica 0.15.3
- lithium 0.11.2
- magiclib 0.7.398+fe2125a-stable
\-- magiclib-1_20_1 0.7.398+fe2125a-stable
- malilib 0.16.3
- memoryleakfix 1.1.5
- minecraft 1.20.1
- modernfix 5.18.0+mc1.20.1
- modmenu 7.2.2
- moreoverlays 1.22.4.2-fabric
- nerb 0.3
- nicer-skies 1.3.0
- nvidium 0.2.6-beta
- player-animator 1.0.2-rc1+1.20
- reeses-sodium-options 1.7.2+mc1.20.1-build.101
- reicollapsibleentries 3.1.0
- roughlyenoughitems 12.1.725
\-- error_notifier 1.0.9
- roughlyenoughprofessions 2.0.2
- roughlyenoughresources 2.9.0
- shut_up_gl_error 1.0.0
- skinlayers3d 1.6.5
- sodium 0.5.8+mc1.20.1
- sodium-extra 0.5.4+mc1.20.1-build.115
|-- caffeineconfig 1.3.0+1.17
\-- crowdin-translate 1.4+1.19.3
- statuseffecttimer 1.2.0+1.20
- supermartijn642configlib 1.1.8+a
- supermartijn642corelib 1.1.17
- videotape 1.0.0
- voicechat 1.20.1-2.5.15
- watut 1.20.1-1.1.1
\-- forgeconfigapiport 8.0.0
- xaerominimap 24.2.0
- xaeroworldmap 1.38.8
- yet_another_config_lib_v3 3.4.4+1.20.1-fabric
|-- com_twelvemonkeys_common_common-image 3.10.0
|-- com_twelvemonkeys_common_common-io 3.10.0
|-- com_twelvemonkeys_common_common-lang 3.10.0
|-- com_twelvemonkeys_imageio_imageio-core 3.10.0
|-- com_twelvemonkeys_imageio_imageio-metadata 3.10.0
|-- com_twelvemonkeys_imageio_imageio-webp 3.10.0
|-- org_quiltmc_parsers_gson 0.2.1
\-- org_quiltmc_parsers_json 0.2.1
- zoomify 2.13.5+1.20.1
|-- com_akuleshov7_ktoml-core-jvm 0.5.1
|-- dev_isxander_settxi_settxi-core 2.10.6
\-- dev_isxander_settxi_settxi-kotlinx-serialization 2.10.6
I really like the functionality of this module and hope to be able to fix this issue in the future!
New discovery! After disabling the display of the second row of hotbars and restarting the game, the display appears to have returned to normal.
I have yet again tested with a clean installation using just double hotbar 1.3.1 for 1.20.1, fabric api, cloth config, and mod menu. I experienced no issues. Even changing double hotbar settings I could not reproduce this bug. I believe this is likely a compatibility issue with one of the other mods listed above. I am marking this issue as resolved, but if someone can identify the problematic mod and provide me a list of steps to reproduce the error then I am happy to revisit the issue. Just create a new issue and list it as a compatibility problem instead of a general bug with the mod.