It would be nice if we started to sort out the skin database. Hawk did an amazing job keeping all the paints together but now that modding is starting to get shape and we`re going to see more bikes, we need to organize it just that little bit better to keep everything in control.
I suggest making a folder for each bike we have and put the skins in the correct bike folder. I`m seeing 500cc, RSV4 & GP8 skins in the 1000cc folder. If someone would download everything as 1 whole .zip file and put it in his murusama paint folder, alot of skins wouldn`t match and show up incorrectly. Putting the wrong skins in the wrong folder happened in our shared dropbox folder and it was a pain(t) in the ass trying to pick out which paints showed up faulty because noone cared to name them correctly aswell.
This brings me to my other point..name templates. Right now everyone is naming their skins however they want, but it make alot of difference if we started to use a fixed template for paint names.
What the best way is is something that`s up for discussion, but we need something clear like RTH R6 - JamoZ #14. RTH is my team, R6 is the bike the skin is for, JamoZ is my nick & 14 is my race number. This way you keep everything tidy and there are no more skins named like : carbon, yellow, #25 etc etc.
Hope my rambling makes sense, but i want to keep everything in order ;)
+1
order like Nick_Number_Team_Bike looks more farsightedly for me (i mean naming from more potentialy permanent value to less permanent)
Totally agree on the principle. It should also be applied to bikes, helmets models, helmets paints and tracks.
Quote from: Reactive on December 27, 2013, 10:01:59 AM
order like Nick_Number_Team_Bike looks more farsightedly for me (i mean naming from more potentialy permanent value to less permanent)
I'm for the opposite, as the most important thing is the bike the paint is for.
Team is not really useful, there will not be plenty of teams.
What I'd do:
- Tracks: NAME_YEAR_VERSION as in Monza_2010_v1.1. Maybe it's a good idea to add the author too.
- Bikes: MAKE_MODEL_YEAR_VERSION as in Yamaha_R6_2011_v1.2. If we ever manage to sort out different categories (not easy) the the category could be prefixed (i.e. before the MAKE), like SBK_Yamaha_R6_2011_v1.2
- Paints: to be absolutely clear, the name should include the entire bike name (eventually except the version number), plus the paint name. However if the paint db was kept with the same directory structure as the one needed by gpb (eg. Bikes/SBK_Yamaha_R6_2011_v1.2/paints), then everything would be very clear without the need for a very long paint name.
MaX.
How are we going to do this with all the current bike paints? Someone needs to start renaming them, and people need to start from scratch again downloading all the paints. If we divide it over 2 or 3 people it`s doable. The sooner this gets standardized, the more work and frustration it will save us in the end. If needed i volunteer to do a part of the paints. But first we need to agree on a template. And in the end if a paint is not named properly, it will not be included in the paints library, easy as that :D
I think that is a brilliant solution to what has become like a crazy maze and that's no disrespect to the ones who take time to organise the files.
Quote from: HornetMaX on December 27, 2013, 01:16:19 PM
- Tracks: NAME_YEAR_VERSION as in Monza_2010_v1.1. Maybe it's a good idea to add the author too.
- Bikes: MAKE_MODEL_YEAR_VERSION as in Yamaha_R6_2011_v1.2. If we ever manage to sort out different categories (not easy) the the category could be prefixed (i.e. before the MAKE), like SBK_Yamaha_R6_2011_v1.2
- Paints: to be absolutely clear, the name should include the entire bike name (eventually except the version number), plus the paint name. However if the paint db was kept with the same directory structure as the one needed by gpb (eg. Bikes/SBK_Yamaha_R6_2011_v1.2/paints), then everything would be very clear without the need for a very long paint name.
Agree
Quote from: JamoZ on December 27, 2013, 01:32:32 PM
And in the end if a paint is not named properly, it will not be included in the paints library, easy as that :D
Agreed.
I think a good idea is to start with the 125 paints, just to practice before doing the tough stuff.
MaX.
I agree with what everyone here is saying, I'm quite happy to continue working with dibu to keep the online server track downloads database organized, but, yes, I could do with someone else taking over organizing the paints files(MOD Bike and default Bike paints) and Mod bike databases, as it's too much for one person. I started it because it needed doing and know one else seemed interested at the time.
How long will it be till you guys create this new database?
Anyway. I'll keep the current skins/mods database download thread up till you guys have got yourselves organized, but I won't be continuing to update it.
As soon as you publish your new skins/mods database I will delete my forum thread ;)
This new database your talking about organizing should be great! Good Luck Guys! ;D 8)
Why not just start afresh by publishing a sticky thread for the standardised paint file format rules, and then requesting everyone who has paint files to submit those files again in the new standardised file format required. This will save a lot of work, and only then require the files to be uploaded to the database into their correct folders.
As far as the file name format is concerned, I think you must have the name of the author in the filename(Preferably abbreviated), as confusion could rain when you get two paint files from different authors for the same bike paint scheme; for quality reasons some may prefer one to the other but both could be worthy of including in the database. I feel the same should go for the MOD bike database files too.
There is some good ideas here for organising this database, but is anyone here willing to actually get this up and running?
PS: I would also suggest that the "Paint" section of the forum be wiped clean for the fresh start, too. :)
@ Max and or Ricco, please feel free to remove all the Skin Threads I have posted in the Paints Section of the forum. I will consolidate all Skins
to one thread.
Thanks guys and sorry for the hoarding. ;D
(http://imageshack.us/a/img843/3783/hbti.jpg)
Maybe we can later catagorize the skins into Fantasy/Factory/GBP Team skins? If someone would be willing to setup a template/scheme for this i wouldn`t mind doing the renaming.
I found these old 125 & 500 paints on my hard drive Jamoz
you may want to check them to see if you have them
125 https://mega.co.nz/#F!p01GXAgC!FSY4Sh001lpa3gXULhecTA
500 https://mega.co.nz/#F!YxViFKKS!EbYp6F3ZkCQeeVuMEGZNLQ
I was thinking about doing the paint system in a different way. I want to include them into the bike mod. Eventually everyone will want to have that bike mod, and they are already complete folders. I can just gather all the paints, rename them and put them in the correct bike folder. This way there never is any confusion about which paint belongs to which bike and everything is already organized into categories. Of course i will provide a seperate paint folders with all the paints organized, but i think this could be one way of keeping everything centralized and organized. What are your thought about this?
Highly impossible as soon as you have enough GPB players with personal paints.
MaX.
hello
i'm remeber at first time any of you make a automatic update paints.
Why not speak to Piboso and use for update automatic paints, tracks, and bikes.
With tha's all people have the same game and same options (and good update for all)
I like the idea with a bit of tweaking here and there when your up and running should be good.
I would love to see a full set of Motogp/WSB skins and bikes, this may be a good way to get the mod community heading in one direction instead of trying to make every type of bike.
Quote from: JamoZ on January 03, 2014, 10:35:43 PM
I was thinking about doing the paint system in a different way. I want to include them into the bike mod. Eventually everyone will want to have that bike mod, and they are already complete folders. I can just gather all the paints, rename them and put them in the correct bike folder. This way there never is any confusion about which paint belongs to which bike and everything is already organized into categories. Of course i will provide a seperate paint folders with all the paints organized, but i think this could be one way of keeping everything centralized and organized. What are your thought about this?
Hi JamoZ.
A good idea in theory, but do you intend to supply all the current and future default bikes paints too? After all, the main point of providing a paints database is so that riders have access to all the currently available rider paint schemes, wether they are personal paints or paints of MotoGP/GP500 stars past and present, so that anyone who is online can see other riders paint schemes.
Being able to download any or all paints from one place will encourage riders to install all paints from the database to help achieve this goal of being able to see any other riders paint scheme they decide to use while riding online.
Seems to me that whatever you decide to do, you will still have to create a database structure for all paints catergorised into their class folders for the default bikes(ie, 1000cc/500cc, etc. etc), and then a folder for MOD Bikes Paints, but this time with sub folders for each individual MOD bike created.
But I believe your hardest task will be to get authors to not only inform you about a new paint, but to save the paint file in a named-format that allows you to easily place that file into it's correct category. This is the problem I had, and I had to continually ask people which class their file belonged to. I also asked the community to let me know if any paints were in incorrect folders so I could correct the placement error; no one ever did let me know of one paint placement error. In fact only one person posted to let me know of a newer version of a couple of MOD Bikes that were in the Mod Bike database, and that was "_oDi_".
So I think however you do this new paint database, your going to have to except that your going to have to do quite a lot of administration to keep things bang up to date, as it needs to always be if your going to get the communities trust in knowing that this paint database is the one to use if they want a paint for their bike.
Just some food for thought, as they say ;) :)
I think every user should care about his own paints (personal ones), if the paint is not well named or has not info about the bike it belongs, just reject it.
We can have a sticky post of howto name them (when we decide the best way), if the paint is rejected , redirect them to the howto post.
Maybe a .rar file with the paint and a .txt file with the info, should be submitted to the organization responsible person.
I was thinking about having one single thread were everyone just posts his paint in a pre made template. That way we won`t get 200 threads for a single paint, and if done properly everything is alot easier to go trough and to keep it up to date.
I was thinking about something like this (other idea`s are welcome) :
Bike : Yamaha R6
Class : Supersport
Paint : RTH R6 - JamoZ #14 (also up for discussion)
Link : downloadlink (http://downloadlink)
And then a small screenshot showing the paint.
Paint names would have to at least include the model (M1/RSV4/CBR etc), the rider (Valentino Rossi or Warlock) and possibly the number (like #46 or #13) or year the paint is made of (Ex : M1 - Valentino Rossi 2009)
People who post paints that are not setup properly using the template & name are asked to change it so the thread keeps organized. Also i would like to see that a thread like this is being kept comment free like "good job!" or "great work" or any other kind of discussion regarding the posted paints. For this we could setup a painting thread where everyone can discuss paints, techniques, requests or show off work in progress paints. Right now the painting thread is becoming just as messy as on the old forum.
A thread like this would mean that it`s alot easier for me to pickup all the newly posted paints and put them in all the pre made bike folder. This way i don`t have to organize everything and we dont have to setup a database because everything is first posted here on the forum. I was thinking about updating the whole mod package weekly with paints, or whenever a new version of a mod is coming out.
Example : Right now we have all the bikes centralized into one mod package and database. If a new version of the R6 is coming out, i will update this as usual, but this time include all the new R6 paints that have been posted in the paintst thread. I can easily see which are new due to the date posted and i don`t have to wade trough alot of weird paint names wondering which are R6 paints.
The bottom line is, everyone who is up to date with the bike mod, will be up to date with the paint thread....
It`s just a matter of starting over and willing to take that step. Like i said, i`m willing to rename the current paints we have, but i can`t do this alone..
Quote from: JamoZ on January 06, 2014, 07:13:42 PM
The bottom line is, everyone who is up to date with the bike mod, will be up to date with the paint thread....
This basically is the ideal situation. I guess most people are not going to install (ALL) seperate paints all the time since for some it might not seem like an added value to do so. As said before, the main objective of a centralised system is that everybody can see your personal paint, so the less beautiful have to be installed as well.
The way to do it in my opinion is:
- Have a
locked and
pinned topic in the paints section explaining the procedure, naming convention and to whom it should be send to. The administrator(s) should check the naming and maybe even the design. If something is wrong a message is send back to the creator stating the needed changes.
- If all is ok the paint is added to the bikemod's next release and is thereby distributed to all players downloading the mod.
- The already existing paints have to be renamed first to comply with the naming convention, deleting not used or irrelevant paints in the process.
- If someone wants to update their personal paint, they just send it in again and the old version is overwritten.
- Since there are two types of paints, personal and general use (replica, fictional etc.) i propose we should have a naming convention for each. To keep it as clear as possible, the name should be as short as possible. Since each paint will be placed in the correct bike folder, stating the bike's name in the paint seems unnecessary. Since i think we should pose a limit of 1 personal paint per rider per bike (to limit the size of the database) version numbers will be irrelevant as well.
The naming would then look something like this:
For personal paints: NUMBER_NAME_TEAM (Since not everybody has a team it should be the last one)
For general paints: NAME_NUMBER_ADDITIONAL (Since all general paints have at least a name it should come first, this also sets it aside from personal paints in the selection menu since all paints starting with numbers are personal ones. Aside from this it makes it easy to find your own paint and for others it is clear which numbers have been taken. Not all general paints have numbers so this should come second. If there is a conflicting version of the same paint from different creators, the ADDITIONAL can be used to uniquely identify them).
The only problem is with the database becoming too big if the number of people playing GP bikes increases a lot. We would then have to provide the paints seperately from the bikemod.
P.S. Since piboso mentioned all paints will become corrupt when version 1.0 is released, we maybe should wait with putting in the work now
Ivo might be right. If everything would become obsolete, it would be best to start fresh at 1.0 with the right paint names/database/threads. Or else we`ll be doing double work.
Seems all the talk is about paints for the MOD Bikes? I do hope your going to include the organisation of the paints for the default bikes too? It would be a crime to disregard them, don't you think?
I think that the organisation of a database(preferably via the MEGA Site) is essential for future proofing the large amount of skins that will eventually be created, and indeed are already created if you include the default bike skins into the equation, and to limit the number of skins allowed just so you can keep all paints directly in the Bike Mods paint files to reduce download size is a crazy idea; this would only lead to fragmentation of the paint organisation by others just posting their paints on other threads, and we'll end up back were we started with paint files all over the place. You need a place were anyone can find all paints for all bikes(MOD and Default) in one place.
Seems to me that you guys are making this all too complicated to the point were it will either not get off the ground or it will fail. Keep it simple guys. ;) :)
Quote from: iVolution on January 07, 2014, 10:43:58 PM
- The already existing paints have to be renamed first to comply with the naming convention, deleting not used or irrelevant paints in the process.
I agree, if your going to have a file naming format then existing files will need to be renamed. But who is going to decide which paints are no longer in use or irrelevant, and how would that decision be made? :)
Quote from: JamoZ on January 08, 2014, 12:13:07 AM
Ivo might be right. If everything would become obsolete, it would be best to start fresh at 1.0 with the right paint names/database/threads. Or else we`ll be doing double work.
GpBikes 1.0 could be 1 - 2 years away, maybe even more. Lol ;D
You should look at it this way; use the time now to get a database up and running, and then by the time 1.0 comes along you will know exactly how to organise this really well. ;)
QuoteSeems to me that you guys are making this all too complicated to the point were it will either not get off the ground or it will fail. Keep it simple guys. ;) :)
No offence Hawk, but I don`t think you completely understand what we`re trying to do. I will include paints to ALL bikes into the mod ( adding pre made Murusama & Varese etc folders with paints only so that it`s just drag and drop like everything else). I`m calling it a mod, but actually it will just be one big package of up to date everything. Paints, versions, you name it. Every new mod bike will go into it, as will every new version of that bike. So if we manage to let everyone grab all the new versions from that one centralized "mod", like most of them are already doing, all the included up to date paints will automatically be downloaded aswell.
It`s already working. While you guys probably didn`t noticed it, i`ve included some updated paints into the Piaggio & R6 folder. With the 0.8 update that came out, everyone already grabbed those new paints without probably even knowing. I`ve seen it work as i`ve already seen those skins online. So that part of the idea works.
Next step is to let everyone post their skins into one thread, so i can include new skins every week if needed. So as a user you will experience one of the 2 following scenario`s :
1 : You want to enter a server, but you see that 1.3 is the server version of the mod and you are on 1.2. That means one or more bikes have been added or updated. So you go to the mod link and you see that the R6 is updated to version 0.9. You download that 0.9 and you don`t have to worry about any new paints because they are already included.
2 : You know that on friday new paints are always being added to the mod, so you go ahead and grab the seperate paint only folders i will provide.
Either way, eventually everyone is going to end up with the same paints whether they like it or not, you HAVE to update everything in order to keep playing on the modded servers and knowing that the package is always up to date, why not grab it form there to be sure?.
I have to say. I think MOD-Bike packs should just have default paints. It needs to be up to the people to get the paints they want not for some one to choose what paints they put in the mod bike pack.
This keeping file size low. Now if I want the unofficial/official paint packs, team packs, then that should be it's own thing not forced on me.
So MOD-Bike might have ever bike and default paint.
Then sub packs for bikes. Some people aren't going to care if they see the default on everyone.
Sorry but I'm not gonna try and cater towards the few ones that have bandwidth problems. We live in 2014, downloading a package of paints shouldn't be a problem, and if it is they can always grab bike updates from the author themself in the corresponding thread and grab their own paints from the paint thread. I'm not forcing anyone to use the pack, it's just a way for the ones that DO want everything centralized, organized and installable with one drag and drop action.
Hi JamoZ.
Thanks for explaining your plans and making it clear as to what your actually intending to achieve. I now see exactly what your actually planning and attempting to implement with the organisation of the paints for all bikes including the mod bikes. Thank you for that. ;) 8)
Sounds like now all you need to do is settle on the file naming format, post the procedures in a specialist paint thread, and then things can press ahead to get this fully up and running on top of what you've already done.
Sounds like a good idea so long as there are no restrictions on the number of paints to include in the database, and as I understand from you there would be no restrictions as there would also be a separate paints folder with other organised paints that the community can decide to download or not, separate from the paints folder included for the Mod Bikes(I hope I've got that right. Lol)?
I apologise if I seem a little pushy about this, JamoZ, but having organised and run the previous paints database, I really would like to see this new paint database up and running as soon as possible. ;) :)
Quote from: JamoZ on January 08, 2014, 01:50:50 AM
Either way, eventually everyone is going to end up with the same paints whether they like it or not, you HAVE to update everything in order to keep playing on the modded servers and knowing that the package is always up to date, why not grab it form there to be sure?.
I have to agree with Klax75, this is a bit too much for me too. Paint files are not huge, but you're gonna end up with a lot of them.
One thing I'd strongly advise is to include in the MOD only some common paints for each bike (modded bikes and default bikes). By "common paints" I mean a few nice and representative paints (5 to 10 per bike is probably enough), and no personal paint. Personal ones can go in a separate pack, if you want to manage them. Or we could create a forum section with personal paints: each message would have a standard template to make it easy to find the personal paint of a given rider.
No matter the bandwidth problems, I'm not sure many people will like to download a thousand personal paint files just because they "have" to.
Personally I think that personal paints make sense only when you're racing in events (where everybody can download an event-specific pack of paints): on public servers if one wants to be sure to be seen correctly he should use one of the "common" paints provided with the bike mod.
MaX.
@Max:
Hi Max.
As I understand it, JamoZ is basically going to do that by having majority of paints in a separate paints folder for others to decide if they want to download them individually or not.
Quote from: Hawk_UK on January 08, 2014, 09:55:59 AM
As I understand it, JamoZ is basically going to do that by having majority of paints in a separate paints folder for others to decide if they want to download them individually or not.
That would be fine, but it doesn't sounds like that from his last post (in reply to Klax75).
MaX.
Ok i hope this makes it more clear...
Users will have the following 4 options :
1 : download the whole package, bike versions & paints
2 : At the same link download just the complete and updated paint folders
3 : Ignore the package and download updated bikes and their default paints from the author on the forum
4 : Just browse the paint thread and grab whatever paints they like
Noone is forced to use anything as every aspect of the package is available as a separate download.
The only idea i can think of is provide 3 kinds of downloads, Paint folders only, Modded bikes only, and a complete package combining those 2. But i really can't see a reason why people just wouldn't want to have all the latest paints provided automatically...
Quote from: JamoZ on January 08, 2014, 10:52:03 AM
The only idea i can think of is provide 3 kinds of downloads, Paint folders only, Modded bikes only, and a complete package combining those 2.
1 archive with modded bikes with their own basic paints + 1 archive with all the other paints (or eventually 1 archive per bike with the extra paints).
It's not worth the effort to have a 3rd option (an archive with everything), in my opinion.
Quote from: JamoZ on January 08, 2014, 10:52:03 AM
But i really can't see a reason why people just wouldn't want to have all the latest paints provided automatically...
Because 1 paint file is 3-8Mb and if you put GPB on a 64 or 128GB SSD, space can become a problem.
MaX.
Quote from: HornetMaX on January 08, 2014, 11:26:32 AM
Quote from: JamoZ on January 08, 2014, 10:52:03 AM
The only idea i can think of is provide 3 kinds of downloads, Paint folders only, Modded bikes only, and a complete package combining those 2.
1 archive with modded bikes with their own basic paints + 1 archive with all the other paints (or eventually 1 archive per bike with the extra paints).
It's not worth the effort to have a 3rd option (an archive with everything), in my opinion.
Quote from: JamoZ on January 08, 2014, 10:52:03 AM
But i really can't see a reason why people just wouldn't want to have all the latest paints provided automatically...
Because 1 paint file is 3-8Mb and if you put GPB on a 64 or 128GB SSD, space can become a problem.
I think the third option is critical because in the end we want to encourage everybody to have all the paints. If they do not care to download a bigger file, but do not want the extra work in encorporating the paints seperately, the third option is necessary. It should be just as easy to have everything (mods+paints) as to install just the mods.
For each 500 paints it will take on average 2GB of storage with an already high average of 4MB per paint. I do not really share the opinion of Hawk that we should let everybody have as much
personal paints as they would like to. As some people simply create more paints then others, having 10 personal paints of the same person for a single bike, whilst he is probably only using the most recent one, is only creating extra storage for the database and will result in a shitload of unnecessary entries in the ingame selection menu. Personal paints are mostly for
personal use only, i guess no one is going to use them except for that person and their existence in the database is purely so that others can see your paint, not do display your whole collection of historical paint schemes.
This of course would not hold for the general paints (replica's, fantasy bike's, etc.) since everybody is going to make use of these and there is never too much of a choice.
As for the deletion or filtering of already existing paints that i mentioned earlier, I was thinking of paints that are of such a low quality that most would agree that should not have a place in the database. I can't mention a specific example but i recall seeing some "my first paint test" sort of paints that I cannot imagine somebody actually using on track. Yes this is pretty subjective but i hope you get the idea.
I don't see why you have to group paint packs with Mod Bike packs? It should be two different things. I am all for paint organization and I like having them all. Personally though I only use my personal paints. But I got the others so when on track I can see them.
It makes no sense to me loading the MOD bikes pack with paints. So even we may have MotoGP MOD Bike Pack, World SuperBike MOD Bikes Pack, and so on. But if I don't want the extra paints that you're saying I have to hunt down the authors website go searching for different forums. And try to find the stand bike .zip file.
Paint Organization should have nothing to do with MOD Bikes. Eventually the bike packs will get huge hundreds of mega bites, then having paints tacked on to the download adds even more to the download.
It doesn't make any sense. Up to date MOD Bike packs should be one thing, and Paint Organization packs should be something else. I want the most up to date bikes in one file. And then I can choose later if I want all the paints for whatever bike pack I downloaded.
We need choices.
I go and download MotoGP Mod Bike Pack (Which in the future make contain all the classes and models of bikes)
Then I can decide to choose later if I want MotoGP Official Team Paints Pack, MotoGP Fantasy Team Paints Pack, MotoGP Personal / Player Team Paints Pack.
Every make and model of bike will have it's own paints. But there should be the three categories of paints per bike.
To break it down.
MotoGP Bike Pack has base paint jobs thats it.
Now in the paint Organization site I can look under MotoGP Paints, which would give me a listing for each bike with the three categories.
Quote from: Klax75 on January 08, 2014, 04:13:32 PM
It doesn't make any sense. Up to date MOD Bike packs should be one thing, and Paint Organization packs should be something else. I want the most up to date bikes in one file. And then I can choose later if I want all the paints for whatever bike pack I downloaded.
I agree that it makes sense to have a seperation between those, but having the third option where everything is combined makes the installation a lot easier. As Jamoz said, I am also a person that does not care how large file sizes get. I just get the newest bikemod once in a while and i don't have to bother with installing the newest paints, and I guess we are not the only ones. The option 1 and 2 still cater to you and similar people that want to have the choice on what to install.
Quote from: iVolution on January 08, 2014, 04:20:04 PM
I agree that it makes sense to have a seperation between those, but having the third option where everything is combined makes the installation a lot easier.
Well, if whoever is maintaining the database/mega account is willing to upload stuff twice or thrice, fine to me.
But having 2 separate archives (1 for Bike MODs and their basic paints + 1 for Extra Paints) does not "make the installation a lot harder": unzipping 2 files instead of 1 file doesn't seem like a big deal.
On the other hand, if people have to download a large archive and manually delete the parts they don't want, that's very messy.
So, as far as the option to download separately MOD bikes (with basic paints) and Extra paints is there, whichever number of options is fine to me.
Notice however that more options --> more work for the lucky one that administer this stuff.
MaX.
Quote from: HornetMaX on January 08, 2014, 06:21:09 PM
Quote from: iVolution on January 08, 2014, 04:20:04 PM
I agree that it makes sense to have a seperation between those, but having the third option where everything is combined makes the installation a lot easier.
Well, if whoever is maintaining the database/mega account is willing to upload stuff twice or thrice, fine to me.
But having 2 separate archives (1 for Bike MODs and their basic paints + 1 for Extra Paints) does not "make the installation a lot harder": unzipping 2 files instead of 1 file doesn't seem like a big deal.
On the other hand, if people have to download a large archive and manually delete the parts they don't want, that's very messy.
So, as far as the option to download separately MOD bikes (with basic paints) and Extra paints is there, whichever number of options is fine to me.
Notice however that more options --> more work for the lucky one that administer this stuff.
MaX.
Let's see how long JamoZ is willing to put the necessary work in ;D
Try this link, paints are not renamed yet but this is the general idea....
https://mega.co.nz/#F!LwYHmKbJ!R4UaHGAZ6NQ37KDLSovS4A (https://mega.co.nz/#F!LwYHmKbJ!R4UaHGAZ6NQ37KDLSovS4A)
Quote from: JamoZ on January 08, 2014, 07:43:07 PM
Try this link, paints are not renamed yet but this is the general idea....
https://mega.co.nz/#F!LwYHmKbJ!R4UaHGAZ6NQ37KDLSovS4A (https://mega.co.nz/#F!LwYHmKbJ!R4UaHGAZ6NQ37KDLSovS4A)
Looks good to me, Jamoz. ;D 8)
I think this should satisfy everyone. Nice job, mate! ;) ;D
It`s really easy to maintain honestly. All i need now is a name template, so me and ivo can rename the paints, and let everyone use that standard.
And then a nice place where people can post their paints in a organized fashion..we`re nearly there ;)
Quote from: JamoZ on January 08, 2014, 07:43:07 PM
Try this link, paints are not renamed yet but this is the general idea....
https://mega.co.nz/#F!LwYHmKbJ!R4UaHGAZ6NQ37KDLSovS4A (https://mega.co.nz/#F!LwYHmKbJ!R4UaHGAZ6NQ37KDLSovS4A)
Thx Jamoz , looks good to me
Quote from: JamoZ on January 08, 2014, 07:43:07 PM
Try this link, paints are not renamed yet but this is the general idea....
https://mega.co.nz/#F!LwYHmKbJ!R4UaHGAZ6NQ37KDLSovS4A (https://mega.co.nz/#F!LwYHmKbJ!R4UaHGAZ6NQ37KDLSovS4A)
All fine Jamoz !
MaX.