24.03.2016, 11:27
I had written a small "/work" command with preset data to test the traindriver code for transporting passengers in a never-ending route.
This command has now been rewritten to actually gather the required data based on class, vehicle and level of the player.
By doing so, the Busdriver class became functional as well because it has the same jobtype: transporting passengers on a never-ending route.
I added some test-data to test it and it works perfectly, without changing anything in the actual job processing code.
The job-code for traindriver was written in a way so it uses actual data and is not class-restricted.
In fact, any class would be able to use that same code, as long as the route is defined as a passenger-traject routetype.
When using the "/work" command, it gathers all cargo types that can be transported in the player's vehicle.
Cargo is restricted to a certain class and level-range and has a certain cargo-category.
Also, every vehicle holds some flags which indicate which cargo-categories that vehicle can transport.
These flags are just bits merged into an integer, so any vehicle can basically be assigned 32 cargo-categories which it can transport.
There won't be that much categories defined though.
By using all that data together, it's easy to create a query to get the cargo-types that are valid for the player.
When there is no cargo found, you're informed about it.
You don't have the proper level, vehicle or class to run a job (traindriver using a taxi for example).
When only 1 cargo type is found, it's selected automatically.
When multiple cargo types are found, you're shown a list of cargo-types and you can choose one.
This list also shows the buying price for the cargo, profit and experience points for each cargo-type.
These values are per unit of that cargo-type.
If your vehicle can hold 100 of those units, you can multiply these values by 100 as well to get the total cost, profit and experience for any route with that cargo.
So it's best to choose a route that's as short as possible because profit isn't based on distance anymore like in V1.
Driving from A to B over a distance of 200 meters will earn you the same profit as transporting the same cargo over a distance of 5000 meters.
This is done because V2 will have route-types where you have to pickup your cargo at several locations and deliver your cargo at several locations and it would be very difficult (if not impossible) to calculate distances between loading point and unloading point.
Upon choosing (or auto-selecting) a cargo-type, a list of routes is created.
When there is no route, then the data isn't properly in place and you're informed to contact an admin about the problem.
When 1 route is found, it's chosen automatically.
When multiple routes are found, you're also shown a list of routes and you can choose one.
For now, only 1 route-type is defined (passenger-traject) so it can only start one type of job.
For passenger-traject routes, you won't get to choose a location and the route is started immediately.
For other route-types (like truckers transporting cargo from A to B), you will be shown a list of pickup and delivery locations as well.
That code isn't ready yet as the route-type hasn't been written yet as well.
But it should also be possible to define a passenger-traject routetype for pilots as well (using large planes) and when the data is inserted into the database, the pilot class could also be functional already.
I have no video about multiple funtional classes yet, since it's only some stupid test-data that's defined.
The video about the traindriver class is valid since that route (stopping at every trainstation) will actually be in the finished V2.
I'll try to define some proper routes later this week and upload new videos showing busdriver and pilot classes working already.
This command has now been rewritten to actually gather the required data based on class, vehicle and level of the player.
By doing so, the Busdriver class became functional as well because it has the same jobtype: transporting passengers on a never-ending route.
I added some test-data to test it and it works perfectly, without changing anything in the actual job processing code.
The job-code for traindriver was written in a way so it uses actual data and is not class-restricted.
In fact, any class would be able to use that same code, as long as the route is defined as a passenger-traject routetype.
When using the "/work" command, it gathers all cargo types that can be transported in the player's vehicle.
Cargo is restricted to a certain class and level-range and has a certain cargo-category.
Also, every vehicle holds some flags which indicate which cargo-categories that vehicle can transport.
These flags are just bits merged into an integer, so any vehicle can basically be assigned 32 cargo-categories which it can transport.
There won't be that much categories defined though.
By using all that data together, it's easy to create a query to get the cargo-types that are valid for the player.
When there is no cargo found, you're informed about it.
You don't have the proper level, vehicle or class to run a job (traindriver using a taxi for example).
When only 1 cargo type is found, it's selected automatically.
When multiple cargo types are found, you're shown a list of cargo-types and you can choose one.
This list also shows the buying price for the cargo, profit and experience points for each cargo-type.
These values are per unit of that cargo-type.
If your vehicle can hold 100 of those units, you can multiply these values by 100 as well to get the total cost, profit and experience for any route with that cargo.
So it's best to choose a route that's as short as possible because profit isn't based on distance anymore like in V1.
Driving from A to B over a distance of 200 meters will earn you the same profit as transporting the same cargo over a distance of 5000 meters.
This is done because V2 will have route-types where you have to pickup your cargo at several locations and deliver your cargo at several locations and it would be very difficult (if not impossible) to calculate distances between loading point and unloading point.
Upon choosing (or auto-selecting) a cargo-type, a list of routes is created.
When there is no route, then the data isn't properly in place and you're informed to contact an admin about the problem.
When 1 route is found, it's chosen automatically.
When multiple routes are found, you're also shown a list of routes and you can choose one.
For now, only 1 route-type is defined (passenger-traject) so it can only start one type of job.
For passenger-traject routes, you won't get to choose a location and the route is started immediately.
For other route-types (like truckers transporting cargo from A to B), you will be shown a list of pickup and delivery locations as well.
That code isn't ready yet as the route-type hasn't been written yet as well.
But it should also be possible to define a passenger-traject routetype for pilots as well (using large planes) and when the data is inserted into the database, the pilot class could also be functional already.
I have no video about multiple funtional classes yet, since it's only some stupid test-data that's defined.
The video about the traindriver class is valid since that route (stopping at every trainstation) will actually be in the finished V2.
I'll try to define some proper routes later this week and upload new videos showing busdriver and pilot classes working already.