(Important bug) Dim variables in "with" statements [Fixed Patch 31.1]

[Lx Xzit]

When you use a dim variable and then use a "with" block, accessing to this object's variables will result in "Access Violation" error.

For example:

Code: Select all

dim i as integer
with npc(1)
    .xsp = 1 'stops the script
end with

This bug breaks basically all my scripts.
By the way, it reminds me to the "struct" bug I reported that hasn't been fixed yet.

[Void]

When you use a dim variable and then use a "with" block, accessing to this object's variables will result in "Access Violation" error.

For example:

Code: Select all

dim i as integer
with npc(1)
    .xsp = 1 'stops the script
end with

This bug breaks basically all my scripts.
By the way, it reminds me to the "struct" bug I reported that hasn't been fixed yet.

I think this should be stickied and (hopefully) fixed ASAP. Most experienced scripters are actually using the dim variable ever since it's been discovered, so to see basically half of the scripts break in patch 31 is really upsetting to a lot of people, including myself. As a result I've been discouraging people from using patch 31.

[Omega02]

When you use a dim variable and then use a "with" block, accessing to this object's variables will result in "Access Violation" error.

For example:

Code: Select all

dim i as integer
with npc(1)
    .xsp = 1 'stops the script
end with

This bug breaks basically all my scripts.
By the way, it reminds me to the "struct" bug I reported that hasn't been fixed yet.

This has been fixed in patch 31.1, which just came out a few minutes ago.