Guild Ownership Transfer to Bot User

(#107) Bug Fixed api community

7mo agoby RexSystem edited originally by @Radiant-Xyz on GitHub

Summary

I've noticed that the UI of the app provides an option to transfer the ownership of a guild to bot users. I have not attempted to actually confirm the transfer, so this issue might be limited to the UI. It might be worth to double-check whether the underlying API would catch and reject this request. It is also worth noting that the option is not marked as dangerous (red text) unlike the other dangerous options (Kick, Ban, etc.).

Steps to reproduce

Go to User Settings > Developer > Applications
Create a new application
Invite the app with the bot scope to a server you own
Right click the bot in the "Members" menu and choose "Transfer Ownership"

Environment (optional)

stable (15cfdfb), 2026-02-16 01:06:50 UTC, Electron 39.2.7, Linux 6.17.7-ba25.fc43.x86_64 (x64), desktop stable 0.0.8

Logs or screenshots (optional)

Notice the "BOT" tag on the right: image Context menu shows "Transfer Ownership" option: image Clicking it shows the Transfer Ownership confirmation dialog: image

550228768-a1274627-bdc8-44e3-91d3-f0a471ee788b.png
572×201 | 32 kB
550228454-028d04f7-8697-448b-aad2-d2d595fce7cf.png
455×520 | 40 kB
550228515-c9c4ae3d-fc3a-496d-995e-9d490286bfce.png
456×272 | 23 kB

History

7 comments

tempest:squll.fartcore.ai 1 vote 7mo ago originally by @HellishBro on GitHub

i can confirm this works and does exactly what you expect. my bot is now my guild owner

Permalink

RexSystem 1 vote 7mo ago edited originally by @Radiant-Xyz on GitHub OP

I hope it was just a test guild @HellishBro. Otherwise... good luck getting it back.

Permalink

RexSystem 1 vote 7mo ago originally by @Blaze-Wolf on GitHub

Yeah it was just a test guild I can confirm.

Permalink

RexSystem 1 vote 7mo ago originally by @Radiant-Xyz on GitHub OP

Thank you for the PR. I would recommend to patch the API to catch this edge case as well, just to make sure this cannot happen. If I am correct this might be the right place to catch it and throw an error: https://github.com/fluxerapp/fluxer/blob/cb316085235723e68fce5b5b7f86befca8e47c09/fluxer_api/src/guild/services/data/GuildOwnershipService.ts#L52-L55 Adding the check right below that if block.

Permalink

tempest:squll.fartcore.ai 1 vote 7mo ago edited by moderator originally by @HellishBro on GitHub

@hampus-fluxer hello, im actually thinking of having a new error for this kind of stuff, what are your thoughts on it?

Permalink

RexSystem 1 vote 7mo ago originally by @Jiralite on GitHub Collapsed as outdated by Rex: The refactor has landed.

Right now, it's advised to wait before making any pull requests, code changes, or otherwise due to the note in the README.md:

Over the past month, I've been working on a major refactor that touches every part of the codebase.

Once the refactor lands in this codebase, you can continue contributing!

Permalink

RexSystem 1 vote 7mo ago originally by @Radiant-Xyz on GitHub OP

This issue has been fixed in d5abd1a7e4bbb6a389b7ecdf7b24c573bf71fc88. Client UI - https://github.com/fluxerapp/fluxer/blob/d5abd1a7e4bbb6a389b7ecdf7b24c573bf71fc88/fluxer_app/src/components/uikit/context_menu/GuildMemberContextMenu.tsx#L92 Server API - https://github.com/fluxerapp/fluxer/blob/d5abd1a7e4bbb6a389b7ecdf7b24c573bf71fc88/packages/api/src/guild/services/data/GuildOwnershipService.tsx#L63-L66

Permalink