|
Help Making Scenarios by MaxisWaylon
Here at Maxis we get excited when we see new scenarios posted on the SimCity Exchange. No, not because we need something new to keep us busy during the day, but we like to see users taking advantage of the Scenario Creator. In terms of numbers, many more buildings and cities have been uploaded then scenarios. I don't think this means people don't like to play scenarios, because they seem to be a quite popular SimCity Day download. I feel the lack of uploads is a result of the time it takes to learn the Scenario Creator. The Scenario Creator is far from C++, but it's much more then a point-and-click process. So here's a standing ovation to the users who have taken the time tackle the Scenario Creator.
After playing all of the user-made scenarios, I've noticed most of them share a few minor problems on the scripting end of things. I'm sure many of you have played a scenario when a pop-up message appears every day making the scenario impossible to play. Although it creates a major problem in terms of game play, it's a minor problem in the script that one additional line of code may have fixed. I'm going to address some of these problems with possible solutions in an attempt to help those who are trying to make scenarios. Also, for those who may start writing scenarios, this will help by pointing out a few things you should do that are easily overlooked.
Problem 1 - The Evil, Reoccurring Pop-Up
The key to fixing this problem is using a flag. A flag is just name given to a variable that has the sole job of, for lack of better words, turning things OFF an ON. In the requirements that trigger a pop-up, be sure to include a flag. For example, you have a pop-up message that happens after two fire stations are built. Make a variable called "FS Pop-Up" (it can be named anything you like) and add "If FS Pop-Up equals 0" to go along with "If Fire Stations equal 2" in your script. After the line of code that displays the pop-up message, add "Set FS Pop-Up 1". Setting the flag to 1 will prevent the pop-up from reoccurring (assuming you still have two fire stations).
Problem 2 - Incorrect Coordinates
In several scenarios, the player is required to build something in a certain location. However, once the specified building is placed in what seems to be the correct location, nothing happens. In all likelihood there is a problem with either the coordinates specified in the script or the value of the radius. To obtain the coordinates of a certain tile, press "shift-c" while playing the game. As you move the cursor over each tile, you'll see its' coordinates. Make sure to double-check the coordinates because if you tell someone to build something in a specific region and they do with no results, the scenario may become un-winnable. Also make sure that the radius is set accurately. If you're telling someone to build in a large region, a radius of 1 isn't going to get the job done
Problem 3 - Counting Wrong Structures/Value
It's safe to say that at one point every scenario is going to count a certain structure (like Police Stations or Subway) or a value (like Crime or Pollution). A problem arises when you tell the player your counting a certain structure or value, but the scenario is actually counting something else. For example, you receive a pop-up message that tells you to build a school in your city to satisfy a goal. After building the school, the goal isn't satisfied. In an act of frustration you start building every thing you can, but once you place the University, the goal is satisfied. My best advice here is to be specific in the directions you give and make sure you're actually counting what you say you are.
Problem 4 - Not Calling Scripts
I've played a few scenarios that either ends as soon as you start and others that don't seem to do anything after you start. Without being able to look at the script itself it's hard to tell what exactly is going on, but it looks like the sub-scripts are not being called from the main script. For example, if you write a script that checks the status of your goals, you need to call that script from the main script using the "repeat regular" command. If you don't call on your sub-scripts, they don't exist as far as the Scenario Creator is concerned.
Hopefully addressing these problems will help everyone who's trying to make scenarios. One of the best ways to determine if your scenario has problems is to play it before you upload it. Playing your scenario will let you see if there are any major problems with it. No matter how confident you are in your scripting abilities, I can guarantee you that you will change something. Another good idea is to have someone else play it. If you play a scenario you made, you have an unfair advantage of knowing what is supposed to be done. Having someone that hasn't played it yet will be the best way to tell if you need to make any major changes or minor adjustments.
|