pd
24.12.2007, 12:00:40
Go into yourselves. Think about what modding (and I am referring to TS/RA2 modding here) will look like in exactly a year from today.
Some of you may think "RockPatch4" and "NPatch Santa Claus Edition" and "gufu's TS Patch", while others may not have any hope that tools like that contribute anything and that time will do its job and slowly make the community die out as people move on to work on modern titles.
I can almost assure you that none of these things are going to happen.
The TS engine has something with it that no other game has. The TS engine, after having been researched, was found to be a kind of RTS game maker, that allowed for simple modification of its workings.
It does not use any really compiled files (MIX files have quickly been broken), it does not rely on compiled scripts that only few could decompile and even fewer could understand.
The nature of being based on INI files has made the TS engine a target for many people to create their own twist in a game with ease.
And although by the time Renegade, Generals and lately even C&C3 have been released, this is the one feature of the engine that kept it alive and popular even today.
However, time is leaving its mark.
The attitude towards modding on the developer's side has changed entirely. While they formerly encrypted and compiled files so that nobody can steal content and modify the game, it is now a standard that a map editor is included, and newer games even bring their own SDK with them.
The TS engine is standing strong, which might be because of it's nature being a 2D game (and naturally, 2D games are easier to work with than 3D games).
Still, you see members leave and move on.
In the end, the set of possibilities is used out. If you do not come up with a total conversion, which has a huge lot of work involved, it has been done already and it is not special.
The motivation starting to work on a TC is not only limited by the amount of effort involved, but also by the question "Who am I doing this for?", seeing more and more people moving on and losing interest in this old TS engine.
Have executable modifications changed anything about this?
For a while, certainly. When the first version of my own product, the RockPatch, was released, the attention was exploding.
Suddenly, there was something new. Things that were said to be impossible became possible, modders who gave up on certain ideas suddenly felt a little bit of hope.
This hope lasted for a while, but the executable modifications took something away from modders that they loved most: total control over their own project.
Most people are not able to disassemble an executable, to understand what they see and to modify it to what they want, and can you blame them?
They completely rely on the developers for that matter, and there are only three people that have ever worked on these patches in the TS/RA2 community.
Quite frankly, three people can not live up to the expectations of a community which counts hundreds of people.
Everyone wants something else, the wishlists were filled to overflowing, the bug reports arrived in masses.
After all, all the exe modifications turned out useless, being heavily bugged and not giving people exactly what they want.
So, can we expect that in one year, nothing has changed? Will 2008 be a boring year for the TS/RA2 community?
Will we see "RockPatch4", "NPatch Holy Mary Edition Revision #1337" and another guy's TS patch?
I have, while developing RockPatch2, realized that there is nobody I am devleloping it for. Maybe 20 people have a major interest in it.
And, I do not know this, but maybe, these 20 people would have found RockPatch2 buggy and stopped using it as well.
After reading through the thread that I posted on DeeZire almost 3 years ago, announcing my first executable modification, I got an idea, immediately stopped RockPatch2 development and worked on realizing this new idea.
What if I told you that modding TS/RA2 will be changed forever some time next year?
My new project gives modders back their total control.
I have a working prototype of an application that allows for executing a specific procedure in an external module on demand.
That means, you create a DLL with an exported function and tell the application when to execute it.
The DLL name, the function name and the time to call it can be specified in what TS/RA2 modders love most: INI files.
Such a DLL can be coded up in C++ with ease.
Said application is not the only tool available. As soon as I finished it, I will start writing wrappers for C++, so that later, you can have something simple as "Unit->Kill( )" and it works.
How do you know the time when your function must be called? To be honest, this will be the hardest part to make easily understandable, but I already have an idea concerning that.
The goal is that those who know C++ and those who are willing to learn C++ can implement their very own features into the game (things like new SuperWeapons will be a piece of cake).
Those who do not know C++ can opt to use other people's work, and of course there will be a RockPatch2, just in a DLL.
Making advanced development publicly available is only one of the benefits of this idea.
The most important thing might be the possibilities. It can take you an hour to write a long function in assembly. That function often requires hours of planning and researching.
All that was then. Now you can easily add to the game.
Heck, if I am able to come up with good drawing wrappers it might be an easy enough job to make a SuperWeapon that launches a game of Tic Tac Toe on the screen.
If you win, the enemy receives heavy damage, if you lose, goodbye.
Just one of many possible ideas.
And that's still not all. This system is pretty easily portable to any executable.
IE, Tiberian Sun and even Red Alert 1 will probably not be forgotten.
Prepare for a huge change next year.
Merry Christmas!
-pd
Some of you may think "RockPatch4" and "NPatch Santa Claus Edition" and "gufu's TS Patch", while others may not have any hope that tools like that contribute anything and that time will do its job and slowly make the community die out as people move on to work on modern titles.
I can almost assure you that none of these things are going to happen.
The TS engine has something with it that no other game has. The TS engine, after having been researched, was found to be a kind of RTS game maker, that allowed for simple modification of its workings.
It does not use any really compiled files (MIX files have quickly been broken), it does not rely on compiled scripts that only few could decompile and even fewer could understand.
The nature of being based on INI files has made the TS engine a target for many people to create their own twist in a game with ease.
And although by the time Renegade, Generals and lately even C&C3 have been released, this is the one feature of the engine that kept it alive and popular even today.
However, time is leaving its mark.
The attitude towards modding on the developer's side has changed entirely. While they formerly encrypted and compiled files so that nobody can steal content and modify the game, it is now a standard that a map editor is included, and newer games even bring their own SDK with them.
The TS engine is standing strong, which might be because of it's nature being a 2D game (and naturally, 2D games are easier to work with than 3D games).
Still, you see members leave and move on.
In the end, the set of possibilities is used out. If you do not come up with a total conversion, which has a huge lot of work involved, it has been done already and it is not special.
The motivation starting to work on a TC is not only limited by the amount of effort involved, but also by the question "Who am I doing this for?", seeing more and more people moving on and losing interest in this old TS engine.
Have executable modifications changed anything about this?
For a while, certainly. When the first version of my own product, the RockPatch, was released, the attention was exploding.
Suddenly, there was something new. Things that were said to be impossible became possible, modders who gave up on certain ideas suddenly felt a little bit of hope.
This hope lasted for a while, but the executable modifications took something away from modders that they loved most: total control over their own project.
Most people are not able to disassemble an executable, to understand what they see and to modify it to what they want, and can you blame them?
They completely rely on the developers for that matter, and there are only three people that have ever worked on these patches in the TS/RA2 community.
Quite frankly, three people can not live up to the expectations of a community which counts hundreds of people.
Everyone wants something else, the wishlists were filled to overflowing, the bug reports arrived in masses.
After all, all the exe modifications turned out useless, being heavily bugged and not giving people exactly what they want.
So, can we expect that in one year, nothing has changed? Will 2008 be a boring year for the TS/RA2 community?
Will we see "RockPatch4", "NPatch Holy Mary Edition Revision #1337" and another guy's TS patch?
I have, while developing RockPatch2, realized that there is nobody I am devleloping it for. Maybe 20 people have a major interest in it.
And, I do not know this, but maybe, these 20 people would have found RockPatch2 buggy and stopped using it as well.
After reading through the thread that I posted on DeeZire almost 3 years ago, announcing my first executable modification, I got an idea, immediately stopped RockPatch2 development and worked on realizing this new idea.
What if I told you that modding TS/RA2 will be changed forever some time next year?
My new project gives modders back their total control.
I have a working prototype of an application that allows for executing a specific procedure in an external module on demand.
That means, you create a DLL with an exported function and tell the application when to execute it.
The DLL name, the function name and the time to call it can be specified in what TS/RA2 modders love most: INI files.
Such a DLL can be coded up in C++ with ease.
Said application is not the only tool available. As soon as I finished it, I will start writing wrappers for C++, so that later, you can have something simple as "Unit->Kill( )" and it works.
How do you know the time when your function must be called? To be honest, this will be the hardest part to make easily understandable, but I already have an idea concerning that.
The goal is that those who know C++ and those who are willing to learn C++ can implement their very own features into the game (things like new SuperWeapons will be a piece of cake).
Those who do not know C++ can opt to use other people's work, and of course there will be a RockPatch2, just in a DLL.
Making advanced development publicly available is only one of the benefits of this idea.
The most important thing might be the possibilities. It can take you an hour to write a long function in assembly. That function often requires hours of planning and researching.
All that was then. Now you can easily add to the game.
Heck, if I am able to come up with good drawing wrappers it might be an easy enough job to make a SuperWeapon that launches a game of Tic Tac Toe on the screen.
If you win, the enemy receives heavy damage, if you lose, goodbye.
Just one of many possible ideas.
And that's still not all. This system is pretty easily portable to any executable.
IE, Tiberian Sun and even Red Alert 1 will probably not be forgotten.
Prepare for a huge change next year.
Merry Christmas!
-pd
![[Image: jsfml.png]](http://jsfml.org/img/jsfml.png)