Medici was an interesting project because of how simple it was. It is my first conversion project that has taken significantly less time than I thought it would and is also the quickest that I’ve been able to make a new game.
I recently wanted to add a photo search capability to my Timeline program and discovered that you can open a windows explorer with a custom search. You can also type these searches directly into the address bar in a windows file explorer.
The key is the search-ms protocol. It allows programs (like windows explorer) to directly query the windows search index. The parameters to this command are somewhat obscure, but it is very flexible and it can be used to perform any search that you could perform with the graphical search function in the windows file explorer.
For my application, I wanted to search for all photos that were taken between two dates (the start and end date of an event on my timeline). The idea is to quickly find all the photos that I took on a trip or at an event.
The general syntax for the search-ms command is:
crumb=<location and display parameters>&
syntax=<NQS or AQS(default)>
The query string can be any valid SQL or AQS search. For my application I wanted to query on the date my photo was taken which windows stores as “datetaken” and I wanted to query over a range of dates. Dates have to be in the YYYY-MM-DD format, and a range is specified with “..”.
I used the crumb specifier to target a just the “My Pictures” special folder. To specify a location you put crumb=location:<URL encoded path>. For a special folder you do crumb=location:shell%3a<folder name>.
I’ve completed a touch-table version of Castles of Burgundy. In the board game, players build up their estate with tiles drawn from a common area. Each turn, players roll two dice and use the results to pick tiles, place tiles or sell goods. Placed tiles give the player victory points, extra actions, or advantages in later turns. Each player manipulates their own estate and only interacts with the other players through competition for the tiles in the center.
We were interviewed by Distract-O-Vision at Conclave of Gamers this year. We talked about the games that we’ve been making and the basic ideas behind the touch table. They put together a great video that shows off the touch table and games.
I’ve completed a touch-table version of Concordia. We saw the game at Essen last year. They were promoting the Salsa expansion, but we weren’t familiar with the base game. The game has relatively simple rules but it takes many steps to achieve your goals.
The game was a good candidate for the touch table because is no hidden information, there is a decent amount of setup time and piece twiddling, and I felt like the game could be improved with a real-time scoreboard.
A couple of months ago I started a project to convert some card games for play on the touch table. I started this project because I wanted to convert the card game “Linko”, but I’d also been planning to convert “Turn the Tide”.
I’d done one card game (Wizard) in the Torque engine and I used the web interface to keep player’s card’s on their device. I wanted this implementation to be more generic and support multiple card games.
I planned to use Unity’s built in networking and have the server run on the touch table with an Android application that players would download to their phone to show their hand of cards.
When making my first networked game in Unity, I found a way to keep two copies of the same project open at once. Unity will usually only open the same project one time. In a networked application, this means that you either have to build the client or server application, then run as the other side within Unity. Not only is this a hassle, but you can only debug one side of the program at a time.
Being able to have the same project open with two Unity windows allowed me to develop much faster.
The key to having the project open twice is to have two project directories that point to the same source files. A Unity project has three sub-directories: Assets, Library and ProjectSettings. Everything the developer creates goes in Assets and Unity controls the other two directories. So, to have two Unity windows into the same project, you have to create two project directories that share the same Assets directory.
I did this in Windows 10 with Unity 5.3. I’d expect this to work for Windows 7+ and Unity 5.x.
Create your project in Unity. Get everything setup the way you want it. Exit Unity.
Copy the whole project directory: Use the GUI -OR- xcopy /e/h Game GameCopy
Delete the Assets sub-dir In the new project directory: Use the GUI -OR- del /s GameCopy/Assets
Link the original Asset directory to the new directory: (in an elevated command prompt) mklink /j GameCopy/Assets Game/Assets
Now you can bring up one Unit window on the Game project and another on the GameCopy project. Any asset changes (code, scenes, graphics, audio, prefab, etc) that you make in one Unity window will show up in the other Unity. The only thing that isn’t shared are project settings.
Remember that you don’t actually have two copies of your assets. Any changes/additions/deletions in one directory are done to both!
In Linux/Mac, I’d try a soft link first and see if that works. If that fails, make a hard link.