JSON Export - Discussions Game

Bald_Eagle · May 31st 2018

could you please list in your post JSON Export all possible values for user.status (and any other Enum I have not noticed yet)? That would be very helpful.

Btw., are you aware that you have uninhabited planets that have a name:

Code

"id": 60,
            "position": 12,
            "temperature": 30,
            "coords": "01:04:12",
            "name": "Stefan Kuntz",
            "image": "\/img\/planet\/planet_60.gif",
            "user": false,

One more thing I'm still undecided whether to be impressed or appalled:

Code

"user": {
                "id": 1,
                "nickname": "<div style=\"display:inline-block;\"><table cellpadding=0 cellspacing=0><tr><td><div style=\"display:inline-block;height:14px;width:35px;overflow:hidden;border-radius:4px;background:#000;margin-right:2px;\"><img style=\"height:18px;display:inline-block;top:-1px;left:4px;position:relative;\" src=\"https:\/\/board.bitmeup.com\/wcf\/icon\/flag\/bmu.svg\"><\/div><\/td><td>Dschibait<\/td><\/tr><\/table><\/div>",
                "status": "admin",
                "ranking": false
            },

That 'nickname' is over 400 characters long! My DB barfed at me b/c I have NAME VARCHAR(255) in it. Of course, that is true for the screen-scraped version, too, only shows that I didn't import anything for quite some time. Anyway, since this is a machine interface, can we strip out the eye candy? I think status: "admin" is a dead giveaway.

Best regards
Eagle

Dschibait · May 31st 2018

Hi,

Quote

could you please list in your post JSON Export all possible values for user.status (and any other Enum I have not noticed yet)? That would be very helpful.

i added (hopefully) all planet status values on that galaxy post.

Quote

Btw., are you aware that you have uninhabited planets that have a name:

yeah, its possible that we have such names. But if that user (or any other user) dont report that planet, we dont change them. Its hard to have an automatism that checks if this "could" be a real name or not.
For that we need the help of all players.

Quote

That 'nickname' is over 400 characters long! My DB barfed at me b/c I have NAME VARCHAR(255) in it. Of course, that is true for the screen-scraped version, too, only shows that I didn't import anything for quite some time. Anyway, since this is a machine interface, can we strip out the eye candy? I think status: "admin" is a dead giveaway.

the problem is that on the galaxy map also titles are involved. Means that you get the fully nickname + title here (the title is that bitmeup logo in front of the admin name).

I will remove the tiles for that json.

regards
Dschibait

Bald_Eagle · May 31st 2018

Quote from Dschibait

the problem is that on the galaxy map also titles are involved. Means that you get the fully nickname + title here (the title is that bitmeup logo in front of the admin name).

I will remove the tiles for that json.

How about a compromise, a key 'nickname' and a separate key 'title'.

Dschibait · May 31st 2018

so now you have the "name" field with only the name - and i added a new field called "title" with the title.

please notice - thats the title without username so for example:

"Schrottsammler %name%" or "Astroschütze %name%"
(they are localized!) - you need to replace the %name% with the unsername to get the full "titled" username.

regards
Dschibait

Bald_Eagle · May 31st 2018

Works for me.
Thank you.

Bald_Eagle · Jun 5th 2018

I know I specifically asked for it, but I now reconsidered.
This

Code

"buildings": {
                "building_6": "0",
                "building_7": "12",
                "building_8": "0",
                "building_9": "13",
            },
            "ships": {
                "1": "0",
                "2": "0",
                "15": "0",
                "16": "0"
            },
            "defense": {
                "1": "0",
                "2": "0",
                "10": "1",
                "11": "1"
            },

Display More

is a fragment of the Intergalactic planet overview. This

Code

"buildings": {
            "6": {
                "name": "Thermosolarfabrik",
                "level": "1"
            },
            "7": {
                "name": "Entwicklungszentrum",
                "level": "12"
            },
            "9": {
                "name": "Waffenfabrik",
                "level": "10"
            },
        },
        "ships": null,
        "defense": {
            "3": {
                "name": "Leichte Gravitonkanone",
                "level": "1"
            },
            "4": {
                "name": "Schwere Gravitonkanone",
                "level": "1"
            },
            "11": {
                "name": "Gro\u00dfe Schildkuppel",
                "level": "1"
            }
        },
        "researches": {
            "1": {
                "name": "Minentechnik",
                "level": "1"
            },
            "2": {
                "name": "Energietechnik",
                "level": "1"
            },
        },

Display More

is a fragment of a spy report. And this

