This time you’ve got me to help you…

A few months back I received an email from Marmalade Studios. Marmalade is the system I used to give me cross platform support. I pay for a licence yearly which is still covered by the ongoing sales on the long tale of the game. Anyway, the email informed me that Marmalade were pulling out of the Tools business to focus on their own development. They laid out a timetable and final release plan for the current tools but ultimately from March 2017 they will no longer be supporting their toolset. There was an offer to purchase rights to the source code, but as a small indie, that’s not really an option.

This doesn’t affect the current releases, but what it does mean is that any chances of me producing updates in the future have almost certainly been removed. And with every new OS release, the chance of the game not working are increased.

I know I have not been prolific with updates since the release of Doomdark’s Revenge settled. There was so many things I wanted to do, but just haven’t gotten around to. The reality is two fold, as amazing as the sales of the games have been, they are obviously not enough to support me full time, and secondly, the games were written quite frantically in the end and I never regained that sense of purpose after their release; this is not just for these games but for everything that I have been doing creatively.

I’ve been trying recently to tie up another release. The main reason for this is to produce a build with the latest version of Marmalade and get it out there to properly support the latest devices. In theory a new release should keep its visibility in the App Stores for a few more years. As part of this I’ve been slowing adding a couple of features: Discovery Mode, Difficulty Modes, Rationalise the code base between DDR and LOM. etc..

So with all this in mind I have been toying with the following: Uploading the source code to GitHub and making it open-source with the objective of transferring it to another cross platform solution, Cocos2d-x for example. Or, allowing people to port the engine to any other coding languages they like, so it could be used however they like.

The current codebase is written in c++, and thus moving to Cocos2d-x makes sense, but I quite like the idea of porting to c# or swift.

Moving to open source could also allow for the tool chain to be fully developed which would allow for more work to be put into ongoing development of the games.

Anyway, I shall think on this more, but if anyone is interested in getting involved, then drop me a note…

 

 

Related Posts:

No ice, no storm, no sword or shaft shall keep me from thy side

ddr_google_feature_graphic_1024x500

Just in case you missed it… Doomdark’s Revenge is out on all formats.

Related Posts:

We ride to tear the Frozen Empire asunder!

doomdark_site_indexAfter hastily announcing that I will be releasing Doomdark’s Revenge on the 7th I can now confirm that the actual release date will be the Monday 17th Feb.

The main reason for this change is purely logistics. I have to get the website ready to go, PR and Press Packs, Screenshots, Video, submit all versions, and create the store for direct selling.

However, the other reason that I hadn’t taken into account until thinking about submission congestion, is that, during the week of the 17th, it would have been Mike Singleton’s 63rd birthday. So it feels appropriate.

The iOS version is ready to go, and I intend to submit to Apple tonight. Apple usually take 7 days to approve a new submission. If there are any problems, then I would likely miss the 7th. The real area of concern is that from Feb 1st, Apple are insisting that all submissions are done using XCode5 and target iOS7 as the build SDK. In theory this shouldn’t be a problem, however in order to guaranty this, I need to build with the latest version of the Marmalade SDK 7.1.1 and as this version is only BETA at the moment I have slight concerns. I am currently not able to submit to MAC Appstore because of a Marmalade issue, and that affects my confidence in it.

The Android version appears to be ready. The first initial sweep has been done and a few small visual bugs stamped out. The game UI now seems stable across resolutions so I would suspect that supported devices will be the same as with The Lords of Midnight. I don’t foresee any issues moving forward. The turn around time on Google Play is such that I still have plenty of time to fix anything that crops up.

I have done a Blackberry build, and it all seems to be running in the simulator without issue. I need to perform an actual device test but again I don’t foresee any issues. There were some initial problems with the Q10 720×720 resolution but they have been ironed out. BTW: this version will allow the Q10 to rotate and I will include this fix in The Lords of Midnight ASAP.

Samsung and Amazon builds are just packaging. So again, I don’t foresee any issues.

Windows and OSX builds should be good, as this is how I develop. I expect to hand over a master to Fastspring and GoG.com early next week.

