Changing Objectives

I’m trying to create a game in which the player is a restaurant worker trying to deliver food. So far I have a script that displays what food an NPC will order, but as it goes I’m stuck trying to develop a script that changes once the player drops the right items. In essence I want to create a script that players drop 3 of the right objects in which will then change the image and recognize as a win state. My coding is a bit garbage so any suggestions would be greatly appreciated. I’ve had a look for a drop off like system but for the life of me I can’t find a single one.

Here’s the script I have so Far

using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using UnityEngine.UI;

public class UIAppear : MonoBehaviour
{
[SerializeField] private Image Order;

void OnTriggerEnter(Collider other)
{
if (other.CompareTag(“Player”))
{
Order.enabled = true;
Debug.Log(“Food Please”);
}
}
void OnTriggerExit(Collider other)
{
if (other.CompareTag(“Player”))
{
Order.enabled = false;
Debug.Log(“Thank You!”);
}

}
}

It won’t be a script. Scripts are just a few bits of code. It will be an entire context: scenes, prefabs, scripts to control it all, authored level content, etc.

Start with basic tutorials to get a car moving around a level.

After that, understand how to detect the player being in a trigger area.

Once you have that, set up a trigger for the pickup zone and one for the drop off zone.

Detect player being in whichever one, and either take aboard, or drop off, the payload.

That’s it. Everything else is gravy and authoring actual content. But don’t even think about it until you have all the steps above working rock solid on a hard-coded demo level.

When you work on tutorials, don’t try to skip any steps. There’s only two steps:

How to do tutorials properly, two (2) simple steps to success:

Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. That’s how software engineering works. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.

Fortunately this is the easiest part to get right: Be a robot. Don’t make any mistakes.
BE PERFECT IN EVERYTHING YOU DO HERE!!

If you get any errors, learn how to read the error code and fix your error. Google is your friend here. Do NOT continue until you fix your error. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.

Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.

Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. If you want to learn, you MUST do Step 2.

Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If there’s an error, you will NEVER be the first guy to find it.

Beyond that, Step 3, 4, 5 and 6 become easy because you already understand!