Reminder: please do not respond to bots. If you do, we cannot nuke them without messing up the database. Report them to staff and we'll take care of it.
Hey guys,
While I was working on my level for the competition, a weird exception came up right after I selected the ground tile from the brown Volcano tileset.
Here are the Details:
System.ArgumentOutOfRangeException: Value of '-4' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at NSMBe4.ObjectEditor.UpdateInfo(Boolean keep)
at NSMBe4.ObjectEditor.SetObject(NSMBObject no)
at NSMBe4.ObjectsEditionMode.UpdatePanel()
at NSMBe4.ObjectsEditionMode.SelectObject(Object o)
at NSMBe4.LevelEditorControl.SelectObject(Object no)
at NSMBe4.ObjectAction.AfterAction()
at NSMBe4.Action.DoRedo(Boolean multiple)
at NSMBe4.UndoManager.Do(Action act)
at NSMBe4.ObjectsEditionMode.MouseDrag(Int32 x, Int32 y)
at NSMBe4.LevelEditorControl.DrawingArea_MouseMove(Object sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseMove(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseMove(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
I'm not sure how we could reproduce this... I guess we have to turn on our debugger.
EDIT: I got a similar error, only with -11 when I created a sprite, and selected Chain Chomp / Log without moving the sprite at all.
System.ArgumentOutOfRangeException: Value of '-11' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at NSMBe4.SpriteEditor.UpdateInfo()
at NSMBe4.SpriteEditor.SetSprite(NSMBSprite ns)
at NSMBe4.ObjectsEditionMode.UpdatePanel()
at NSMBe4.ObjectsEditionMode.SelectObject(Object o)
at NSMBe4.LevelEditorControl.SelectObject(Object no)
at NSMBe4.SpriteAction.AfterAction()
at NSMBe4.Action.DoRedo(Boolean multiple)
at NSMBe4.UndoManager.Do(Action act)
at NSMBe4.ObjectsEditionMode.MouseDrag(Int32 x, Int32 y)
at NSMBe4.LevelEditorControl.DrawingArea_MouseMove(Object sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseMove(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseMove(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
EDIT: It happened again when I added the left facing ice wall from the Frosty TS, only with -16
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '-16' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at NSMBe4.ObjectEditor.UpdateInfo(Boolean keep)
at NSMBe4.ObjectEditor.SetObject(NSMBObject no)
at NSMBe4.ObjectsEditionMode.UpdatePanel()
at NSMBe4.ObjectsEditionMode.SelectObject(Object o)
at NSMBe4.LevelEditorControl.SelectObject(Object no)
at NSMBe4.ObjectAction.AfterAction()
at NSMBe4.Action.DoRedo(Boolean multiple)
at NSMBe4.UndoManager.Do(Action act)
at NSMBe4.ObjectsEditionMode.MouseDrag(Int32 x, Int32 y)
at NSMBe4.LevelEditorControl.DrawingArea_MouseMove(Object sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseMove(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseMove(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Well, in that case, this problem may never be fixed, because some bugs are very hard to reproduce, so I can't give you the details on how to reproduce this bug.
The only chance we have is to turn on the debugger.