azerothcore / azerothcore/Keira3

[Feature Request] Quest editing is very poorly constructed

Open
#2,845 3 comments 2 reactions 0 assignees View on GitHub
enhancement feature request
Dominant language
TypeScript
Stars
450
Forks
183
Avg merge
23h 42m
Merged PRs (30d)
18

Description

Quets editing is really hard because Keira positions things in a bad order and includes unused fields whilst hiding important fields on different pages.

Quests do not use "AreaDescription" yet they are in the 4 "texts" area.

Currently it's hidden across 3 pages and in this bad order:

1) QuestCompletionLog (??? Last)
2) QuestDescription
3) AreaDescription (NOT USED)
4) LogDescription (After Completion?)
5) RewardText (Different Page)
6) Completion Text (Different Page)

Rewardtext is hidden in quest offer reward subfolder.

Completion text is hidden in quest request item subfolder (and does not show up on the right).

This is what it should be like for good/easy/useful quest editing/creation:

When writing custom quests you want to do them in order and all on the same page.

1) QuestDescription
2) LogDescription
3) CompletionText
4) QuestCompletionLog
5) RewardText

Please can you improve this as TrinityCreator recently broke and its last supported Azerothcore Database is 2022 so there's now no tool to make quests.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the quest editor entry point and inspect how QuestDescription, LogDescription, CompletionText, QuestCompletionLog, and RewardText are currently distributed across pages and the quest offer reward and request item subfolders. Done means these fields appear in the requested order on one page, with the unused AreaDescription removed or excluded and completion text visible in the editor.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.