This is just a complete random idea, I have no idea if it would work, but here goes.

First of all, I'd like to state categorically: WE LOVE LCPD:FR! It's a really awesome mod and, whilst I'm sure that LSPD:FR is just as fantastic, nothing yet beats the mods and customizations available for LCPD:FR. Plus, I'm sure some of us just don't want to buy a new game :P

As such, I would propose that when LCPD:FR sadly does eventually reach EOL at G17 Media, its code is passed into the hands of the community. G17 Media can retain the LCPD:FR trademark and branding, the community can retain our sense of community centred around this mod, and the wider world retains THE BEST police mod for GTA ever invented. And arguably the best police game ever too.

What are your thoughts on this? G17 people, is this feasible?

In terms of licensing and the legal bits, I'd personally recommend the Microsoft Public License or the Microsoft Reciprocal License, as they both allow for retention of trademark rights and the rights of the owner whilst open-sourcing. They're also OSI approved.

Again, none of this may be feasible, it might all be impossible, but I'm just putting it out there.

It's LCPDFR, not LCPD:FR. 

In regards to open sourcing LCPDFR, LCPDFR and LSPDFR both share similar code and engine, therefore open sourcing LCPDFR would probably only happen if LSPDFR was EOL'd.

However, this is why we introduced the API. You can get started creating your own callouts for LCPDFR right now.
I'd be willing to expand the API of LCPDFR, if this is wanted, to allow external developers to introduce new features, but as far as I'm aware, the LCPDFR API is pretty feature complete.

Edited August 17, 201510 yr by Cyan

It's LCPDFR, not LCPD:FR. 

In regards to open sourcing LCPDFR, LCPDFR and LSPDFR both share similar code and engine, therefore open sourcing LCPDFR would probably only happen if LSPDFR was EOL'd.

I'd be willing to expand the API of LCPDFR, if this is wanted, to allow external developers to introduce new features, but as far as I'm aware, the LCPDFR API is pretty feature complete.

Apologies, I thought LCPD:FR was the "official" name. :P

With regard to extensions of the API, that could be good, but it's not really the same heh. I understand your point about the engine similarities, but I do worry that after LCPDFR EOL (which seems frighteningly close to me :/) things might break and existing bugs may not be fixed.

Oh well, it was worth a go :P

I could imagine open sourcing it at some point, but not anytime soon. I know that this probably not what you expected to hear, as the longer we wait the more IV might die, but as Cyan mentioned it's closely related to LSPDFR atm and would also need a clean up in some areas (server communication, authentication) to remove sensitive stuff. Your best bet would be to bring this up again next year.

So its 2022 almost and will this be a thing? I'd love to take a crack at fixing the FPS drop when going on duty and during traffic stops.