From 7d14a033f27f026350a9af90ec6cd2d95fcce747 Mon Sep 17 00:00:00 2001 From: C'tri Goudie <CtriCoding@Ctri.co.uk> Date: Sun, 14 Jan 2024 12:27:46 +0000 Subject: [PATCH] Update version 2.1.4 (week 27&28).md --- blog/version 2.1.4 (week 27&28).md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/blog/version 2.1.4 (week 27&28).md b/blog/version 2.1.4 (week 27&28).md index bcaef8b..f7d9bc9 100644 --- a/blog/version 2.1.4 (week 27&28).md +++ b/blog/version 2.1.4 (week 27&28).md @@ -13,7 +13,12 @@ Chain trading is pretty good for efficiency, but during the ramp up we really wa I've created a simple "trade best" behaviour that will look at the best trade available and execute it. It can be optimised by factoring in the distance to the starting location. The commander is set to use this behaviour when it's trading. -: +## Ramp up improvements - "Manage supply chain" +so far we've not automated the fancy supply chain managment behaviour from last time - but additionally we observed markets evolving whilst restricted. This means that restricted doesn't block evolution, but does slow price changes. Evolving a restricted market is easier whilst they're restricted. Thus, focusing on evolution step by step is the best way, not trading exports UNTIL their imports are evolved. That's unlikely to happen since our other trade routes are going to want to trade the those exports, and we don't have a reservation system. + + +## Ramp up improvements - "Evolve" +Evolution and managing of markets ar actually super seperate, so before we start managing a chain we should evolve it to its best possible state. ## Command and control