I've just had a random idea that I'd be keen to implement:
Driver Jobs
"3/40 driver jobs complete!"
The idea
Special cars parked in specific locations. When a player enters one of these cars, they are prompted with a message:
You have entered a driver job car. Would you like to attempt the driver mission? Yes/No
If they click No they are ejected from the car.
If they click Yes...
A checkpoint shows at a location that has previously been set and the countdown begins.
For example, a player enters a special Super GT parked near the casino. They must drive to Los Santos Airport in 120 seconds. They cannot exit the car.
If they do it, they pass the driver job.
This has the same concept as hidden packages: We create about 40 of these jobs. For every one a player passes, a message shows: "x out of 40 driver jobs complete!".
When a player finds all of the special cars and completes all of the driver jobs, they unlock a new command similar to /inf, but speaks for itself: /maverick.
Each individual job can have different levels of difficulty. This system can be nice and dynamic so that its easy to add new driver jobs.
It should be fun for players because they have to:
- Explore to find these special vehicles
- When they finally find one they have to actually complete the mission, unlike the spraytags
- Its addicting: If a player misses the deadline by a few seconds they're gunna keep trying.
- Its easy and fun to understand for new players.
The implementation
Whilst I'd like this to be nice and dynamic, I don't see the need to include the possibility for any run-time editing of the job like changing the route or so on. I'd like to keep this short and sweet so everything works as expected, nice and easy. On this basis I also don't see the need to store anything (relating to the job data) externally.
Whilst leaving options in for further improvement and expansion in the future, for now I only see the need for three classes:
Job - core class which maintains information relating to the state of the mission and attributes for controlling this. Contains information for the location of the completion point and time to complete it. Future expansion may include storing of best times but this will be omitted from the first version.
Vehicle - Subclass which stores information relating to the vehicle: State (in use? available?), (current) location. Any additional features that may be included such as distance to location meter could be included here. Again however, this will be omitted from the first version.
Player - Subclass which contains attributes for the player element that's taking part in the mission. Obviously given SA-MP's use of vehicles only one player can undertake a mission at any one time and this class needs to maintain this. Communication with the job class is obviously vital. It should also handle integration with the players account - each completed mission needs to be saved along with some stats such as times.
If I get some time tomorrow morning I'll draw a detailed class diagram.
Thoughts?
Driver Jobs
"3/40 driver jobs complete!"
The idea
Special cars parked in specific locations. When a player enters one of these cars, they are prompted with a message:
You have entered a driver job car. Would you like to attempt the driver mission? Yes/No
If they click No they are ejected from the car.
If they click Yes...
A checkpoint shows at a location that has previously been set and the countdown begins.
For example, a player enters a special Super GT parked near the casino. They must drive to Los Santos Airport in 120 seconds. They cannot exit the car.
If they do it, they pass the driver job.
This has the same concept as hidden packages: We create about 40 of these jobs. For every one a player passes, a message shows: "x out of 40 driver jobs complete!".
When a player finds all of the special cars and completes all of the driver jobs, they unlock a new command similar to /inf, but speaks for itself: /maverick.
Each individual job can have different levels of difficulty. This system can be nice and dynamic so that its easy to add new driver jobs.
It should be fun for players because they have to:
- Explore to find these special vehicles
- When they finally find one they have to actually complete the mission, unlike the spraytags
- Its addicting: If a player misses the deadline by a few seconds they're gunna keep trying.
- Its easy and fun to understand for new players.
The implementation
Whilst I'd like this to be nice and dynamic, I don't see the need to include the possibility for any run-time editing of the job like changing the route or so on. I'd like to keep this short and sweet so everything works as expected, nice and easy. On this basis I also don't see the need to store anything (relating to the job data) externally.
Whilst leaving options in for further improvement and expansion in the future, for now I only see the need for three classes:
Job - core class which maintains information relating to the state of the mission and attributes for controlling this. Contains information for the location of the completion point and time to complete it. Future expansion may include storing of best times but this will be omitted from the first version.
Vehicle - Subclass which stores information relating to the vehicle: State (in use? available?), (current) location. Any additional features that may be included such as distance to location meter could be included here. Again however, this will be omitted from the first version.
Player - Subclass which contains attributes for the player element that's taking part in the mission. Obviously given SA-MP's use of vehicles only one player can undertake a mission at any one time and this class needs to maintain this. Communication with the job class is obviously vital. It should also handle integration with the players account - each completed mission needs to be saved along with some stats such as times.
If I get some time tomorrow morning I'll draw a detailed class diagram.
Thoughts?