Alternative boot module
Posted: Tue Apr 10, 2012 3:36 pm
The current T-Engine boot module is very set up for ToME4, including the news feed, the online profile, the boot screen, the music and of course the background animation thing. When wanting to distribute modules packaged alone in the T-Engine there is a lot of fiddling needed to get something which isn't branded ToME4 everywhere, and which doesn't contain images and sound which can ruin the atmosphere of the independent module. See what I've done for Rogue Rage here as an example of how I've customised the boot module:
http://gruesomegames.com/roguerage-failure.zip (Windows only)
Much of this was done by trial and error commenting things out in the boot module's Game.lua, and replacing artwork in the engine.
It would be very helpful if an alternative boot module was available for module releasers. Telling people to separately download the T-Engine and the then place the module folder in directory x is not a nice way to release for a start. But more importantly the feel of the game is all wrong when the first thing you see is automated ToME4 gameplay and a load of text about ToME4. The alternative module would ideally have:
- Text about the T-Engine with reference to ToME (see the text I used in Rogue Rage)
- Profile linking turned off (with comments in the code for how to enable it)
- No news update
- Fancy mouse pointer turned off
- No animated background - just a plain image
- The image should be something plain saying "T-Engine", perhaps with some blank space on it that module makers can customise into their own splashscreen image
The image is an important thing, and to really fix it the engine needs changing to have the load screen made part of the module rather than part of the engine. Currently (AFAIK) there's no way for a module to override the booby load image - one has to go into the engine files and replace it. The splashscreen is part of the boot module but the load screen is locked into the engine. Same for the "ToME4" logo that appears in the top-left (another inappropriate logo when playing a different game - a "T-Engine" logo would be far more appropriate).
There are possibly some other things that niggle people, but these are what I find to be the most in need of fixing. The T-Engine is obviously very set up around ToME4, but it would be nice to have a bit more independence when releasing an entirely separate game. And it would make sense for all module developers to have access to the same T-Engine boot screen.
http://gruesomegames.com/roguerage-failure.zip (Windows only)
Much of this was done by trial and error commenting things out in the boot module's Game.lua, and replacing artwork in the engine.
It would be very helpful if an alternative boot module was available for module releasers. Telling people to separately download the T-Engine and the then place the module folder in directory x is not a nice way to release for a start. But more importantly the feel of the game is all wrong when the first thing you see is automated ToME4 gameplay and a load of text about ToME4. The alternative module would ideally have:
- Text about the T-Engine with reference to ToME (see the text I used in Rogue Rage)
- Profile linking turned off (with comments in the code for how to enable it)
- No news update
- Fancy mouse pointer turned off
- No animated background - just a plain image
- The image should be something plain saying "T-Engine", perhaps with some blank space on it that module makers can customise into their own splashscreen image
The image is an important thing, and to really fix it the engine needs changing to have the load screen made part of the module rather than part of the engine. Currently (AFAIK) there's no way for a module to override the booby load image - one has to go into the engine files and replace it. The splashscreen is part of the boot module but the load screen is locked into the engine. Same for the "ToME4" logo that appears in the top-left (another inappropriate logo when playing a different game - a "T-Engine" logo would be far more appropriate).
There are possibly some other things that niggle people, but these are what I find to be the most in need of fixing. The T-Engine is obviously very set up around ToME4, but it would be nice to have a bit more independence when releasing an entirely separate game. And it would make sense for all module developers to have access to the same T-Engine boot screen.