It's not that hard to guess what the structure of the config looks like by just having a look at the code. Let's have a look for any occurrences of the config in Ark's code.
Code:
for (let i = 0; i < config.list.length; i++) {
OK, so there is an array called 'list'.
Code:
player.name.toLowerCase() == config.list[i].name.toLowerCase()) {
The items in that array have a property called 'name' which we know is a string since it's being compared to one here.
Code:
'Found: '+ player.name + ' : ' + config.list[i].type);
The items also have a property called 'type' which is most likely also a string.
Code:
for (let i = 0; i < config.portals.length; i++) {
There is another array called 'portals'.
Code:
update.newObjects[k].objectType == config.portals[i].id
The items in that array have a property called 'id' which we know is a number since its being compared to one here.
Code:
' Found: ' + config.portals[i].name);
The items also have a property called 'name' which is most likely a string.
Putting all of this information together, we can guess that the config looks something like this
Code:
{
"list": [
{
"name": "Eendi",
"type": "Cool players"
},
{
"name": "Oshyu",
"type": "Fame Trainers"
},
{
"name": "You get the idea",
"type": "I hope"
}
],
"portals": [
{
"id": 81942,
"name": "Ice Tomb Portal"
},
{
"id": 23879423,
"name": "Cave of a Thousand Treasures"
}
]
}