Update 38 (Version 9.0)

[sirinsidiator]

The next chapter "Necrom" will be available on the PTS later today.

New API Version: 101038

Notable Changes

• New zone, trial, item sets, combat changes, etc.
• More Daily/Weekly Reset Timer Updates
• New "Arcanist" class
• Collectible Favorites
• Filleting multiple stacks of fish
• New PVP Keep Messaging
• Confirmation dialog for quest rewards that would be lost due to currency caps (i.e. Event Tickets)
• New error UI behavior (see comment below)
• New integer53 type to replace id64 where possible (see comment below)
• The code for various wheel menus (e.g. FISHING_MANAGER) has been merged into INTERACTIVE_WHEEL_MANAGER.
• Beta version of a new Launcher

PTS Dev Guild
We have created guilds on the EU and NA server for all addon developers, which get copied over during the PTS cycle for a new update, so we can test guild related things, ask for help with testing or just chat. If you need an invite, ask here or over on our Matrix channel. You are also free to join them on the live servers so you don't always have to be reinvited when the PTS is wiped.

Links

• API Patch Notes (changes in P38_2)
• PTS Patch Notes 9.0.0 (code changes from 8.3.7)
• PTS Patch Notes 9.0.1 (code changes from 9.0.0)
• PTS Patch Notes 9.0.2 (code changes from 9.0.1)
• PTS Patch Notes 9.0.3 (code changes from 9.0.2)
• PTS Patch Notes 9.0.4 (code changes from 9.0.3)
• Patch Notes 9.0.5 (code changes from 9.0.4) (code changes from 8.3.8)
• ESOUIDocumentation.txt
• ESOUI source code
• Feedback Megathread on the official forum
• Thread for Update 37 (Version 8.3)

I'll edit the OP with more useful information as you post it and add the links as they become available.

[ZOS_DanBatson]

Documentation. Patch notes to follow tomorrow.

[ZOS_DanBatson]

Note: we've changed the way UI errors work to make them less disruptive to regular players. There's now simple mode and advanced mode. Addon devs will want to turn on advanced mode.

I've also introduced the concept of an integer53. This is essentially a uint64 cast to a luanumber (double) which has up to 2^53 precision. Any time we were using an id64 but the number was likely to be within that precision, I've switched to a integer53. This will allow you to do regular math operations and see the true value and what not on it, and not need the annoying id64 APIs to work with it. Most commonly this pertains to timestamps. Many kinds of ids like furniture ids and character ids are still id64. The patch notes will call out which things have changed, but you can search the documentation for integer53 to get an idea.

[Sharlikran]

I can't see any Lua errors at all. Where do I turn on advanced mode?

Also popups are kinda broken. At least the popup for the chat menu doesn't open when you click the gear or circle. If it's a mod causing it then I don't know because I can't see any errors and nothing shows up in LibDebugLogger either.

[Sharlikran]

I guess it's in UserSettings.txt

[ZOS_DanBatson]

The setting to control it is in the AddOn settings menu. By default it's simple mode, but simple mode does not make no errors show up. If you're experiencing that, I suspect something else would be causing that experience. Only addon devs or particularly Lua-savvy users should conceivably get any real benefit from advanced errors, and thus the setting lives where addon settings live.

The big change with the new simple mode is that it will not show you more than one error at a time (so when you dismiss, you dismiss any and all errors that had occured) and you can suppress to make sure you don't see errors again, allowing you to get past otherwise innocuous erros locking you down from an update loop.

[Navarill]

Originally Posted by Sharlikran I guess it's in UserSettings.txt

If you use Addon Selector, it overwrites the checkbox for advanced lua errors at the top of Addon Settings.

[Baertram]

Originally Posted by Navarill If you use Addon Selector, it overwrites the checkbox for advanced lua errors at the top of Addon Settings.

Originally Posted by ZOS_DanBatson The setting to control it is in the AddOn settings menu.

Maybe I'm the only one seeing it that way but in my opinion those new chechboxes for advanced error messages should be placed IN THE SETTINGS PLEASE @ZosDanBatson and not at the addon manager...
These are general settings, so why not use the settings panel for it?

[Baertram]

