MC1110 (Wireless Transmitter) not activated by repeater powering the sign directly from the front, contradicting documented behavior

[Carl-OS15]

CraftBook Version

craftbook-3.10.13

Platform Version

paper-1.21.11-132 minecraft 1.21.11

Confirmations

• I am using the most recent Minecraft release.
• I am using a version of WorldEdit compatible with my Minecraft version.
• I am using a version of CraftBook compatible with my Minecraft version.
• I am using the latest or recommended version of my platform software.
• I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
• I am NOT using a fork of WorldEdit, such as FastAsyncWorldEdit (FAWE) or AsyncWorldEdit (AWE)

Bug Description

According to the MC1110 documentation, the transmitter should activate
when powered "from the front or either side" of the Wall Sign block.
Powering the sign block directly from the front via a Redstone Repeater
no longer activates the transmitter. This makes compact wireless
transmitter setups (multiple transmitters placed close together, each
fed by its own repeater from the front) impossible, which used to work
fine in Minecraft 1.7.10-era CraftBook.

Expected Behavior

Per the official documentation, a redstone signal fed into the front (or
either side) of the Wall Sign block should activate the transmitter,
exactly as it did in earlier CraftBook/Minecraft versions (e.g. 1.7.10).
A Repeater powering the sign block directly from the front should
reliably trigger the transmitter, allowing compact setups with multiple
transmitters placed close together, each individually fed by its own
repeater.

Reproduction Steps

1. Build a standard MC1110 Wireless Transmitter (Wall Sign with
   [MC1110] and narrowband/wideband config, lever on the back).
2. Place a Redstone Repeater directly in front of the Wall Sign, facing
   into it, and power the repeater's input.
3. Observe: the transmitter does not activate (the configured band does
   not go high), despite the repeater delivering power directly to the
   front face of the sign block.

Anything Else?

CraftBook 3.10.12 (1.21.3-1.21.11) - reproduced
CraftBook 3.10.13 (1.21.5-26.2) - reproduced

[me4502]

Spigot/Paper are fairly bad at sending redstone events consistently, these issues occur when the underlying platform fails to send the correct redstone events in the correct spots. Repeaters have been notoriously poorly supported in both Spigot/Paper over the years. This issue has disappeared and re-appeared a few times over the lifecycle of the Bukkit API, as the server platforms have rewritten how their redstone systems work.

As you're using Paper, the best recommendation is to disable any of the "alternate redstone algorithm" settings, as those almost entirely break Bukkit redstone events. If that's already disabled, then this is a bug that must be fixed on Paper's end

[Carl-OS15]

Thank you so much for the quick and helpful response!

With your explanation as a starting point, I dug into the CraftBook source
with some debug logging and was able to confirm exactly what you described:
BlockRedstoneEvent simply isn't firing for the Repeater block in this
setup, even with redstone-implementation set to VANILLA on Paper.

Since that rules out a CraftBook-side issue, I've opened a bug report with
the Paper team, including the debug findings as reproduction steps:
PaperMC/Paper#14169

Really appreciate you taking the time to point me in the right direction -
saved me a lot of guessing! CraftBook is still a joy to use after all these
years, thanks for keeping it alive.