Posted July 25, 2020 by vfabien21
Ok, this time I wanted to move on to something more interresting.
In a previous round, I had a very promising way to define goods, and how they might evolve as the planet develops (from lvl1 to lvl2)
Lvl1 : pink potatoe lvl2 : pink jam Lvl1 : good looking lettuce lvl2 : pruned good looking lettuce Lvl1 : moon-apple lvl2 : crates marked with moon-symbols Lvl1 : rainbow potatoe lvl2 : rainbow pickeld potatoe Lvl1 : surprising fruit lvl2 : surprising jam
Each product is defined as a product (potatoe) + a qualifier (pink), and also a productType and qualifierType to transform them correctly.
Now, I wanted to cross that with the planet type and features. ( for example, to produce "Sand Cactus" on a "Desert planet covered with dunes." and transform them into "Cans marked with a dune and a cactus" )
TextStew can handle it. But code cmplexity rises incredibly quick, and gets hardly readable.
#Food *PlanetType#R-2020-07-23.PlanetType/#R-2020-07-23.FoodStep2:&PlanetType #FoodStep2:PlanetType *PlanetFeature#R-2020-07-23.PlanetFeature:@PlanetType/ , #R-2020-07-23.ProductionSetter:Production:ProductionType:Qualifier:QualifierType:PlanetFeature:PlanetType , Planet type : &PlanetType . Planet feature : &PlanetFeature . Production : &Production . Qualifier : &Qualifier #FoodLvl1:ParamPlanetType:ParamPlanetFeature #R-2020-07-23.@ParamPlanetType @ParamPlanetFeature/#R-2020-07-23.RandomHyphen/#R-2020-07-23.@ParamPlanetType (...)
So, I will probably put that asside for a few days, while I do some work to improve the language.
I might keep playing with planet descriptions though (just to keep practicing)