@@ -66,7 +66,7 @@ For example, here's a `content.json` which replaces Abigail's portraits with you
66
66
67
67
``` js
68
68
{
69
- " Format" : " 2.5 .0" ,
69
+ " Format" : " 2.6 .0" ,
70
70
" Changes" : [
71
71
{
72
72
" Action" : " Load" ,
@@ -121,7 +121,7 @@ So if you wanted to change Abigail's portraits, you would use Content Patcher to
121
121
5 . Create a ` content.json ` file with this content:
122
122
``` js
123
123
{
124
- " Format" : " 2.5 .0" ,
124
+ " Format" : " 2.6 .0" ,
125
125
" Changes" : [
126
126
// your changes will go here
127
127
]
@@ -134,7 +134,7 @@ That's it! You now have a working Content Patcher pack, though it doesn't do any
134
134
That ` Format ` field is the version of Content Patcher for which you designed the content pack. This
135
135
is used to keep your content pack compatible with future versions.
136
136
137
- You should always use the latest format version (currently ` 2.5 .0 ` ) to enable the latest features,
137
+ You should always use the latest format version (currently ` 2.6 .0 ` ) to enable the latest features,
138
138
avoid obsolete behavior, and reduce startup time.
139
139
140
140
### Changes
@@ -167,7 +167,7 @@ would change her portraits in-game:
167
167
168
168
``` js
169
169
{
170
- " Format" : " 2.5 .0" ,
170
+ " Format" : " 2.6 .0" ,
171
171
" Changes" : [
172
172
{
173
173
" Action" : " Load" ,
@@ -201,7 +201,7 @@ For example, this doubles the price of moss soup (see [object fields](https://st
201
201
202
202
``` js
203
203
{
204
- " Format" : " 2.5 .0" ,
204
+ " Format" : " 2.6 .0" ,
205
205
" Changes" : [
206
206
{
207
207
" Action" : " EditData" ,
@@ -238,7 +238,7 @@ For example, if your content pack has an `assets/tuna.png` image with a custom
238
238
239
239
``` js
240
240
{
241
- " Format" : " 2.5 .0" ,
241
+ " Format" : " 2.6 .0" ,
242
242
" Changes" : [
243
243
{
244
244
" Action" : " EditImage" ,
@@ -269,7 +269,7 @@ This lets you...
269
269
For example, this replaces the town square with a custom version in your content folder:
270
270
``` js
271
271
{
272
- " Format" : " 2.5 .0" ,
272
+ " Format" : " 2.6 .0" ,
273
273
" Changes" : [
274
274
{
275
275
" Action" : " EditMap" ,
@@ -296,7 +296,7 @@ exactly as if they were directly in `content.json`.
296
296
For example, you can combine this with [ tokens and condition] ( #tokens ) to load a dynamic file:
297
297
``` js
298
298
{
299
- " Format" : " 2.5 .0" ,
299
+ " Format" : " 2.6 .0" ,
300
300
" Changes" : [
301
301
{
302
302
" Action" : " Include" ,
@@ -332,7 +332,7 @@ For example, this gives Abigail a different portrait for each season:
332
332
333
333
``` js
334
334
{
335
- " Format" : " 2.5 .0" ,
335
+ " Format" : " 2.6 .0" ,
336
336
" Changes" : [
337
337
{
338
338
" Action" : " Load" ,
@@ -347,7 +347,7 @@ Or this gives her different seasonal portraits if you're married to her:
347
347
348
348
``` js
349
349
{
350
- " Format" : " 2.5 .0" ,
350
+ " Format" : " 2.6 .0" ,
351
351
" Changes" : [
352
352
{
353
353
" Action" : " Load" ,
@@ -372,7 +372,7 @@ For example, you can use config values as [tokens and conditions](#tokens):
372
372
373
373
``` js
374
374
{
375
- " Format" : " 2.5 .0" ,
375
+ " Format" : " 2.6 .0" ,
376
376
" ConfigSchema" : {
377
377
" EnableJohn" : {
378
378
" AllowValues" : " true, false" ,
@@ -403,7 +403,7 @@ in any Content Patcher field that allows [tokens](#tokens):
403
403
404
404
``` js
405
405
{
406
- " Format" : " 2.5 .0" ,
406
+ " Format" : " 2.6 .0" ,
407
407
" Changes" : [
408
408
{
409
409
" Action" : " EditData" ,
0 commit comments