Creating quests

The one rule

The post must come from one of your project X accounts (registered on the Settings page). Fealty reads engagement with the author's own authorization, which is also the only way X exposes a post's likes. Paste any post URL and the author is checked automatically; if it's your own connected X but not registered yet, a one-click button adds it.

From the dashboard

On Quests, paste the post URL, tick the actions you want to reward and set what each one pays (like, retweet, comment carry separate values), add an end time, and create. The header shows exactly which accounts you can post quests from.

Unticked actions are not tracked at all, so they cost no credit. Note how likes work: X reveals like data only to the post's author, so like points are earned by pressing the quest's Like button (on the Discord post or the hub), which records the click and then opens X — a like made straight on X can't be seen and won't pay. The quest post tells members this. Retweets and comments verify from real X data when the quest ends. Open the quest afterwards and press Post to Discord to announce it in your quests channel with the engage buttons.

From Discord

/tweet does the same in one command (requires Manage Server):

/tweet url:<post> hours:24 like:true retweet:true points_like:10 points_retweet:5

Duration comes from hours and minutes; at least one is required. Each points_* option defaults to 10. The quest posts into the channel with its reward breakdown and engage buttons.

Limits and lifecycle

Active quests are capped by your plan (see Plans). A quest is active until its end time, then ended after verification; paused means verification couldn't complete correctly yet (out of credit, or X reads failing) and it will finalize on its own once the cause clears. The exact reason is shown under the quest.

A paused quest never ends on its own: nobody's rewards are forfeited by an outage. Reads retry automatically (with an automatic fallback across X data backends), your team is notified when a quest first pauses and again if it is still stuck after 3 days, and the quest page offers an explicit End without awards button when you'd rather close it than wait. Until you press it, the quest keeps retrying.