The only issue with the OSX version is that it is unlikely to be available in the MAC Appstore for a while. This is due to the aforementioned issue with the Marmalade SDK and OSX Mavericks. If the issue is not fixed soon, and I have a window of opportunity before the 17th ( preferably by the 10th ), I will install an OSX Mountain Lion machine and attempt to build the app. The OSX version will however be available direct or through GoG.com, where I don’t need to release a signed app.

Once the release is out there, I intend to revisit Windows Phone 8 version of both Doomdark’s Revenge and The Lords of Midnight.

Related Posts:

Version 1.11

lom_advert_for_mobilesI finally managed to push out the update to Lords of Midnight. All platforms have been updated to 1.11

This is the first time that all platforms have shared the same code base, and it’s the first time I have updated all platforms on the same day. It’s quite a big day as I’ve been trying to get this update out for a while, and I feel this marks the proper hand over to Doomdark’s Revenge. So, I really hope I haven’t missed something massive somewhere!

This will likely be the last update this year, unless of course I’ve messed something up. For the next 6 months I suspect all my focus will be on Doomdark’s Revenge. Not only getting it released, but those first few updates that will happen to it early next year after the initial release.

I full list of changes can be found here….

But I thought I might pickup and summarise a few of the items.

Big change was adding new grouping controls. You can now scroll around lords that are grouped making it easier to select lords from the select screen when they are grouped. You can also merge groups, disband with one click, change the leader of the group, and drag a lord from one group to another. You can also disband a group or leave a group from the think screen. Video of it working here…

There is more keyboard support on screens. This is for the desktop version and hopefully Android where it has keyboard support.

Mouse wheel support is there for the desktop version.

The scaling on the map is now available to the mobile versions. You can scale with pinch and spread, but I have also left in the scaling gadget on the mobile versions too.

Selecting lords on the Map screen has had a little work. You can now select the multiple lord icon in order to gain access to all the lords.

For iOS I have added an option to toggle between an ebook novella and pdf novella. I hadn’t considered that people might not have iBooks installed. But I have also added ebook support to the OSX version now that Mavericks is shipping with iBooks.

Two biggies that will make a difference to the game. You can no longer select a lord from the map screen when Luxor is dead and Morkin does not have the Moon Ring. This was a bug that would have allowed you to still control your lords even though you didn’t have the Moon Ring – sorry that exploit has now been plugged!

lom_advert_for_desktopsAnd, armies were fighting double at night. Which means battles would have been quicker than they should have been because double damage was being dealt out. This would have meant that you could have lost a fight without the chance of escaping, because you should have had a turn between the two battles. Or the armies on both sides are unable to get reinforcements between the two battles.

I hope you enjoy…

Related Posts:

Update

dragonI thought I’d post an update of where things are at, at the moment.

I’ve been having a bad run of “can’t be arsed”, this is not just on the Midnight front, but with a number of things. It happens now and then. I think part of this is due to the fact that from October I worked tirelessly on Lords of Midnight right up to release, and then followed the release with two months of updates. In the end, I think it burnt me out a little. That combined with the day job and that I work for some of my clients in the evening as well. The problem is that I have now lost a little bit of momentum and I just need to get that back…

The desktop version is almost ready. I hoped to put it into test a few weeks ago, but didn’t because I was waiting to add one more feature, which is the MAP scaling and movement gadget. I did the temporary graphics, but haven’t implemented it yet. Once that is in I will make a request of Jure for the final graphics and then upload for test and open the forum for testers.

I intend to formally request Jure start work on Doomdark’s Revenge at the start of May, so that is my new goal; I’m going to aim to have the desktop version in test and DR started by the 1st May. And then aim for DR to be ready for at least the Mac App Store  by the end of May.

 

Related Posts:

This is a gift beyond gifts…

ms62

To celebrate what would have been Mike Singleton’s 62nd birthday later this week, The Lords of Midnight will be reduced to half price on all available stores for the whole of this week starting Monday 18th February…

Related Posts:

Is it any less hopeful than defending the Plains of Blood?

