The Cause of The ESC Bug
 

It looks like the interface runtime is expecting us to use table.insert and not "key in" array entries directly.

Here is the offending function in my code: https://github.com/Exterminatus/eso-...e516885616L212

Here is how we should be doing it: https://github.com/Exterminatus/eso-...72850fa7ff7R12

If you pass a "badly created" array to ESO it seems to cause this issue (in my case, I was sending it to the settings menu via LAM).

Just one to watch out for. There are other plugins besides mine causing this, but sadly my guildies haven't been bothered to nail down which of the plugins are causing their issues.

lol even if that 's the cause it 's utterly retarded because the table functions of Lua are actually outdated since long ago and most of them don't even support metatables properly (like table.insert) - so it 's a bug that can't and shouldn't be adjusted to rather then fixed (if its really the cause).

I however can't really believe that claim as table.insert by logic does nothing more then tablename[#tablename+1] = value in the background.

table.insert also does a setn for you, so I think that may be it.

Hey, it fixed my plugin, so...

Better would be a small reproduceable test case.

I feel we're running into a "correlation does not imply causation" issue here.

I'll try set up that test case tonight - I was running trials last night :banana:

Edit: also a bit curious as to which Lua version ESO uses and how this is a bit strange: http://www.reddit.com/r/elderscrolls...sc_bug/chs2ar5

People here told me Lua 5.1.


... and yeah, interesting link.

I noticed the ESC-Bug (or a variant of it) when I used :SetKeyboardEnabled(false/true) on an Editfield.

Even when correctly renabling it it would block all Global Keyboard Input for the whole UI from time to time -
the only thing that worked was not using it at all (as in never using SetKeyboardEnabled).

Might be a different one, but just if anyone comes across that weird behaviour as well ...