Skip to content
View in the app

A better way to browse. Learn more.

LCPDFR.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

What is the countdown for?

Featured Replies

No, there isn't enough time to correct everything and prepare for beta in that short amount of time.

Don't no, when you say that short amount of time, what about the time b4 the counter was displayed? And when you look at the special forum, nobody has made a comment for nearly a week so the alpha3 must be in good order coz nobody reportin bugs. I still think its just when thay guna pick beta testers lol

  • Replies 310
  • Views 19.4k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • For our super secret nuke of course. No one can't stop us! NO ONE!

  • Interference
    Interference

    Guys I got exclusive access to 0.95 Beta! Look! NOTE: Just kidding.

  • What I dont get is what is so classified about a damn modification that it has to have closed testing. There is no reason for it. Its not like you risk anything by making the alpha/betas public down

Don't no, when you say that short amount of time, what about the time b4 the counter was displayed? And when you look at the special forum, nobody has made a comment for nearly a week so the alpha3 must be in good order coz nobody reportin bugs. I still think its just when thay guna pick beta testers lol

Bugs aren't reported over the forum herp derp, we report them over the developer's hub.

Due to the graphic nature of this post, reader discretion is advised.
lspdfrsig2njsuy.jpg

LCPD First Response 0.95, along with a gigantic range of improvements, now allows you to code your own scripts, callouts and world events for LCPD:FR.

Using LCPD:FR's new Lua API, you now have access to LCPD:FR's innovations and proven engine to unleash your own creativity.

Sounds intresting, although I'm not such a awesome coder. :confused:

[center][url="http://styragressor.tumblr.com/post/33331898333"][img]http://i.imgur.com/b2aNE.gif[/img][/url][/center]

Sounds intresting, although I'm not such a awesome coder. :confused:

Before Alpha Testing began, there was a forums for code edits. but only devs could view it and it was taken down.

Sticks and stones may break bones, but 5.56 fragments on impact.

What I dont get is what is so classified about a damn modification that it has to have closed testing. There is no reason for it. Its not like you risk anything by making the alpha/betas public downloads. If it won't cause someones computer to fail and/or the download will be free than why hide it so much.

Its not like someone can't go back to .91 if they dont like the bugs. This just doesn't make any sense at all. If LCPDFR was something we had to pay for than I wouldnt mind waiting for a final version because I personally don't like it when something is broken and I paid for it. But #1 LCPDFR is a free modification and that won't change, #2 The previous download is and should still be avail for download, and #3 a Open testing would improve testing.

Thats just my, wand what should everyone elses, .02

Well LCPD:FR is free, so if you don't like how the devs manage the testing of the Alpha/Betas you may aswell go to PPM. And you probably just ruined your chance on being a 0.95 Beta Tester, so yay for that.

For a nicer sounding version, read post below.

Edited by Break

Due to the graphic nature of this post, reader discretion is advised.
lspdfrsig2njsuy.jpg

They have outlined in a post why they keep it closed. It's because they are a team that looks to release a quality product to the masses. A buggy, unstable, difficult to understand product is not mass marketable. And while they're doing this for free, G17 is still a company, and integrity is important. Let them make their product on their terms.

Tips/Donate: u.gamecaster.com/unr3al
Twitch Channel: Twitch.tv/unr3al_twitch
YouTube Channel: YouTube.com/unr3algaming
Twitter: @unr3alofficial

No, there isn't enough time to correct everything and prepare for beta in that short amount of time.

If it isn't Beta then what is it? (Mysterious music starts) DUN DUN DUN. I guess we'll find out when that reaches to 0:00:00:00. Unless it's some sort of prank lol.

They have outlined in a post why they keep it closed. It's because they are a team that looks to release a quality product to the masses. A buggy, unstable, difficult to understand product is not mass marketable. And while they're doing this for free, G17 is still a company, and integrity is important. Let them make their product on their terms.

There is an easy fix to that "release a quality product to the masses. A buggy, unstable, difficult to understand product is not mass marketable"

Highlight the current official version, and sub the beta version. Make it clear that the beta version is buggy and could cause frequent crashing. But there is just no reason to tease people. Teasing only works in the payware market because it makes you want it more thus bringing in more net$. But that doesn't work here. It makes the devs look like they get a thrill from teasing people. Im not saying they closed the testing for a thrill. It just seems unreasonable to lock something from the public just because you want to.

Edited by b737lvr

First of all, I noticed that the color of the countdown changed from red to yellow. So I think it is something good, but then again I might be completely wrong. I got 2 predictions. Maybe its when they will announce who the beta testers are (they will not release the beta, theyll just release who are gonna beta test it) or they will tell the beta testers that they are gonna beta test but the rest of the public wont know. My second and the most likely, nothing. There will be nothing, but then why would they put it. I will continue to think about even though I wont figure it out in time.

I don't want to customize my profile. Stop asking.

Why not let the devs release it on their terms? They don't want a buggy version at all.

Edited by unr3al

Tips/Donate: u.gamecaster.com/unr3al
Twitch Channel: Twitch.tv/unr3al_twitch
YouTube Channel: YouTube.com/unr3algaming
Twitter: @unr3alofficial

.91 is buggy

Your buggy.

sorry couldnt resist :P

  • Management Team

There is an easy fix to that "release a quality product to the masses. A buggy, unstable, difficult to understand product is not mass marketable"

Highlight the current official version, and sub the beta version. Make it clear that the beta version is buggy and could cause frequent crashing. But there is just no reason to tease people. Teasing only works in the payware market because it makes you want it more thus bringing in more net$. But that doesn't work here. It makes the devs look like they get a thrill from teasing people. Im not saying they closed the testing for a thrill. It just seems unreasonable to lock something from the public just because you want to.

Well it is. So live with it.

And no, it's not because we 'get a thrill from teasing people'. Look at our fucking support forum. Now imagine an open beta buggy version.

You can imagine those two things would not mix.

Plus, it's good to reward certain members of the community the ability to playtest LCPD:FR, in return for the time and generousity they show dealing with support requests and activity on the forum.

If you would've clicked the link (I think it was milestone), you would've found out what the countdown was for, but I'm keeping that a secret.

EDIT: Hey, look, the countdown is back to just over 2 days.

Edited by c13

Sticks and stones may break bones, but 5.56 fragments on impact.

Guest
This topic is now closed to further replies.

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.