Transport Tycoon Forums

Pingaware wrote:Have you downloaded the scenario? As far as I remember from my last test, you have to load the scenario and then the script will automatically run. Zuu can confirm/deny this best however.

EmperorJon wrote:Anyway, I'm interested in helping this along at some point. Not right now, very busy, but in the future I may be able to put in some time, either learning to use gamescript as I go or just writing generic "this is what I think this chapter should say" stuff, providing general feedback, spellchecking, all the simple stuff.

Zuu wrote:While I like the idea to transport the goods produced by the oil chain, that will require users to always take the ship chapter before trucks. For this reason I propose to use a primary chain for trucks instead. A second option would be that if you choose the truck chapter before the ship chapter you are offered to either cancel or let an AI to complete that chapter. Currently I think that the former solution is better and is also easier (quicker) to implement.

MinchinWeb wrote:

Zuu wrote:While I like the idea to transport the goods produced by the oil chain, that will require users to always take the ship chapter before trucks. For this reason I propose to use a primary chain for trucks instead. A second option would be that if you choose the truck chapter before the ship chapter you are offered to either cancel or let an AI to complete that chapter. Currently I think that the former solution is better and is also easier (quicker) to implement.

I see your point Zuu. If you want code for an AI to run a ship, I could modify something out of my AI, WmDOT, rather quickly. The other reason I liked using the ship-serviced Oil Refinery is there will always be lots of goods to truck away.

/*static*/ function ChapterShips::Init(table)
{
	// Industry index 0
	table.refinery <- 0;

	// Industry index 1 and 2
	table.oilrig1 <- 1;
	table.oilrig2 <- 2;

	// station IDs for the oilrig stations
	table.oilrig1_station <- GSStation.GetStationID(GSIndustry.GetDockLocation(table.oilrig1));
	table.oilrig2_station <- GSStation.GetStationID(GSIndustry.GetDockLocation(table.oilrig2));

	// canal start/end
	table.canal_start_tile <- g_tile_labels.GetTile("CanalStart");
	table.canal_end_tile <- g_tile_labels.GetTile("CanalEnd");
	table.canal_lock1 <- g_tile_labels.GetTile("CanalLock1");
	table.canal_lock2 <- g_tile_labels.GetTile("CanalLock2");
}

• Builds a ship to transport oil from the most productive rig to the oil refinery. Will build docks, depots, and buoys as required.

• Build canals, or otherwise terraform
• Connect both oil rigs to the refinery
• Build more than one ship, replace old ships, or otherwise manage ships

• The pathfinder can take a long time to fail if there is no possible connection; this could be an issue if it tries to connect the oil rigs that needs the canal built first.

import("util.MinchinWeb", "MetaLib", 5);
	Array <- MetaLib.Array;
	Atlas <- MetaLib.Atlas;
	Marine <- MetaLib.Marine;
	OpLog <- MetaLib.Log;
import("util.superlib", "SuperLib", 25);		//	For loan management,etc
	SLMoney <- SuperLib.Money;
	Helper <- SuperLib.Helper;
	AIAbstractList <- AIList;

require("OpMoney.nut");
require("Tutorial.OpHibernia.nut");

• Updated strings to the last changes by Pingaware
• Fix: some strings included more {TOWN} than code
• Feature: Trucks chapter
• Codechage: Moved some code to common.nut to be shared by all chapters.

Zuu wrote:I have only lightly reviewed the texts from the chapter plan for the trucks chapter and focused on the programming part to get a functional chapter. I hope Pingaware or someone else is interested to have a look at the strings and suggest improvements.

Pingaware wrote:As promised Zuu, here are my suggested changes to the strings. As usual, there are minor changes throughout and major changes to the new chapter.

Pingaware wrote:The town "Highland Hills" hasn't got the second word capitalised when it should do

Pingaware wrote:, and there is a bug in the string STR_TRUCKS_4_6_4_ORDERS. When I went through this part of the tutorial, this string didn't correctly display the station. It came up first as "Undefined/Unknown Station" and then flickered between some of the town names as I moved my cursor around the screen. Couldn't work out what was causing it to change to the different town names.

Pingaware wrote:Edit: Would you object if I asked in the General OpenTTD forum for experienced players to play through the tutorial? I'm interested in hearing other players' opinions on how clear my strings are to understand.

Zuu wrote:Great that you keep taking an active role in taking care over the strings.

Zuu wrote:However, when I replace english.txt with your updated english.txt I get the following error which I do not get with the old english.txt from the released version 8. I wonder, do you test the language file before uploading it here? Does it work for you? If you did export it directly from Word, it probably needs to be converted from windows-1252 to UTF8 as it contains some non-ASCII dash characters. (at least when working with data exported from Excel, I know that this conversion is often needed if you need data do be in UTF8)

BlueDeath wrote:Just some points questions about that tut:

- has the first plane anything loaded? My default is not fully load and so the plane would be empty.
STR_AIRPLANES_2_3_5_ORDERS :Click anywhere on the airport in {TOWN}, excluding the hangar. This gives an order to the aircraft to go to this airport, and load any passengers and mail which are currently waiting.

-> Tell about why the first time nothing is loaded? And that changing orders comes in next capter?

english.txt wrote:STR_AIRPLANES_2_4_1_SUM_UP :Aircraft - Station Window and Vehicle Details Window{}{}You have now completed your first transport route in OpenTTD. Before moving onto the next chapter, you'll be shown how to look at some more detailed information about your route.{}{}To see the number of passengers and the amount of mail waiting at an airport, click anywhere on the airport, excluding the hangar.{}{}Note that before the first aircraft has visited the station, there will be no passengers or mail showing up at the station. Only after the first visit, customers will know about the service and start to use it.

BlueDeath wrote:STR_SHIPS_3_3_3 :You may have realised that you haven't built a dock by the oil rig. However, you won't have to do this as oil rigs, uniquely in OpenTTD, have their own in-built station.{}{}Click on the highlighted buttons to give orders to your ship to go first to the oil rig ({STATION}), then go to the refinery dock ({STATION}).{}{}Note that you will have to click on the rear tile marked as "Dock Tile" on the oil rig to give the ship the order to go to the oil rig.

-> What about skipping orders after first visit to get the ship loaded a bit next time?
-> What about shared orders

BlueDeath wrote:Trucks
-> Cloneing with shared orders?

BlueDeath wrote:edit: You could force the user to make an plane goto hanger order to tell the difference instead of a warning when done.

Zuu wrote:That is possible, or keep it as is, and cover servicing in detail later. Its all a trade off between how much details to provide in the first chapter or how many chapters there will need to be. My guess is that newbies will probably want to see results quickly before getting too much into details.

MinchinWeb wrote:the functions for a GameScript to give orders to a vehicle have yet to be implemented. (Is this something easy for you to fix Zuu?) The ship building takes about a month to complete. If you want to review the code, it's up on GitHub.

krinn wrote:

MinchinWeb wrote:the functions for a GameScript to give orders to a vehicle have yet to be implemented. (Is this something easy for you to fix Zuu?) The ship building takes about a month to complete. If you want to review the code, it's up on GitHub.

You could trigger the AI to do it for the GS itself when trigger by a sign. For pre-define/simple task it could be done in few lines.

I don't know what you wish to do: if it's only "turn your order to FULLLOAD"... it is really easy.