Character
Rules
Events
Map
RP Points
Proplimits
Statistics
Steam Group
Members
Hall of Fame
Team
Bans
Blacklists
Warnings
Changelog
Content
07-29-2018, 01:27 AM
(This post was last modified: 09-01-2022, 01:07 AM by Fearless Community. Edited 6 times in total.
Edit Reason: Fixed Encoding
)
I explained the currency issue in the discord general chat by the way Huskii. You can probably find it somewhere by doing ctrl+f - The reason the original thread in announcements was so short was because we just received the figures ourselves and needed something done ASAP and so a lengthy explanation was not plausible, which as I previously stated was remedied in the general chat in discord.
As for transparency we can always get better, however in the last year we have been extremely transparent.
This should be apparent in things such as the strike system (where you no longer get the feeling of not knowing and simply received 'abuse noted', but actually get a somewhat detailed explanation on the strike system thread - considering it's not sensitive issues such as leaking which could expand the leak further):
https://www.fearlessrp.net/showthread.php?tid=83582
The community survey where the results were later revealed:
https://www.fearlessrp.net/showthread.php?tid=85413
Inactivity announcements being moved to the public so people know when people aren't on the server:
https://www.fearlessrp.net/showthread.php?tid=84224
Proplimit guidelines being moved to the public and later the admin one too:
https://www.fearlessrp.net/showthread.php?tid=84347
And more.
Personally I think from being able to see the offices - There's nothing for you TO know really, the main things resolve around rule changes which are now able to be discussed in the suggestions forum after a recent change, and promotions - which obviously can't get out because there's a chance someone might not actually get it.
When it comes to Development we don't want to over hype updates because everyone is here voluntary and Developers in the past and present don't want added pressure to get their updates out in a hurry as they want to go on their own pace. Sometimes people will switch projects to something that needs more attention which can lead to further delays and sometimes people may resign mid-project and another Developer may not want to pick it up. I'm not sure what more we can give you honestly. These are all from learning from past mistakes.
Spoiler :
![[Image: oTyU9AB.png]](https://i.imgur.com/oTyU9AB.png)
As for transparency we can always get better, however in the last year we have been extremely transparent.
This should be apparent in things such as the strike system (where you no longer get the feeling of not knowing and simply received 'abuse noted', but actually get a somewhat detailed explanation on the strike system thread - considering it's not sensitive issues such as leaking which could expand the leak further):
https://www.fearlessrp.net/showthread.php?tid=83582
The community survey where the results were later revealed:
https://www.fearlessrp.net/showthread.php?tid=85413
Inactivity announcements being moved to the public so people know when people aren't on the server:
https://www.fearlessrp.net/showthread.php?tid=84224
Proplimit guidelines being moved to the public and later the admin one too:
https://www.fearlessrp.net/showthread.php?tid=84347
And more.
Personally I think from being able to see the offices - There's nothing for you TO know really, the main things resolve around rule changes which are now able to be discussed in the suggestions forum after a recent change, and promotions - which obviously can't get out because there's a chance someone might not actually get it.
When it comes to Development we don't want to over hype updates because everyone is here voluntary and Developers in the past and present don't want added pressure to get their updates out in a hurry as they want to go on their own pace. Sometimes people will switch projects to something that needs more attention which can lead to further delays and sometimes people may resign mid-project and another Developer may not want to pick it up. I'm not sure what more we can give you honestly. These are all from learning from past mistakes.
![[Image: f2kzlKW.png]](https://i.imgur.com/f2kzlKW.png)