This topic is about the future of our development. The last 6 months we’ve been working on 2.90, and we started working on 2.91, but we must go on. We must start thinking about 3.0, what will it be, how do we decide which features we want with what priority, when should we set milestones. All that stuff can be discussed here.
As you might already know, Badeend started working on a Pre-Compiler branch, which is basicly a new LVP version, using the pre-compiler. The pre-compiler gives many advantages over the compiler we use now, so it is a huge step switching to that, but it is probably the best one. So, what do we do?
In the next few weeks we need to continue working on 2.91, we want a cool update to be ready when SA-MP 0.3 gets released. We can add some new features into 2.91, that use the new 0.3 features. We can add some cool new handlers, and try to fix some more bugs that we find. We must not forget though, that 2.91 will also need some optimization, the current code is not quick enough. Some things that could help speed things up have already been suggested by Jay here. These things have to be done in the next week.
However, we need to move on, the 2.x codebase is a mess, the code’s not organized, there’s double code, and a lot of useless code and variables. That is why we should work on a the Las Venturas Playground Community 3.0 version. This version will be a huge update from 2.x, it includes a massive rewrite of much code, it has new possibilities for us using the pre-compiler, and it will be a fresh and clean start.
Another thing we would like to introduce together with 3.0, is an open-source codebase. The SVN repository will be read-only for the public. Players can check out the code, but will not be able to commit or run the code, which we will prevent by the code requiring some sort of plugin to run. People that are interested in writing code for Las Venturas Playground, but that don’t want to be in the development team, or that we don’t want in, can however write patches. These can be created by Tortoise SVN, which will generate a .patch file. This file can be sent to use, reviewed and tested, then we can decide whether or not we want this specific feature in our gamemode.
So, how do we work on this? How do we involve players in the development, after all, we want the players to see it a huge fantastic update too. I would like everyone’s reaction in this topic as soon as possible, post all your ideas, comments and reactions, so we can work more on it.
The Las Venturas Playground Lead Developers
As you might already know, Badeend started working on a Pre-Compiler branch, which is basicly a new LVP version, using the pre-compiler. The pre-compiler gives many advantages over the compiler we use now, so it is a huge step switching to that, but it is probably the best one. So, what do we do?
In the next few weeks we need to continue working on 2.91, we want a cool update to be ready when SA-MP 0.3 gets released. We can add some new features into 2.91, that use the new 0.3 features. We can add some cool new handlers, and try to fix some more bugs that we find. We must not forget though, that 2.91 will also need some optimization, the current code is not quick enough. Some things that could help speed things up have already been suggested by Jay here. These things have to be done in the next week.
However, we need to move on, the 2.x codebase is a mess, the code’s not organized, there’s double code, and a lot of useless code and variables. That is why we should work on a the Las Venturas Playground Community 3.0 version. This version will be a huge update from 2.x, it includes a massive rewrite of much code, it has new possibilities for us using the pre-compiler, and it will be a fresh and clean start.
Another thing we would like to introduce together with 3.0, is an open-source codebase. The SVN repository will be read-only for the public. Players can check out the code, but will not be able to commit or run the code, which we will prevent by the code requiring some sort of plugin to run. People that are interested in writing code for Las Venturas Playground, but that don’t want to be in the development team, or that we don’t want in, can however write patches. These can be created by Tortoise SVN, which will generate a .patch file. This file can be sent to use, reviewed and tested, then we can decide whether or not we want this specific feature in our gamemode.
So, how do we work on this? How do we involve players in the development, after all, we want the players to see it a huge fantastic update too. I would like everyone’s reaction in this topic as soon as possible, post all your ideas, comments and reactions, so we can work more on it.
The Las Venturas Playground Lead Developers
