Items not currently being POSTed by the game engine

[sdunham]

Here's a list of items which are not currently being POSTed by the game engine, and which probably should be:

• Robot's score (engine.player.score)
• Phone scores (see Phone Score API)
• Deleted tiles (engine.platforms.deletedTiles, 2d array)

Other questions that came up during today's meeting:

• Are you looking for minion requests from the phones and creating them?

[sdunham]

Another question: What's the convention for the deleted tile coordinates? (what does [2,3] signify)

[d-bahr]

[2, 3] signifies a row-column pair, beginning at 1 I believe (I will confirm this shortly).

Also, the documentation does not define where the robot's score should be placed. Can you add that to this page as well? https://github.com/UPS-CS240-F12/WebServerGroup/wiki/JSON-Object-Specification I'll add it to engine.player.score for now, as requested.

Still in the works -- I will post back again when I've pushed the bug fixes.

[etan-bard]

My empty tiles list should include negative values (I then scale the coordinates to fit the designated game size, but it isn't as useful with a fixed game size). This was done so the center of the gameworld is on a corner of the origin.

[sdunham]

Didn't realize we hadn't included the player's score in the spec. Fixed!

On Sat, Dec 8, 2012 at 5:51 PM, Daniel Bahr notifications@github.comwrote:

[2, 3] signifies a row-column pair, beginning at 1 I believe (I will
confirm this shortly).

Also, the documentation does not define where the robot's score should be
placed. Can you add that to this page as well?
https://github.com/UPS-CS240-F12/WebServerGroup/wiki/JSON-Object-SpecificationI'll add it to engine.player.score for now, as requested.

Still in the works -- I will post back again when I've pushed the bug
fixes.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-11166430.

[d-bahr]

Awesome, thanks.

I will add a modifier to the tile locations so that they go from 0 to 7 (8 rows and 8 columns). So a potential tile location can look like: [2, 4]. This would mean the tile that is 2nd on the x-axis and 4th on the z-axis.

I've got everything working now, just need to push the changes, which I'll do when I get home...

[sdunham]

Sounds good.

Something I just noticed in the spec... It says that deletedTiles should only have values added to it (never taken away). Not sure that makes sense now that tiles can be regenerated, though... I'm assuming you'll be removing them from the array once they've been replaced?

[d-bahr]

Yeah. So our idea was to have regenerating tiles. Basically, I'm looping through the whole array each time we send JSON data, so deleted and regenerating tiles should take of themselves. Alas, it's also incredibly inefficient on my part =\

I need to think of a way to make that better, but it should work nonetheless.

[d-bahr]

Just pushed my changes. Included are all the bug fixes above and working Kinect integration. Woo! I'm going to go ahead and close the bug.