TasQuestBox

[P3in]

Looks dope, thanks for another great resource!

Also, for that search toolbar, it is only available to Lua? I cant seem to have it on vjass version

 

[Tasyen]

ty, yes, the vjass version does not have a search bar and is overall more simple/hardcoded.

 

[Antares]

The background texture is missing for me in the Lua map.

 

[Tasyen]

The Lua demo also loads the blizzard fdf templates and uses 2 frame blueprints from them. Either load that addional toc becore making the questbox or change the frame blueprints.
This 2 blueprints choose how the box/background looks and the textarea.
in the systems "config".

,TextAreaFdf = "EscMenuTextAreaTemplate" -- frame blueprint used for the textarea it works even with "" or invalid
,BoxFdf = "EscMenuControlBackdropTemplate" -- frame blueprint for the window box, "" or nil make no box

one could use ,BoxFdf = "EscMenuBackdrop" that works just like that.


I am thinking about adding a Lua version into the current jass file and rename into Light.
Edit: It was done. The Lua Light version can still use quests but has no search and no code reqs.

Edit: Updated Lua version to V1.2) There is now only 1 toc that loads ButtonList and the blizzard templates, TasQuestBox2.toc
Edit: Updated to 1.3) As it was requested can now remove entries with TasQuestBox.Remove(obj) / call TasQuestBox_Remove(integer index)

 

[Aldeia]

Is there a non-light version for Jass?

 

[Tasyen]

i didnt make one.

 

[SpasMaster]

Hello, Tasyen!

Is it possible and is it something you'd consider adding, to have a boolean parameter which has this system function independently from the default wc3 Quest Log? Where there would be a separate button that offers the same functionality, but without overriding the default Quest Log? This would allow users to have (for example) a Quest Log and a Journal of sorts. Or whatever one can come up with.

I'd assume if the system functions independently, then you wouldn't be able to add entries via the "Quest" actions, but that should be fine assuming you can still create an entry with TasQuestBox_Add().

 

[Tasyen]

Ty, for your interest.
it can work without touching the default quest system.
There already is a setup to replace the questbutton with a custom button or not. Check out the top of the system. On default it replaces it.
public boolean ReplaceQuestButton = false
this.ReplaceQuestButton = false
in this case one also should check out function this.PosOpen(frame) or public function PosOpen to choose the position of the open button

In the Lua version one can disable the quest copy feature. The vjass version does not copy any quest content, the demo just uses the same wts strings.
this.HookQuest = false

 

[SpasMaster]

I don't know how I missed this.
Probably because I didn't open it with syntax highlighter.

Anyways, disregard my previous comment then.
Great work!

 

[Wyrelade]

This is looking crisp! Nice job!

 

[Mellstorm]

Tell me how to make it possible to launch it by pressing F9 on ESC or by using the -board command instead of the standard one.
I'm also interested in how to increase the window size. I noticed in the standard quest window from Blizzard, there's a small gap in their board, and it actually limits the text greatly, which is inconvenient for reading. There's also no output via command in the chat, which is sad.

The version that I will use is JASS and GUI, since I have not yet reached the level to upgrade to LUA.

It's just awful, she practically did nothing, I pressed F9, she didn't respond, and it was impossible to turn her on using the chat command. She practically didn't do any of the tasks I assigned her.

What's the point of At 0s if the tasks don't work in it, and they're actually saved in DemoJass? Moreover, it won't be possible to control which player receives them, for example, by language, so the message will only appear in one language. Therefore, it was necessary for tasks to be displayed using the At 0s graphical trigger. This was generally incorrect, but fortunately, I managed to find a way to change the task title name in the game interface. However, I still can't launch it via chat or hotkey. If that were the case, I would agree with you, but for now, it's very difficult.

Not only did Blizzard screw up the ability to call box with the if (GetLocalPlayer() == GetTriggerPlayer()) then command
call ForceUICancel() //
call QuestMessageBJ(GetPlayersAll(), bj_QUESTMESSAGE_UPDATED, "!")
endif

But your system also refuses to work correctly. Of course, if we were to use this through DemoJass, it would be impossible to split it into languages. This would effectively negate all your work.

Unfortunately, I was forced to remove TasQuestBox until better times, I hope they will bring it to mind.

 

[Tasyen]

The 0s trigger is an example i used it to insert the strings. They are fixed/hardcoded text therefore they will be externalized into war3map.wts by world editor. in jass demo i use the string numbers. The vjass version was made from the Lua version in which one can feed data to TasQuestBox by quest api.

with the oskey event api, one could create a trigger and make OSKEY_F9, F9 open it then. I'll add it

 

[Mellstorm]

The 0s trigger is an example i used it to insert the strings. They are fixed/hardcoded text therefore they will be externalized into war3map.wts by world editor. in jass demo i use the string numbers. The vjass version was made from the Lua version in which one can feed data to TasQuestBox by quest api.

with the oskey event api, one could create a trigger and make OSKEY_F9, F9 open it then. I'll add it

I noticed that they fixed the bug with the standard box.
Please send me the full version, because using a mistake made by Blizzard is comparable to suicide.

 

[Tasyen]

Updated to V1.4)
(vjass) Hotkey F9 added to open/close the custom ui

Lua-Light fixed a error with the ESC event for players higher than red.

both Lua versions, if a page uses a quest and the quest is not discovered it will not display the big text in the textarea.

I noticed that they fixed the bug with the standard box.
Please send me the full version, because using a mistake made by Blizzard is comparable to suicide.

Expand Quest-Description's space by taking Quest-Defeat-Condition reserved space.

function QuestCheck takes nothing returns nothing
    call BlzFrameClick(BlzGetFrameByName("UpperButtonBarQuestsButton", 0))
    call BlzFrameClick(BlzGetFrameByName("QuestAcceptButton", 0))
    call BlzFrameSetSize(BlzGetFrameByName("QuestItemListContainer", 0), 0.01, 0.01)
    call BlzFrameSetSize(BlzGetFrameByName("QuestItemListScrollBar", 0), 0.001, 0.001)
endfunction

you first create a quest then call the function afterwards.

 

[Mellstorm]

It got better, it could be opened by F9, but I still couldn't call it with a command, and also filling out the quest in JASS doesn't suit me, the text is filled in on the GUI, because the text in my map works in several languages.