• Download the SDK
  
  • Download the Server and Mapper and the full Client.
  • Keep these 2 zip files for later use, because if you mess things up very badly while experimenting (I did), u can just start over from here.
  • Copy the Client, Mapper, Server, Tools folders from the zip files to your development folder.
• Setting up the Mapper: (don't use yet)
  
  • If you start the Mapper for the first time, it will use the default video resolution, which is set in the client. Unfortunately, this will trim down the Mappers interface, so the first thing you should do, is launch the FOConfig.exe in the Client folder and set the resolution to at least 1024*768.
  • I also advise you to disable Full Screen.
  • Save and Exit.
• Try out if it works
  
  • Start the Server and wait for the scripts/everything to load, when it's done, you will see something like this: ***   Starting game loop   ***
  • Start the Client, create new char, log in. If no errors, then you are done with the setup.
• If you got problems with this part, you might try to set up your environment again, if it fails, search Questions and Answers at fodev.net.

• Launch the Dialog Editor (Tools\DialogEditor)
• Create a new dialog by pressing the Add Tree. Name your dialog engl. (This isn't actually it's name, but it's language type, it should be "engl" always, unless you want the dialog in a different language, but don't ask me about it)
• You will get a node named Predialogue Installations. This node is responsible for the initial reaction of the NPC to the player.
• For now let's make a new dialog. On the botton, select Dialog tabpage. For text enter the text the NPC will say, for example: "The robot scans you briefly then greets you. Hi. I'm TuRo MKI.". Edit the dialog number to a unique number, this time 200, and Add Dialog.
• This dialog will need answers as well, from which the player can choose from. Select the newly added dialog, on the botton select answer tabpage, and add two answers:
  
  • First answer with text: "Hi yourself Robot.", set the radio button to Other->Close dialog. This will make your robot interactive, but NPC's only have one option, to leave the conversation at first answer.
  • Second answer with text: "Hi. I'm lost.", set the radio button to On dialog and leave the number at default value or set it to 200. This answer might generate an infinite loop, bc it will always get the player back to where the Robot says Hi. In order to advance the dialog we need more dialoges, but for presentation purposes this should do.
• Now set the predialogue installations. Add an aswer to it: "I dont know you" and link it so, that the answer takes the player to the first dialog (200). This will make the Robot react to the players by always saying Hi.
• To give a meaning to the "I dont know you" answer, we can introduce a demand constraint. Go to Demands,select Var: "name_mem_npc_player", set the equation sign to "==" and enter the value "0".
• Add a Result to this answer as well: Var "name_mem_npc_player", set the equation sign to "=" and enter "1" for value. Also select NPC from the radio box and add the Result.
• This way we made our Robot to interract with each NPC only once.
• Other contrains can be made as well, like required strenght, or intellect, or simply make the robot talk at a different level of language if the player has low intellect. The example below shows this.
• Save the dialog with a name you remember, for example: tut_dialog1.fodlg
• For next step, we need to link the dialog with the Robot.
  
  • First, you need to edit the file named dialogs.lst in Server\Dialogs to include the new dialog. Just copy a line and give a unique ID for the dialog file, I used 2100. Try to keep the order and structure of this dialogs list file.
  • Use the Mapper to add this dialog to the Robot. Simply select the robot, and at dialogs enter this number.
• Save the map, delete world save files, launch server, try.

• First things first, if you haven't, create a new bat file to lauch your server. It should delete all fosmapb from the maps, and launch server after. This way you will never run in circles trying to figure out, why things don't works, when the only problem was, that you forgot to clean, rebuild the maps and reload the world.
  (In case you don't know how to make batch files, just make a new text file with the name CleanWorld.bat in the Server folder and add the following 3 lines to it:
  
  • "del maps\q*.fomapb"
  • "del save\world*.fo"
  • "FOnlineServer.exe"
  This will delete ur current world save as well, so every progress your char had, except it's creation and location is lost.)
• Launch Mapper.
• Create a cave (or copy one, but remove useless "tech" objects so u don't accidentally get random monsters generated) and place some rats in it.
• Use the property editor (press F9 to toggle on/off) to set the mobs (I will refer to monsters/critters as mobs from now on) script to the following:
  
  • set ScriptName to "mob" (This will tell which script file to check for the function below. Server\Scripts\mob.fos )
  • set FuncName to "critter_init" (This is the function (script) to be called when creating this mob)
  
  
• Save the map and try it. Use your new batch file.

• Select the mob (click on it, have details window turned on - F9)
• On the bottom panel select Norm, double click it and filter for ammo.(You target on the map still should be the rat.)
• Now Alt+Click on some shotgun shells.
• On the bottom panel select Inve, you should see the shotgun shells added. You can Alt+Click to remove them.
• To set the amount of the shells, just click on the shells and edit the Count to a differnt value than 0.
• Launch server and client, to try it out.
• Kill the mob for your reward: 1 shotgun shell

• Launch Dialog Editor and create a new dialog.
• Make the dialog tree as the picture below shows.
• After saving it, make sure you edit the dialog list (Server\dialogs\dialog.lst)file and add to it the dialog you made, I used 2102 for dialog ID.
• Add the dialog ID to the Molerat Dialog property.
• Add some small rats around the Molerat and set their ScriptName to "mob" and FuncName to "_DontMove".
• Add some weapons to the entrance of the cave, so your character can survive the rat attack.
• Save map and try. Gl.

• Create a new scriptfile:
  
  • Create a new textfile named "quest_tut1.fos" in "Server\scripts\"
  • Copy paste the content from the code part below.
• Bind the script file to the Scenery in Mapper:
  
  • Launch Mapper and the load the map.
  • If you haven't add a Scenery object to the map. (I used some defected robot.)
  • Set the ScriptName value of the Scenery object to your script files name. (quest_tut1.fos)
  • Set the FuncName value of the Scenery object to the function to be called when player interaction. (s_RefillRobot)
  • Save the map and exit.
• Run the server to compile your script:
  
  • To test if your script compiles error free, you can use: Server\scripts\compile.bat quest_tut1.fos
  • Delete previous script file binaries of your modified script file if they exist. (quest_tut1.fosb, quest_tut1.fosp)
    
  • Run the server.
• Understand the script:
  
  • Study the script file, pretty straightforward, comments are useless but I left them there anyways.
  • If the player tries to use the Repair Skill on the robot, it will say that he can't do that without Small Energy Cells.
  • If the players tries to use the Science Skill on the robot, the system will say that the robot is out of energy.
  • Finally, if the player tries to use Small Energy Cells on the robot, the system will notify about the success and set the quest variable to the desired value. This is how the quest is progressed in this case.
  • Also one Small Energy Cell is removed from the backpack of the player.
  • If the player tries to use the Repair or Science skills on the robot, the notification will tell, that it is already done. This is ensured by the quest variable chesk at the start.

//  Includes some definitions
#include "_macros.fos"

//  Function signature for player interactions with Scenery objects
bool s_RefillRobot(Critter& player, Scenery& robot, int skill, Item@ item)
{
	//	Retrieve the variable used by the quest to mark it's progress, plus error handling
	GameVar@ questVar = GetLocalVar(LVAR_q_turo_prog, player.Id);
	if(valid(questVar))
	{
		//	is quest still in progress and before repairing the robot
		if (questVar < 30)
		{
			//  Check if repair skill is used on the robot	
			if(skill == SK_REPAIR)
			{
				player.Say(SAY_NETMSG, "You don't think it can be done without some small energy cells.");
				return true;
			}
			//	Check if science skill is used on the robot
			if(skill == SK_SCIENCE)
			{
				player.Say(SAY_NETMSG, "The robot is running very low on energy.");
				return true;
			}
			//	Check if the player used a Small Energy Cell on the robot.
			if(valid(item))
			{
				if(item.GetProtoId() == PID_SMALL_ENERGY_CELL)
				{
					player.Say(SAY_NETMSG, "You replace one of the energy cells of the robot.");
					//	Set the quest progress
					questVar = 30;
					//	Remove the Small Energy Cells used.
					item.SetCount(item.GetCount() - 1);
					item.Update();
					return true;
				}
			}
		}
		else
		{
			if(skill == SK_REPAIR || skill == SK_SCIENCE)
			{
				player.Say(SAY_NETMSG, "You already replaced the energy source of this robot, there is nothing more you can do here.");
				return true;
			}
		}
	}
	return false;
}

• r_GetQuest(..)
  
  • This function should be called from the dialog, when the NPC gives the quest.
  • If the timed even is available, then it will summon the location, but this is a precation only, the dialog branching should decide this.
  • Try and test this, if the timer is not up, it should say in system window that the quest is not available yet.
• e_ResetSpawnLocTimer(..)
  
  • This is an even function which will be called from r_getQuest(..) and is responsible for reseting the timer.
  • All this function does, is to call the setTimedEventAvailable(..) function to allow the retaking of the quest.
• setTimedEventAvailable(..)
  
  • Is used to set the Unique variable for this quest timer.
• isTimedEventAvailable(..)
  
  • Check the value of the timer variable.

//	Demo for Timed Event used for repeatable quests.
void r_GetQuest(Critter& player, Critter@ npc)
{
	player.Say(SAY_NETMSG, "r_GetQuest() called");
	if (isTimedEventAvailable(player, npc))
	{
		uint[] values = {player.Id, npc.Id};
		setTimedEventAvailable(player, npc, false);
		CreateTimeEvent(AFTER(REAL_SECOND(10)), "e_ResetSpawnLocTimer", values, false);
		r_SpawnLoc(player, npc);
	}
	else
	{
		player.Say(SAY_NETMSG, "r_GetQuest() - Quest not available yet.");
	}
}

//	S
uint e_ResetSpawnLocTimer(array<uint>@ values)
{
	Critter@ player = GetCritter(values[0]);
	player.Say(SAY_NETMSG, "e_ResetSpawnLocTimer()");
	Critter@ npc = GetCritter(values[1]);
	setTimedEventAvailable(player, npc, true);
	return 0;
}

bool setTimedEventAvailable(Critter& player, Critter@ npc, bool isReady)
{
	player.Say(SAY_NETMSG, "setTimedEventAvailable()");
	if(!valid(player) || !valid(npc))
		return false;
	GameVar@ var = GetUnicumVar(UVAR_q_timedEventAvailable, npc.Id, player.Id);
	if (!valid(var))
	{
		return false;
	}
	if (isReady)
	{
		var = 1;
		player.Say(SAY_NETMSG, "setTimedEventAvailable() - 1");
	}
	else
	{
		player.Say(SAY_NETMSG, "setTimedEventAvailable() - 0");
		var = 0;
	}
	return true;
}


bool isTimedEventAvailable(Critter& player, Critter@ npc)
{
	player.Say(SAY_NETMSG, "isTimedEventAvailable()");
        if(!valid(player) || !valid(npc))
                return false;
	GameVar@ var = GetUnicumVar(UVAR_q_timedEventAvailable, npc.Id, player.Id);
	if (!valid(var))
	{
		return false;
	}
	if (var == 0)
	{
		player.Say(SAY_NETMSG, "isTimedEventAvailable() == 0");
		return false;
	}
	else
	{
		player.Say(SAY_NETMSG, "isTimedEventAvailable() == 1");	
		return true;
	}
}