lom_map
Last night I submitted a new version to the Apple App Store. The review process usually takes a week. So hopefully release 1.06 will be ready for Monday 18th.
Unfortunately during my device testing, I found a problem with one of the new features, and made an 11th hour decision to drop it from this release. The feature in question was the Map Pinch and Zoom. The problem was that not all the graphic elements were scaling correctly and during the zoom the focus point of the map was changing. The end result was that it was a little messy and I wasn’t happy letting it out. An evening of work will see the problem fixed, but to do that would mean delaying this release, and I’m painfully aware that the slow down problem needs resolving. So I decided to pull the feature. I know it would be have easy to just delay the release, but I need a working version ready and available on the 18th…

Thankfully, the Android version doesn’t need to be submitted until the end of the week, so I will make the changes and hopefully have the Android version ship with the feature. As long as testing this week proves everything to be working correctly, I will submit another Apple version with just this new feature as soon as possible.

I will upload the current version to the test servers tonight, as I would like it to take a good test pounding this week.

After this month release schedules will be slowed down, and I will go back to utilising the test process more fully!

Related Posts:

Next set of features…

dragon_redI have identified the new features that will be in the next version.

Next version should bring Android, iOS, Playbook, and BB10 all into sync.

 

 

The features are…

1. Change Swipe up on look screen for showing map to be two finger swipe.
2. Add two finger swipe down on map screen to return to look.
3. Save game Meta Data for identifying stories – “Day 5 – Luxor – Tower of the Moon”
4. Option – Auto Unhide on move, or prompt
5. Option – Auto fight critters on move, or prompt
6. Option – Show movement indicator, On/Off
7. Hold down on main screen for compass, and then choose direction to look.
8. Tweak button sizes for small devices
9. Fix undo storage!
10. Tighten hit box on shield.
11. Fix stray line on certain images ( Android )
12. Fix Select screen shields being under Look Icon.
13. Option – Screen Transitions off

Related Posts:

To pay or not to pay….

After uploading an update to the Android store at 1am last night, and then waking at 7am to see a tweet showing the location of the cracked version of said upload. It made me think about the issue of piracy.

Now I don’t think that £2.99 is too much to ask for an app, but some do. I’ve seen many comments since the release of the iOS version stating the the price was steep. I understand that nowadays some people might find it a high price to punt on a game, despite the large number of high rating reviews for the game. And I do need to find a way to allow people to experience the game for the first time. Now I don’t like the idea of Ad backed games, it’s not really a direction I want to follow. I also don’t want to reduce the price of the game. I think £2.99 is more than fair and reasonable, despite the prices of Apps in general.

I was thinking about doing a price promotion in Feb, around Mike’s birthday. But I was also thinking about releasing a Lite version. However, part of me is thinking about releasing a Free version.

The idea being, Free version and Paid version. Free version just has a nag screen pointing at the Paid version, and the free version will not get updates and new features. I’m kind of thinking almost like an honesty box version. You like it you buy it. But if you don’t buy it you miss out on any new features I add in the future. I’m sure others have tried this to varying success. But if anyone can cite some examples, that would be great.

I did wonder a little about should I remove a few items from the original free version, like. Remove a couple of the ways of destroying the ice-crown, or remove the quest entirely. Remove the grouping functionality. Remove the last undo. Remove the multiple stories. Should I remove more from a Lite version? Restrict the number of game days you can play it?

Anyway, thoughts…

Related Posts:

Getting up and running…

It seems a little strange, that after all this time, something might just finally become of this project! 🙂

The first stage was to get the Midnight Engine up and running under iOS. Well I tried that about 3 years ago without any major success. However, it’s a little more important now. So I downloaded the Airplay SDK which Mike and I had decided to evaluate, and started porting the engine.

It was a pain! Differences in compilers, changes in the language, blah blah blah… it took a couple of days of monotonous work before I had a project that loaded the TME data in. While I was working on that, Mike was playing around with some graphic ideas that we had talked about implementing – mainly to do with lighting.

Continue reading

Related Posts: