+- Fearless Forums (https://fearlessrp.net)
+-- Forum: CityRP - Events Server (https://fearlessrp.net/forumdisplay.php?fid=489)
+--- Forum: Bugs (https://fearlessrp.net/forumdisplay.php?fid=128)
+---- Forum: Fixed/Closed (https://fearlessrp.net/forumdisplay.php?fid=129)
+---- Thread: Nobody is building or sending @ calls! (/showthread.php?tid=80758)
Pages:
1
2
Nobody is building or sending @ calls! - Tomo - 05-27-2017
Apparently nobody has spawned in any props or sent any @ calls in the last 27 days...
[Image: Rm9uhww.png]
RE: Nobody is building or sending @ calls! - Ryan F - 05-27-2017
I think it happened after the servers were down for maintenance
RE: Nobody is building or sending @ calls! - Prompt - 05-27-2017
I blame the restricted proplimits! Players get a proplimit of 0 and a prop extention of 1! I can't believe it!
RE: Nobody is building or sending @ calls! - Dragnort_ - 05-27-2017
Its probably a database thing, i spawned about 50 props today and saw a lot of others
RE: Nobody is building or sending @ calls! - Rebdogg - 05-27-2017
(05-27-2017, 03:09 PM)Dragnort_ Wrote: Its probably a database thing, i spawned about 50 props today and saw a lot of others
Confirmed proppsammer....
Yeah it's been like that since yesterday when the severs when down. Something probably fucked up along the way
RE: Nobody is building or sending @ calls! - Envy - 05-27-2017
I can't even get on stats
[Image: 5mbNcoV.png]
RE: Nobody is building or sending @ calls! - DVN - 05-27-2017
Stats need to be rolled back from the maintenance last night, must have changed some stuff.
RE: Nobody is building or sending @ calls! - Dauntless - 05-27-2017
They're messed up because of the hacker who wiped the databases last night I assume.
RE: Nobody is building or sending @ calls! - ELAD - 05-27-2017
no floodify to fix the website, remember
RE: Nobody is building or sending @ calls! - Marty - 05-27-2017
Even although the DB hack would have reset these figures it should only have been reset to 18 hours previously.
Not to 0, on top of that, even if it was reset to 0 the count should start over again. So there's not really a lot to worry about here. If the count hasn't started over then more than the Database has been breached.