Issue with inventory UI

Scripting C# & .NET
2

The main issue with the code above is going to be maintainability. You are conflating the actual tracking and processing of the data (counts, inventory, numbers, amounts, etc., aka “the model”) with the presentation of the contents (the text, aka “the view” of your data).

Break it all apart:

  • store and track the addition/removal of items, and add copious debugging into there to prove that all cases of adding/removing work perfectly (This should be ULTRA simple and tiny, just a little bookkeeper class)

  • create a UI (view) into this data and present it however you like.

That way if in the future you radically change either one, they both don’t just become a complete mess.

Plus when you encounter a bug like the above, you have a much tinier area of code to consider: either prove that the error is in the bookkeeping section, or if that is spitting out correct values, look in the view.

Beyond that, to help gain more insight into your problem, I recommend stripping things down to the barest simplest set of items that show off the problem, then liberally sprinkling Debug.Log() statements through your code to display information in realtime.

Doing this should help you answer these types of questions:

  • is this code even running? which parts are running? how often does it run? what order does it run in?
  • what are the values of the variables involved? Are they initialized? Are the values reasonable?
  • are you meeting ALL the requirements to receive callbacks such as triggers / colliders (review the documentation)

Knowing this information will help you reason about the behavior you are seeing.

You can also put in Debug.Break() to pause the Editor when certain interesting pieces of code run, and then study the scene

You could also just display various important quantities in UI Text elements to watch them change as you play the game.

If you are running a mobile device you can also view the console output. Google for how on your particular mobile target.

Here’s an example of putting in a laser-focused Debug.Log() and how that can save you a TON of time wallowing around speculating what might be going wrong: