User Tools

Site Tools


migration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
migration [2021/07/15 15:08] – [Foundation Preview 1.6.0.0522] polymorphgamesmigration [2021/10/22 10:05] maxime
Line 1: Line 1:
 ====== Migration Notes ====== ====== Migration Notes ======
  
-===== Foundation Preview 1.7.1.0610 =====+===== Foundation 1.8.0.=====
  
-  * [[changelog:1.7|Full Preview Changelog]] +  * [[changelog:1.8|Full Changelog]] 
-  [[preview:api|Preview Scripting API]] + 
-  * [[preview:assets|Preview Assets]]+==== Resource bundles ==== 
 + 
 +Building part costs have been changed to allow for building in steps, with the builder bringing a bundle of resources for each step. 
 + 
 +To allow this, ''BUILDING_PART_COST.RessourcesNeeded'' has been replaced with ''[[preview:api:building_part_cost#ResourceNeededList|BUILDING_PART_COST.ResourceNeededList]]'', a list of lists of ''[[preview:api:resource_quantity_pair|RESOURCE_QUANTITY_PAIR]]''. Each entry in the outer list corresponds to a bundle. 
 + 
 +The number of construction steps built for each bundle is proportional to a bundle's quantity of resources. For example, if a part needs two resource bundles, one with 30 planks and the other with 10 planks, 75% of the construction steps will be done with the first bundle, and the rest with the second bundle. 
 + 
 +===== Foundation 1.7.1 ===== 
 + 
 +  * [[changelog:1.7|Full Changelog]]
  
 ==== Texture loading ==== ==== Texture loading ====
  
-Some ''[[api:texture|TEXTURE]]'' properties have been changed, depending on their use, to a new type: ''[[preview:api:atlas_cell|ATLAS_CELL]]''.+Some ''[[api:texture|TEXTURE]]'' properties have been changed, depending on their use, to a new type: ''[[api:atlas_cell|ATLAS_CELL]]''.
  
 Therefore, we added a way to explicitly choose the type of an asset to load, when calling ''[[mod-management-functions#registerassetid|registerAssetId]]''. Specifying the type is optional, ''TEXTURE'' will be inferred for texture assets if absent. Therefore, we added a way to explicitly choose the type of an asset to load, when calling ''[[mod-management-functions#registerassetid|registerAssetId]]''. Specifying the type is optional, ''TEXTURE'' will be inferred for texture assets if absent.
migration.txt · Last modified: 2023/09/05 11:21 by mathieu

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki