(Blockutis) console output event does not detect all console output?

[vital drum]

Denizen: build 1791
Paper: git-Paper-514 (MC: 1.19.4)

I want to detect when a player buys items from a ChestShop shop, and run some commands when that happens.
But, for some reason i am unable to detect the console output. It seems like only Denizen console output is detected by the event?

I enabled redirect_logging in the config and also set it to true. I set up a simple event to narrate a message to myself whenever console output is detected.

Script:

    debug: false
    type: world
    events:
        after console output:
        - narrate targets:<player[8950c8ae-482c-4287-aa0d-2ee258788322]> "hello"```

i put some miscellaneous plugins on my test server for testing console output. But from my testing, no console output other then Denizen output was detected. full latest.log:
https://pastebin.com/XqQz91f6

[shrewd quartz]

(Blockutis) console output event does not detect all console output?

[shrewd quartz]

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>

[vital drum]

some specific examples of console output that wasnt detected:

[ChestShop] Blockutis created an Admin Shop - 33Dirt - B 1 - at [world] 374, 76, -39
[Essentials] CONSOLE issued server command: /eco give Blockutis 100
$100 added to Blockutis account. New balance: $100
[ChestShop] Blockutis bought 1 Dirt for 1.00 from Admin Shop at [world] 374, 76, -39
Made Blockutis a server operator
[Towny] [Global Message] Blockutis created a new town called test
[Towny] [Global Message] The town of test has been deleted!
[Essentials] Blockutis was denied access to command.
[LibsDisguises] Now looking for update on Jenkins..

all of these are messages printed to the console... Why arent they detected as console output??

and if there is a better way of detecting someone buying from a chestshop like that, or detecting an event from another plugin that isnt incorporated into denizen, please let me know!

[clear lodge]

Might be related to the way these plugins log/paper changes? probably worth looking into unrelated to this, but for your use case

A. if the plugin has a public free jar, can always request Depenizen support
B.

!e internal bukkit

[craggy tiger]

Event: internal bukkit event

Group

Server

**WARNING**

This exists primarily for testing/debugging, and is almost never a good idea to include in a real script.

Event Lines

internal bukkit event

Switches

event:<path> (required) to specify the Bukkit event path to use (like "event:org.bukkit.event.block.BlockBreakEvent")

Triggers

when the specified internal Bukkit event fires. Useful for testing/debugging, or for interoperation with external plugins that have their own Bukkit events. Get the raw event via 'context.reflect_event'.

Cancellable

True - this adds <context.cancelled> and determines cancelled + cancelled:false.

[clear lodge]

There is this if the plugin has any events, although generally requires a bit of Java knowledge to use so adding proper support is preferred

[vital drum]

alright, how would i go about getting it supported by Depenizen?

can i just send a link to the plugin here?

[clear lodge]

Well, probably a separate post as this is still potentially a relevant issue, but yeah make a feature thread with the relevant links

[vital drum]

alright, ill make the thread in a bit. until Depenizen support (hopefully) gets added, ill see if i can use the internal bukkit event event

[dry crypt]

Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

@vital drum

[vital drum]

I thought you wanted this thread to stay open:

[vital drum]

.

[clear lodge]

Ah yeah - can seem to replicate, so will mark it as a bug for now

[dry crypt]

Changed to Bug

Thread is now a Bug thread. This indicates a core code bug that a developer must resolved, not an error message or other support topic. Please do not misuse the Bug label. Use </helpthread:1028674284870180883> to switch the thread back to a normal help thread if you are not 100% confident it is a code bug.