I think you are going to have to not use the car-behavior in your specific case. It was never designed to work in narrow passages. Or perhaps disable it temporarily while you are in that specific location.

So am I right on organizing them? If a Hammer has ingredients of wood and iron then I would have three separate XML files.

One for wood, one for iron and one with craftable items (hammer, basket, hat)?

If user searches hammer then it will show wood and iron.

If user searches wood then hammer will show up.

If user searches wood and iron then I can compare and still bring up hammer since it is in both?

If I search leaf and wood then hammer would not show up because hammer isn't under leaf.

I assume I would compare the the leaf and wood XML and remove the ones that don't match.

I am not sure how to do that. Would I somehow use an array to compare?

Would this be the best way?

Yea, that looks good. The alternative is to do a backwards search through parameters, which would take considerable cpu power.

Why does your vehicle have to be on a road more narrow than its collision box?

You have two rotation points in the center of the "tracks" of your bulldozer....

Actually, look at this first:

https://www.gamedev.net/topic/201762-ba ... -movement/

https://gamedev.stackexchange.com/quest ... t-solution

https://forums.tripwireinteractive.com/ ... ed?t=22457

https://stackoverflow.com/questions/667 ... d-movement

You need to use some kind of database.

Use JSON, like:

{ 
 "inventory" : 
   {
           "sword" : { "damage" : 1 },
           "cloak" : {"armor" : 1},
           "armor" : {"armor" 4 }
   }
}
[/code:1drbr2gr]

You have to modify the index.html that the exporter outputs:

https://developers.google.com/maps/docu ... google-map

https://drive.google.com/file/d/0B-xiqK ... sp=sharing

I would use JSON, simply because it is easier and more human readable.

If you have lots of sub-attributes and categories or abstractions, then XML is better.

Sorry, I have been insanely busy lately.

But you need a better schema for identifying which tile has which doors.

Sadly, I have not developed such a system yet, only theorized about what I might do in such a system, so I will be of limited help.

I would recommend studying cesisco 's work here:

You might have to ask if he will share his capx with you (Or publicly).

Like tunepunk says, the default C2 project starts with 500,500 margins which -- in my experience -- you always want to set to 0,0 to make the sprites appear in the proper places.