//inspect does not show who performed the worldedit operation

[Overwrite987]

Server Implementation

Paper

Server Version

1.20.4

Describe the bug

When performing a worldedit operation, you cannot see through //inspect who performed it. it will write that no operation was performed, although it was not.

To Reproduce

1. Install fawe
2. use //set or other operation
3. try to check it with //inspect
4. you'll see that it shows nothing

Expected behaviour

it should show who performed the worldedit operation.

Screenshots / Videos

https://drive.google.com/file/d/1cuFBxBx7sSKW3hK30KPHhtgTlclyfK4w/view?usp=sharing

Error log (if applicable)

No response

Fawe Debugpaste

https://athion.net/ISPaster/paste/view/3dec3480cb1c44fa823de6ba4c88196a

Fawe Version

FastAsyncWorldEdit-646

Checklist

• I have included a Fawe debugpaste.
• I am using the newest build from https://ci.athion.net/job/FastAsyncWorldEdit/ and the issue still persists.

Anything else?

No response

[OneLiteFeather]

Can reproduce this behaviour with fawe 659 and paper 1.20.4 (409), looks like there has something changed.

[LordKnish]

Yep still exists in 659. I am not sure what to do about this because its a pretty big issue that opens up servers for griefing

[OneLiteFeather]

Yep still exists in 659. I am not sure what to do about this because its a pretty big issue that opens up servers for griefing

does it affect griefing if you already put in trust when you give normal players worldedit permissions? Could be more an issue for other plugins relying on this feature if the bug is also happing for example on Coreprotect regarding the worldedit changes.
Can anyone check the severity and how to fix the bug? PRs are welcome.

[NotMyFault]

does it affect griefing if you already put in trust when you give normal players worldedit permissions?

It doesn't. All that happens - or doesn't happen in that case - is a lacking ingame output of the history of actions.
The data is written correctly to the database still and can be accessed at any time if needed.

[OneLiteFeather]

So it is just an display issue?

[NotMyFault]

So it is just an display issue?

Yes.

[LordKnish]

Rollback doesn't work though. I am unable to rollback

…

On Tue, Feb 13, 2024, 5:22 PM Alexander Brandes ***@***.***> wrote: So it is just an display issue? Yes. — Reply to this email directly, view it on GitHub <#2555 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABU7K7BGXKSCF76A6DHFJSTYTOAL5AVCNFSM6AAAAABCODGS6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBRG43TCNBZGY> . You are receiving this because you commented.Message ID: ***@***.***>

[NotMyFault]

Rollback doesn't work though. I am unable to rollback
…
On Tue, Feb 13, 2024, 5:22 PM Alexander Brandes @.> wrote: So it is just an display issue? Yes. — Reply to this email directly, view it on GitHub <#2555 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABU7K7BGXKSCF76A6DHFJSTYTOAL5AVCNFSM6AAAAABCODGS6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBRG43TCNBZGY . You are receiving this because you commented.Message ID: @.>

That would be a different issue then, in that case, please file a separate issue.