SC2Mapster

Hey before talk about a bug I wanted to say I really enjoy your game.
You obviously put a lot of time and effort into it and congrats its amazing.

However,
There is a huge bug with Hull research that does not allow you to save your Hulls.
It completely destroys the game and if It keeps happening I'm sure a lot of loyal ppl will get frustrated and stop playing the game.

What steps will reproduce the problem?
1. Research a Hull
2. Try to Save it and it only goes to a screen with delete last researched item button ie. Delete shields
3. Error message continues and you can't save any hulls

What is the expected output?
The regular Save Research Screen

What do you see instead?
a Save Research Screen which has a big red delete research button instead. (Screenshot Attached)

Do you have an error log of what happened?
The Exact Error Message is in red:

Trigger Error in
'gt_DialogsRsave_Func': Trying to
access an element past the end of an
array

Please provide any additional information below.
Screenshot is Attached

Please fix this as soon as you can.
Thx.
P.S.
I registered this account just so I could get this message to you in hopes that this bug will be fixed so I can play more lol...

Seems to be a simple issue of either an array that was improperly sized or a counter integer that skips too high for whatever reason.

Should be an easy fix, so it's probably worth it to fix it and publish it as 1.20 or something instead of waiting for the full UI redesign to be done, so that at least people can keep playing the current version until the new one comes out.

Nice bug report, It have been already reported to me many times btw and I still couldnt find out why it is happening:D I will look into again today.

If you need any help with tracking down the cause and/or finding a solution for this bug (or any other), I'd be more than willing to offer my assistance.

hehe, you dont want to see my research triggers, its one big mess:D I will work on 2.0 instead of tracking this bug down.

Depends on what you call "one big mess". You should've seen my early prototype code for multi-command aliases for the Cortex Engine. It was (sort of) functional, but debugging anything in it was like attempting to debug and modify a reverse-engineered Unreal3 game in assembler - not quite impossible, but not far from it either.

So yeah, if you want me to I can give it a shot, otherwise I've got plenty to keep me busy until 2.0 comes out ^^

Its really a big mess.)