I'm using the latest pyMC_repeater with the pyMC:Console using the feat/companion branch.
When I use a virtual companion and set the region #nl-li then https://mc-radar.woodwar.com/ reports that the message is scoped but does not report the correct region.
When I use a normal companion with the same region mc-radar reports the correct scope.
The raw data with a incorrect scope: 140947000000033324E474620D31BFBB3909337DCA3AB51D560F9538D47C846788E7964BFA9305986E
The raw data with a correct scope: 14E5FB0000000355C90FB10B0890DC0119C39C7FC89B345B37F83EE17CC071D793832C0E65F2AF8B67
I'm using the latest pyMC_repeater with the pyMC:Console using the feat/companion branch.
When I use a virtual companion and set the region `#nl-li` then https://mc-radar.woodwar.com/ reports that the message is scoped but does not report the correct region.
When I use a normal companion with the same region mc-radar reports the correct scope.
The raw data with a incorrect scope:
`140947000000033324E474620D31BFBB3909337DCA3AB51D560F9538D47C846788E7964BFA9305986E`
The raw data with a correct scope:
`14E5FB0000000355C90FB10B0890DC0119C39C7FC89B345B37F83EE17CC071D793832C0E65F2AF8B67`
<!-- github-sync-id:4091018934 -->
Thanks for the report. This was a testing blindspot because my region doesn't use regions yet. I'll give this a look.
Thanks for the report. This was a testing blindspot because my region doesn't use regions yet. I'll give this a look.
<!-- github-comment-id:4077983794 -->
I think maybe that needs to be fixed as part of this as well?
Region handling in general is just completely broken right now.
See https://github.com/rightup/pyMC_Repeater/issues/96 that I raised a little while back.
I think maybe that needs to be fixed as part of this as well?
<!-- github-comment-id:4078096204 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I'm using the latest pyMC_repeater with the pyMC:Console using the feat/companion branch.
When I use a virtual companion and set the region
#nl-lithen https://mc-radar.woodwar.com/ reports that the message is scoped but does not report the correct region.When I use a normal companion with the same region mc-radar reports the correct scope.
The raw data with a incorrect scope:
140947000000033324E474620D31BFBB3909337DCA3AB51D560F9538D47C846788E7964BFA9305986EThe raw data with a correct scope:
14E5FB0000000355C90FB10B0890DC0119C39C7FC89B345B37F83EE17CC071D793832C0E65F2AF8B67Thanks for the report. This was a testing blindspot because my region doesn't use regions yet. I'll give this a look.
Region handling in general is just completely broken right now.
See https://github.com/rightup/pyMC_Repeater/issues/96 that I raised a little while back.
I think maybe that needs to be fixed as part of this as well?