FISHING_MANAGER global variable was removed (was often used for Interaction Manager access to the "interactions tuff below the reticle/crosshair) as the global for that one was missing in the past).
-> Accordig to ZOs you can use INTERACTIVE_WHEEL_MANAGER as a replacement!

SecurePostHook(FISHING_MANAGER or INTERACTIVE_WHEEL_MANAGER, "StartInteraction", OnStartInteraction)

[ZOS_DanBatson]

Patch notes

[Masteroshi430]

* IsZoneCollectibleLocked(*luaindex* _zoneIndex_)
This can be really useful to avoid spoilers on maps for exemple

[ExoY]

I discovered some weird behaviour with moving ui elements from addons. Which is different to how it is currently on live.
Maybe somebody else can check, if they are able to reproduce it.
Also I dont know if that is intended or maybe a bug.


What I usually do to move ui around is "activate" the cursor by pressing the "enter"-key.
This doesnt work properly anymore on pts. Once I click on a ui to drag and drop it the courser just disappears, as if I just clicked on Gui root.

I cann still move stuff around, but I need to activate the courser using the specific hotkey for it, which is "." by default (i believe).


Obviously I cannot try this without any addons activated. But to decrease the chance that some addons interfere I tested it on live and pts with only my addon "ExoYs ProcSet Timer" and its dependencies activated.

I noticed the same behaviour with other addons as well.

[Baertram]

You could try Azurah addon to move vanilla UI around, but it's also an addon for sure ;-)


Maybe unrelated but I wonder if this "reticle" cursor mode change is a general bug "for some players" on PTS?

Someone else told me 2 days ago he was not able (all addons disabled) to click on the chat channel selection box anymore and choose a zone/say/yell/tell cannel there without having the mouse change to the reticle mode automatically.
We did some test and the settings to change/keep mouse cursor uring typing did not change/affect this for him.

Unfortunately it did work fine for me. I could click on the box and after that choose a channel and my cursor was in the text editbox then,r eday to type.
For him it never came to the chat editbox, always switched to reticle mode after selecting a chat channel.

We did remove all addons and libs, created a new char, and did other tests. Nothing helped him.

[Navarill]

Originally Posted by Baertram Someone else told me 2 days ago he was not able (all addons disabled) to click on the chat channel selection box anymore and choose a zone/say/yell/tell cannel there without having the mouse change to the reticle mode automatically.

Update: I've always pressed ENTER to initiate use of the chat box. This is broken on PTS. If I use the period key instead, it works as expected. This behavior is not consistent with the live server, where both ENTER and PERIOD work as expected.

[Baertram]

So ENTER/RETURN key, then use the mouse to click on the chat channel selection and select one entry from the selection, after that your mouse cursor was hidden and the chat textbox got no focus, you could not directly write?

[Navarill]

Originally Posted by Baertram So ENTER/RETURN key, then use the mouse to click on the chat channel selection and select one entry from the selection, after that your mouse cursor was hidden and the chat textbox got no focus, you could not directly write?

Not quite. With ENTER/RETURN I could click on the chat channel selection to bring up the menu of choices, but at that point the focus went back to the main HUD and I could not select any of the choices. Same if I clicked on chat settings - immediately after clicking, the mouse lost focus.

[Calamath]

Originally Posted by ZOS_DanBatson Patch notes

* UI_SETTING_AUTOMATIC_QUEST_TRACKING

I didn't notice it in the patch notes, but this optional setting is something I have been craving for a very long time.
It's odd that this option was added out of the blue, but it saves me from having to run unmannered code on my Quest Tracker add-ons.
I appreciate it very much.

[Anceane]

Originally Posted by Baertram You could try Azurah addon to move vanilla UI around, but it's also an addon for sure ;-) Maybe unrelated but I wonder if this "reticle" cursor mode change is a general bug "for some players" on PTS? Someone else told me 2 days ago he was not able (all addons disabled) to click on the chat channel selection box anymore and choose a zone/say/yell/tell cannel there without having the mouse change to the reticle mode automatically. We did some test and the settings to change/keep mouse cursor uring typing did not change/affect this for him. Unfortunately it did work fine for me. I could click on the box and after that choose a channel and my cursor was in the text editbox then,r eday to type. For him it never came to the chat editbox, always switched to reticle mode after selecting a chat channel. We did remove all addons and libs, created a new char, and did other tests. Nothing helped him.

I am not an author so sorry if i write here, but it happened i had this error, and by disabling the LUI module chat, all went back to normal. (i tested also addons like No thank you and FCO stuff but only LUI did the correction)

[Baertram]

Originally Posted by ExoY I discovered some weird behaviour with moving ui elements from addons. Which is different to how it is currently on live. Maybe somebody else can check, if they are able to reproduce it. Also I dont know if that is intended or maybe a bug. What I usually do to move ui around is "activate" the cursor by pressing the "enter"-key. This doesnt work properly anymore on pts. Once I click on a ui to drag and drop it the courser just disappears, as if I just clicked on Gui root. I cann still move stuff around, but I need to activate the courser using the specific hotkey for it, which is "." by default (i believe). Obviously I cannot try this without any addons activated. But to decrease the chance that some addons interfere I tested it on live and pts with only my addon "ExoYs ProcSet Timer" and its dependencies activated. I noticed the same behaviour with other addons as well.

More insights from Calamath,thanks for that!

When I turned on the "HUD Cursor On Entry" setting and performed the Start Chat action in the HUD scene, the mouse cursor appeared and I was able to enter string text in the chat window. This looks like a transition to the hudui scene. But when I type /script d(SCENE_MANAGER:GetCurrentScene():GetName()), sometimes it returns 'hud' and sometimes it returns 'hudui'. Digging a little deeper, I noticed that this behavior has changed after PTS patch to rely on the mouse cursor coodinates saved just BEFORE performing the StartChat action in the hud scene. If the mouse cursor was inside the chat window for example, it will be 'hudui' no matter where you move the cursor after the action. If the cursor was on a place such as a landscape with no UI elements, it will be 'hud'. Moving the mouse cursor somewhere else after performing the chat start action, such as mouse over a toplevel window, no longer changed the result anymore. Maybe it's a latency issue, but I couldn't resize the chat window in the conditions that I would get 'hud' result. On the other hand, under the condition of returning "hudui", I am free to resize the chat window in the PTS as well as in the live server. This difference in behavior may be as intended by design, but it is very difficult for me to understand intuitively. The conclusion may be that we should not interact with the UI element by mouse cursor AFTER the StartChat action.

Edit:

ZOs was able to reproduce the issue and is working on a fix.

[ZOS_DanBatson]

Originally Posted by Baertram Edit: ZOs was able to reproduce the issue and is working on a fix.

We have a fix. Not clear yet if it'll be in an incremental or Update 39.