# Multi-Platform Engagement

* On Twitter (X) our official Buddy account (and occasionally individual Buddy personas in rotation) tweets skits, insights, and replies in character. Imagine a Buddy responding humorously to Vitalik’s tweets or commenting on MegaETH upgrades in a playful tone. These in-character interactions make our social media presence lively and distinct. People aren’t just following a project’s announcements – they’re following a quirky cast of Buddies and their adventures.

{% embed url="<https://x.com/mega_buddies>" %}

* On Discord we maintain an active presence in the MegaETH Discord and related ecosystem project servers, often role-playing as Buddies. The Buddies chime into daily conversations, share inside jokes, and encourage others with our “Build Different” ideology. This consistent engagement supports our image as the friendly rebels of MegaETH and keeps Mega Buddies in the spotlight without shilling – we’re contributing to conversations, not just promoting ourselves.

* On Telegram, the experience is gamified, personal, and interactive. Our primary hangout is the community chat where Buddies mix with members in signature tone – cheeky, weird, and oddly wise. Alongside that, our announcement channel keeps followers updated on everything from drops to quests, all delivered with that unmistakable Buddy flair.

{% embed url="<https://t.me/megabuddiesann>" %}

{% embed url="<https://t.me/megabuddies>" %}

But Telegram is also home to a deeper ecosystem powered by our Buddy bots. Through these bots, members can submit content, earn Stars, climb ranks, and unlock rewards. It’s not just engagement – it’s an adventure. (More on our bots in the next section.)

From tweets to lore quests, Discord chats to loot box claim rolls, our social presence isn’t a campaign. It’s a world. And the Buddies are your guides.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mega-buddies.gitbook.io/mega-buddies-docs/community/buddy-characters-and-community-engagement/multi-platform-engagement.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.