Code

"agressor": {
                "s3": {
                    "name": "Transmitter",
                    "level": "10"
                },
                "s7": {
                    "name": "Phoenix",
                    "level": "30"
                }
            },
            "defender": {
                "d3": {
                    "name": "Leichte Gravitonkanone",
                    "level": "4"
                },
                "d4": {
                    "name": "Schwere Gravitonkanone",
                    "level": "17"
                },
                "d5": {
                    "name": "Ionengesch\u00fctz",
                    "level": "21"
                },
                "d11": {
                    "name": "Gro\u00dfe Schildkuppel",
                    "level": "1"
                }
            }

Display More

is a fragment of a battle report.
I humbly ask that all keys be in the same format. And if that means that building keys in the Intergalactic planet overview are just number (well actually strings that consist only of numbers), so be it. However, at least the defender in a battle still needs to distinguish between defense and ship IDs, so maybe an alphanumeric component to the key is feasible. But please let it be consistent.
Sorry for the inconvenience.

Dschibait · Jun 6th 2018

thats what i mean - the keys (or sub-objects/arrays) are existing variables.

so i can bring them all to a standard like
sXX => ship
dXX => defense
bXX => building

but i need to "recreate" this variables for the json output. I think this is not an technical problem; but you know - its work

Is there a Problem with the existing ones?

regards
Dschibait

Bald_Eagle · Jun 6th 2018

I apologize for causing unnecessary work, but the inconsistent building keys hurt. I can live with them being numerals in the Intergalactic planet overview as before. Sorry for causing all the fuzz.

Ideally I would prefer all keys being consistent according to the scheme you proposed
sXX => ship
dXX => defense
bXX => building
rXX => research
since that would bring battle reports neatly in line.

Best regards
Eagle

Dschibait · Jun 6th 2018

ok, i changed the keys (and structure) for any building, ship, defense and research to

the key name like:
s1, d1, b1, r1

s = ship
d = defense
b = building
r = research

followed by a number (id) of the entry.

also i changed (hopefully everywhere) the structure to
(for example building 1)

"b1" => object(
"name" => "Name of building"
"level" => "level / amount of entry"
)

if i miss something, please let me know.

regards
Dschibait

Bald_Eagle · Jun 7th 2018

One more small thing, the Intergalactic planet overview has

Code

"ships": {
            "s1": {
                    "name": "Kleiner Transporter",
                    "Level": 0
                }
            },
            "defense": {
                "d1": {
                    "name": "Mörser",
                    "Level": 0
                }
            },
            "buildings": {
                "b1": {
                    "name": "Roheisenmine",
                    "Level": 0
                }
            },

Display More

but even there

Code

"researches": {
        "r1": {
            "name": "Minentechnik",
            "level": 1
        },
    }

Could you please make it so that it uses 'level', like everywhere else? Thank you.

Best regards
Eagle

Dschibait · Jun 7th 2018

i changed all "Level" to lowercase "level"

Bald_Eagle · Jun 7th 2018

I still see 'Level'.

Logged out
Cache cleared
Browser restarted

What else?

*edit* now it is 'level'.

Dschibait · Jun 8th 2018

hm - maybe still a caching problem.

should i add all flying fleets (combined) to the int. planet overview json?

Bald_Eagle · Jun 8th 2018

What do you mean with 'combined'?
- All flying ships lumped together, not bound to any planet?
- Flying ships bound to the planet they end up when they finally land? (target planet for station, origin planet for everything else (even alliance attacks or colonizations))

Dschibait · Jun 8th 2018

combined ors sumsed up - so did you not see where they start or came back

i dont like to put any fleet action into that json - this will make it rly easy to build bots (i think you know what i mean :))

Bald_Eagle · Jun 8th 2018

I'm completely with you, I just want to know in which way combined you intended, ALL flights together or all flights together by planet? The first would not be terribly useful, the second much more so.

Dschibait · Jun 8th 2018

you mean combined by the starting planing (except station flights, there the target planet?)

Bald_Eagle · Jun 8th 2018

Yes

Bald_Eagle · Jun 9th 2018

A question to battle reports.
What does "allianceAttackMember": "" contain when there actually was an alliance attack? A list of strings (["attacker1", "attacker2", "etc."])? Is the 'attacker' also included in this list?

Best regards
Eagle

Dschibait · Jun 9th 2018

yes, this contains a string with all members like
"playerA, playerB, playerC"

i think, that the attacker is also included - i need to search for an alliance attack later
(maybe someone has a report for that ? :))