Open RickyLaChow opened 4 months ago
Confirming this persists for me as well, but switching between methods does not fix it.
CMI plugin version: 9.7.2.12 Velocity CMIB SqLite CMILib: 1.4.7.15 Server: Paper(497) 1.20.4-R0.1-SNAPSHOT- CMI economy: Enabled Vault: 1.7.3-b CMI Chat: Disabled Modules -> 57 enabled 2 disabled: ranks, skin
Could you try pressing F3+B to enable collision box debugging and check if you can see floating hit box when you aim at hologram like this
To me in purpur 1.20.4 (Purpur(2175) 1.20.4-RO.1-SNAPSHOT), the holograms in general work horrible, if you reload the cmi they duplicate, if you go far away and come back they take too long to reappear, etc.
All this happens to me with the latest version of the CMI (9.7.2.12)so far and cmilib (1.4.7.15), when did this start?
When they began to have changes in the holograms with the arrival of 1.20.5/1.20.6. @Zrips
To me in purpur 1.20.4 (Purpur(2175) 1.20.4-RO.1-SNAPSHOT), the holograms in general work horrible, if you reload the cmi they duplicate, if you go far away and come back they take too long to reappear, etc.
All this happens to me with the latest version of the CMI (9.7.2.12)so far and cmilib (1.4.7.15), when did this start?
When they began to have changes in the holograms with the arrival of 1.20.5/1.20.6.
These kinds of things should be expected during update season, tbh, especially with plugins with backwards support or when you're using non-standard software. It usually takes a bit to get everything sorted so it's best to be patient and provide constructive feedback. If you're not willing to do that then staying on older versions is still an option, but just saying things are horrible doesn't help anyone.
To me in purpur 1.20.4 (Purpur(2175) 1.20.4-RO.1-SNAPSHOT), the holograms in general work horrible, if you reload the cmi they duplicate, if you go far away and come back they take too long to reappear, etc. All this happens to me with the latest version of the CMI (9.7.2.12)so far and cmilib (1.4.7.15), when did this start? When they began to have changes in the holograms with the arrival of 1.20.5/1.20.6.
These kinds of things should be expected during update season, tbh, especially with plugins with backwards support or when you're using non-standard software. It usually takes a bit to get everything sorted so it's best to be patient and provide constructive feedback. If you're not willing to do that then staying on older versions is still an option, but just saying things are horrible doesn't help anyone.
I apologize if my message sounded too offensive, I just want to make it clear of your functionality, as long as you are aware of it and fix it in the future I am fine.
If I am required to cooperate with more information I will be available for it.
Few changes will be made with next update, if some of the issues persist, let me know.
Now the holograms work fine again, but there is still a small detail, clicking on the buttons to change pages is unprintable.
If you need more information do not hesitate to ask me.
Edit:
I've got the same issue with holograms not being interactable. Both the old and the new display method for holograms have the same issue, they don't trigger the commands that are attached to the hologram.
Boogschutterhighscores:
Loc: skyblock_world;157.41;84.77;-119.54
HoverParticles:
ShowHover: false
Range: 8
RangeExtra: 16
Interactable: true
Commands:
- '!rightclick!cmi hologrampages Boogschutterhighscores [playerName] next'
- '!shiftrightclick!cmi hologrampages Boogschutterhighscores [playerName] next'
Lines:
- '&7---- * ----'
- '{#orange>}&lBoogschutter Highsco{#e6b173<>}&lres Allertijden{#orange<}&r'
- '&7---- * ----'
- '{#orange}1 &8>> &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_1_alltime_name%
&7- &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_1_alltime_value%'
- '{#orange}2 &8>> &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_2_alltime_name%
&7- &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_2_alltime_value%'
- '{#orange}3 &8>> &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_3_alltime_name%
&7- &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_3_alltime_value%'
- '{#orange}4 &8>> &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_4_alltime_name%
&7- &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_4_alltime_value%'
- '{#orange}5 &8>> &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_5_alltime_name%
&7- &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_5_alltime_value%'
- '&r'
- <T>{#orange>}Meer stat{#e6b173<>}istieken{#orange<}</T><H>{#orange>}&lMeer stat{#e6b173<>}&listieken{#orange<}</H>
- '!nextpage!'
- '&7---- * ----'
- '{#red>}&lBoogschutter Highsc{#e68a8a<>}&lores Wekelijks{#red<}&r'
- '&7---- * ----'
- '{#red}1 &8>> &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_1_weekly_name%
&7- &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_1_weekly_value%'
- '{#red}2 &8>> &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_2_weekly_name%
&7- &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_2_weekly_value%'
- '{#red}3 &8>> &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_3_weekly_name%
&7- &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_3_weekly_value%'
- '{#red}4 &8>> &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_4_weekly_name%
&7- &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_4_weekly_value%'
- '{#red}5 &8>> &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_5_weekly_name%
&7- &f%ajlb_lb_betonquest_questeiland-archeryrange:point.highscore.amount_5_weekly_value%'
- '&r'
- <T>{#red>}Meer stat{#e68a8a<>}istieken{#red<}</T><H>{#red>}&lMeer stat{#e68a8a<>}&listieken{#red<}</H>
I've got the same issue, the next page button may work or may not work sometimes.
This should already be fixed in the latest versions, it should be closed.
No, the problem persists in my server, turn the page few times, then it will stop working for a while. (Player needs to point some where else to trigger the next page button)
No, the problem persists in my server, turn the page few times, then it will stop working for a while. (Player needs to point some where else to trigger the next page button)
Put the details where it happens to you, like which server version, cmi version, etc.
Description of Issue
@Zrips The issue persist i need to use NewMethod: false for make it work in the new versions
Version Information