Duplicate Game crashed while battling in the third gym

[B3zerko42]

Pokémon 3D has crashed!


---------------------------


aSystem specifications:

Pokémon 3D version: 0.36.2

Operating system: Microsoft Windows 7 Home Premium  [6.1.7601.65536]

System time: 9/16/2013 2:40:16 PM

System language: ENU

Decimal seperator: .

Content Packs: {}

Active GameMode: Pokemon 3D

Operating online: FALSE

Game environment: BattleScreenV2

---------------------------



Here is further information:


Message: Object reference not set to an instance of an object.

InnerException: NOTHING

BaseException: Object reference not set to an instance of an object.

HelpLink: No helplink available.

Data: System.Collections.ListDictionaryInternal

Source: 2.5DHero

TargetSite: Name: InflictInfatuate [

  Attributes: PrivateScope, Public

  CallingConvention: Standard, HasThis

  ContainsGenericParameters: False

  DeclaringType: _2._5DHero.BV2.BattleV2

  IsAbstract: False

  IsAssembly: False

  IsConstructor: False

  IsFamily: False

  IsFamilyAndAssembly: False

  IsFamilyOrAssembly: False

  IsFinal: False

  IsGenericMethod: False

  IsGenericMethodDefinition: False

  IsHideBySig: False

  IsPrivate: False

  IsPublic: True

  IsSecurityCritical: True

  IsSecuritySafeCritical: False

  IsSecurityTransparent: False

  IsSpecialName: False

  IsStatic: False

  IsVirtual: False

  MemberType: Method

  MetadataToken: 100663559

  MethodHandle: System.RuntimeMethodHandle

  Module: 2.5DHero.exe

  ReflectedType: _2._5DHero.BV2.BattleV2

  ]

StackTrace:  at _2._5DHero.BV2.BattleV2.InflictInfatuate(Boolean own, Boolean from, BattleScreenV2 BattleScreen, String message, String cause)

  at _2._5DHero.BV2.BattleV2.DoAttackRound(BattleScreenV2 BattleScreen, Boolean own, AttackV2 moveUsed)

  at _2._5DHero.BV2.BattleV2.InitializeRound(BattleScreenV2 BattleScreen, RoundConst OwnStep)

  at _2._5DHero.BV2.BattleMenuV2.PressButtonMoves(BattleScreenV2 BattleScreen)

  at _2._5DHero.BV2.BattleMenuV2.UpdateMoves(BattleScreenV2 BattleScreen)

  at _2._5DHero.BV2.BattleMenuV2.Update(BattleScreenV2 BattleScreenV2)

  at _2._5DHero.BV2.BattleScreenV2.Update()

  at _2._5DHero.Basic.Update(GameTime gameTime)

  at _2._5DHero.DGame.Update(GameTime gameTime)

  at Microsoft.Xna.Framework.Game.Tick()

  at Microsoft.Xna.Framework.Game.HostIdle(Object sender, EventArgs e)

  at Microsoft.Xna.Framework.GameHost.OnIdle()

  at Microsoft.Xna.Framework.WindowsGameHost.RunOneFrame()

  at Microsoft.Xna.Framework.WindowsGameHost.ApplicationIdle(Object sender, EventArgs e)

  at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)

  at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)

  at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

  at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

  at System.Windows.Forms.Application.Run(Form mainForm)

  at Microsoft.Xna.Framework.WindowsGameHost.Run()

  at Microsoft.Xna.Framework.Game.RunGame(Boolean useBlockingRun)

  at Microsoft.Xna.Framework.Game.Run()

  at _2._5DHero.Program.Main(String[] args)

 

[Tornado9797]

First of all, you should always label Crashes with their distinct labels, helps solve the bug faster.
Second, this is a bug that has been reported many times: a glitch with using infatuate users.
This bug has been fixed in the next version.

 

[Malcaroni]

Third, please use code tags.

 

[B3zerko42]

First of all, you should always label Crashes with their distinct labels, helps solve the bug faster.
Second, this is a bug that has been reported many times: a glitch with using infatuate users.
This bug has been fixed in the next version.

where can i see the labels you are talking about?

 

[B3zerko42]

Third, please use code tags.

what are code tags?

 

[Tornado9797]

First of all, you should always label Crashes with their distinct labels, helps solve the bug faster.
Second, this is a bug that has been reported many times: a glitch with using infatuate users.
This bug has been fixed in the next version.

where can i see the labels you are talking about?

When editing the title of a Bug thread, Crash is one of the options (can't be done now because this thread is now in the Bug Archives)

Third, please use code tags.

what are code tags?

It's a text module:

Example.

 

[Malcaroni]

Third, please use code tags.

what are code tags?

[0code]
your stuff
[0/code]

But without 0

If you typed that, without 0, it would be:

your stuff