Comments on: Akihabara Tutorial, Part 3: Basic Mapping

By: Darius K.

Darius K. — Thu, 29 Dec 2011 15:31:25 +0000

I don’t think null is required. It’s just a mapping function — you could leave null in there, set it to some random character like ~, and just never use ~ in your map. Or, just skip the [null, ' '] and do something like:

[ [0, ' '], [1, 'X'] ]

Where the 0-tile is your standard background tile. Or whatever else you want. It can be any configuration you like.

By: John Rockefeller

John Rockefeller — Thu, 29 Dec 2011 03:38:45 +0000

Great tutorials. Thank you ever so much for these.

I’m wondering, though, how to eliminate the ‘null’ value in my asciiArtToMap parameter. I want every tile covered with an image in my tilemap. No nulls!

If null is required, is there a way to specify an image for null rather than being empty?

By: Jaydeep

Jaydeep — Sat, 24 Sep 2011 17:18:13 +0000

its all good, but sadly, theres no documentation on using PAD for touch based devices like iDevices and Android. Sadly will have to give up working on this and look for some other library which has good documentation.

By: Darius Kazemi

Darius Kazemi — Thu, 05 Aug 2010 14:04:25 +0000

The ‘map’ argument is the ID of the tilemap itself. In our map object we have an array, map.map (the second map being the tilemap).

In theory we could change the name to map.tilemap and then we’d change that third argument in the call to ’tilemap’, but the problem is that there is a lot of code in Akihabara that just assumes that the array is called map.map. For a future version of Akihabara we should either hardcode it to map.map (and get rid of the confusing third argument), or make everything more flexible.

By: Matt

Matt — Thu, 05 Aug 2010 06:12:05 +0000

Hello! Thanks for your tutorials. Been following them and trying my hand on the framework.

I started expanding to include multiple tile layers and stumbled on this question:

In the tileCollision method like your example here:
toys.topview.tileCollision(this, map, ‘map’, null, { tolerance: 6, approximation: 3 });

What does the third argument ‘map’ signify?

Thanks again!

By: Pqrks

Pqrks — Wed, 28 Jul 2010 00:35:21 +0000

Thanks for the tutorials! It makes the learning curve on this framework a lot easier. Hopefully once I more fully understand the code I will be able to upload a few docs to contribute to the project. Keep it up!

pqrkchqps

By: Some reminiscences, some memories » Blog Archive » [翻译]Akihabara 指南，第三部分：基本的地图

Wed, 07 Jul 2010 08:15:17 +0000

[...] 原文：http://bostongamejams.com/akihabara-tutorials/akihabara-tutorial-part-3-basic-mapping/ [...]

By: Some reminiscences, some memories » Blog Archive » [翻译]Akihabara 指南，第二部分：精灵的移动

Sat, 03 Jul 2010 13:53:34 +0000

[...] 指南系列第一部分: 标题屏幕第二部分: 移动一个精灵第三部分: 基本的地图第四部分: 卷动地图第五部分: 敌人和 [...]

By: Some reminiscences, some memories » Blog Archive » [翻译]Akihabara 指南，第一部分：标题屏幕

Tue, 29 Jun 2010 15:32:02 +0000

[...] Tutorial Series 第一部分: 标题屏幕第二部分: 移动一个精灵第三部分: 基本的地图第四部分: 卷动地图第五部分: 敌人和 [...]

By: t

Tue, 15 Jun 2010 06:23:51 +0000

Thanks for continuing the tutorial series. I’ve been checking back nearly daily since I found the first two, and worked through this as soon as I saw it was up. These are really helpful considering the lack of documentation in the engine code.

I’ve been playing with the platformer toys in parallel, but I used an array of arrays for the map based on the “leavemealone” sample. After doing the tutorial I realized that the array of arrays is the finalized version of the ascii map after it’s gone through that help function, and I understand that the nulls and 0000′s aren’t arbitrary.

Thanks!