Sarasota Initiative · Version 1.0
Community Standards & Server Rules
Serving Sarasota County • Manatee County • State of Florida
Browse all 32 sections
Scope & Application
These standards apply to Sarasota Initiative gameplay, official communications, events, development work, and member conduct connected to the community. Sarasota Initiative is a fictional roleplay community and does not represent a real government agency.
Departmental SOPs may add role-specific requirements but may not override these standards. References to approvals, staffing limits, cooldowns, and admission criteria mean requirements published by community leadership; this document does not assume a particular staffing ratio or minimum age has already been adopted.
Mission Statement
Sarasota Initiative (SI) is dedicated to providing one of the most realistic, immersive, and professional Grand Theft Auto V roleplay experiences possible. Our community is built around realistic law enforcement, fire rescue, EMS, civilian, and criminal roleplay inspired by the agencies and communities of Florida’s Suncoast.
Our objective is not to “win” roleplay scenarios but to create believable stories, encourage professional interactions, and provide an environment where every player’s actions contribute to a living world.
Every member is expected to conduct themselves with maturity, integrity, and professionalism both in and out of character.
Community Expectations
Every member shall:
- Treat all members with respect.
- Follow staff directions issued within these standards and report suspected misuse through the appeal process.
- Maintain maturity during roleplay.
- Separate Out-of-Character (OOC) issues from In-Character (IC) interactions.
- Use common sense at all times.
- Promote realistic, immersive roleplay.
Sarasota Initiative maintains a zero-tolerance policy for toxicity, discrimination, harassment, or intentionally ruining another player’s experience.
Definitions
Random Death Match (RDM)
Killing another player without valid roleplay or escalation.
Examples:
- Shooting someone because they looked at you.
- Killing another player without interaction.
- Random attacks.
Punishment: Severe disciplinary action up to permanent removal.
Vehicle Death Match (VDM)
Using a vehicle primarily as a weapon.
Examples include:
- Running players over intentionally.
- Using a vehicle to assault officers.
- Purposely ramming players.
Accidental contact is assessed in context. Department-authorized pursuit interventions must meet the Pursuits, Collisions & Vehicle Contact rules; using a vehicle for random attacks remains prohibited.
Meta Gaming
Using information your character could not reasonably know.
Examples include:
- Using another player’s livestream to obtain information or gain an in-character advantage.
- Using CAD information without authorized in-character access or a legitimate roleplay reason.
- Using OOC Discord communications to coordinate in-character actions. Approved in-character radio or dispatch channels are permitted for authorized users.
- Acting on information obtained outside roleplay.
Power Gaming
Forcing unrealistic actions onto another player or performing actions impossible in real life.
Examples:
- “/me knocks officer unconscious.”
- Breaking handcuffs without roleplay.
- Escaping restraints unrealistically.
Combat Logging
Disconnecting to avoid:
- Arrest
- Death
- Roleplay
- Staff intervention
- Criminal consequences
Combat logging is strictly prohibited.
FailRP
Any action that significantly breaks realism.
Examples include:
- Driving a sports car through swamps without consequence.
- Walking away after multiple gunshot wounds.
- Ignoring major vehicle crashes.
- Jumping from rooftops without injury.
Roleplay Standards
Sarasota Initiative is a serious realism server.
Members are expected to portray believable characters and make decisions consistent with how a reasonable person would behave in real life.
Every action should support ongoing storylines rather than simply seeking excitement or conflict.
Roleplay should always take priority over winning.
Character Creation
Every character must have:
- A realistic first and last name.
- A believable age.
- A consistent personality.
- A realistic backstory.
The following are prohibited:
- Meme names
- Celebrity names
- Fictional character names
- Troll characters
FearRP & Value of Life
Your character values their life.
If confronted by overwhelming force, your character should generally comply unless there is a realistic opportunity to escape.
Examples include:
- Complying with multiple armed suspects.
- Surrendering when surrounded.
- Seeking medical treatment after injuries.
Unrealistic “hero” behavior is prohibited.
New Life Rule (NLR)
After roleplay death is established and respawn or scene release occurs:
- You may not return to the scene for at least 30 minutes after respawn or scene release; staff may extend exclusion until the original scene ends.
- You may not remember the events immediately leading to your death.
- Revenge killings are prohibited.
Vehicle Realism
Vehicles must be operated realistically.
The following are prohibited:
- Unrealistic off-roading.
- Continuous high-speed driving through neighborhoods.
- Unrealistic jumps.
- Purposeful desync abuse.
- Intentional ramming outside a department-authorized intervention permitted by these rules.
Firearms & Use of Force
Firearms are considered deadly force.
Deadly force should always be a last resort.
Roleplay and de-escalation should occur whenever reasonably possible.
Gunfights should be rare, meaningful, and justified by the circumstances.
Criminal Roleplay
Criminal roleplay should emphasize planning, investigation, and storytelling.
Criminals are expected to:
- Create believable scenarios.
- Leave opportunities for investigation.
- Avoid unnecessary violence.
- Accept realistic consequences for their actions.
Random violence and “cop baiting” are prohibited.
Civilian Roleplay
Civilian roleplay is essential to the server’s economy and atmosphere.
Encouraged careers include:
- Business owners
- Mechanics
- Tow operators
- Journalists
- Attorneys
- Commercial drivers
- Construction workers
- Security personnel
- Real estate agents
- Fishermen
- Utility workers
Law Enforcement Standards
Law enforcement officers shall:
- Maintain professionalism.
- Follow departmental Standard Operating Procedures.
- Use realistic tactics.
- Complete reports accurately.
- Utilize proportional force.
- Preserve crime scenes.
Abuse of authority, revenge policing, and quota-based enforcement are prohibited.
Fire Rescue & EMS
Emergency medical personnel shall:
- Treat injuries realistically.
- Coordinate with law enforcement.
- Assess injuries based on the incident and coordinate believable outcomes with the patient.
- Transport patients when appropriate.
Players may not refuse legitimate medical roleplay simply to respawn.
Safe Zones
The following areas are designated Safe Zones unless an approved roleplay event is occurring:
- Spawn Locations
- City Hall
- DMV
- Staff Training Areas
Do not initiate criminal activity in designated Safe Zones. Existing incidents are handled under Safe Zones, Priorities & Event Controls; entering a safe zone does not erase an active scene.
Staff Authority
Staff members are responsible for maintaining fairness and realism.
During active situations:
- Staff directions govern the immediate situation and may be reviewed through the appeal process afterward.
- Do not argue during roleplay.
- Appeals may be submitted after the situation concludes.
Failure to comply with staff instructions may result in disciplinary action.
Intellectual Property & Asset Protection
Ownership & Permission
SI respects the ownership and licensing of all community and third-party assets. Assets include scripts, source code, vehicle models, liveries, uniforms, maps, textures, logos, graphics, audio, and documentation.
Ownership remains with the respective rights holder unless a separate written agreement provides otherwise. Purchasing, commissioning, contributing, or hosting an asset does not by itself give SI or a member ownership of every underlying component or permission to redistribute it.
Access to SI servers, development files, or staff resources grants permission only for the approved community purpose. Membership, staff status, or a donation does not grant ownership or permission to copy, sell, share, or reuse protected assets.
Prohibited Conduct
- Ripping, dumping, extracting, or copying assets from SI or another community without authorization from the relevant rights holder.
- Leaking, selling, trading, uploading, or redistributing protected assets, source files, credentials, or download links without authorization.
- Using stolen, leaked, or pirated assets, or asking another person to obtain or distribute them.
- Bypassing asset escrow, encryption, access controls, or other protections to obtain or reuse an asset without authorization.
- Removing creator credits, license notices, or identifying marks contrary to the applicable license, or claiming another creator’s work as your own.
- Reusing SI-owned branding or assets on another server, project, or commercial product without written approval.
Contributions & Approved Use
Members who submit assets must have permission to provide them and must disclose applicable licenses, usage limits, required credits, and third-party components. Publicly available or open-source assets may be used only in accordance with their licenses and SI’s approval process.
Before commissioned or contributed work is accepted, community leadership and the contributor should document ownership, permitted use, modification rights, distribution rights, and any continuing use after the contributor leaves. Submission alone does not transfer ownership.
Staff approval does not override a creator’s license or authorize use of content that SI does not have permission to use.
Reporting & Enforcement
Report suspected asset theft, ripping, or unauthorized distribution privately to staff. Provide available evidence, such as the original creator’s listing, license terms, or relevant messages. Do not repost or redistribute the disputed asset as part of the report.
Staff may restrict access to or remove disputed assets while reviewing the report. Violations may result in loss of development or staff access, removal of the affected content, suspension, or permanent removal from the community. Appeals may be submitted after the staff review concludes.
Accounts, Access & Community Conduct
- Use only your approved account and identity. Account sharing, impersonating another member or staff member, and using alternate accounts to evade restrictions are prohibited.
- Meet the community’s published admission requirements and the applicable platform eligibility requirements. Do not misrepresent your age or qualifications.
- Harassment, discriminatory slurs, targeted humiliation, threats, stalking, doxxing, and retaliation are prohibited in community spaces and in off-platform conduct targeting members because of community activity.
- Do not raid other communities, organize harassment, spam channels, or use unsolicited messages to recruit members or advertise services.
- Keep account credentials, server access details, and staff materials secure. Report compromised accounts promptly; do not share passwords or access tokens.
Privacy, Streaming & Sensitive Content
- Do not publish or threaten to publish anyone’s real name, address, workplace, phone number, account details, private messages, or other personal information without permission.
- Gameplay may be recorded or streamed. Do not reveal private information during gameplay, and do not broadcast staff tickets, confidential meetings, credentials, or private development material without authorization.
- Stream sniping and using recordings, stream chats, or outside communications for an in-character advantage are prohibited. A recording may be submitted privately as evidence.
- Sexual roleplay, sexual violence, sexual harassment, and sexual content involving minors are prohibited. Hate-based roleplay and reenactments of real-world mass-casualty attacks are prohibited.
- Graphic torture, mutilation, and suicide or self-harm scenarios are not permitted. Non-graphic injuries must remain appropriate for the community.
- A member may request an immediate pause for a real-life safety or personal-boundary concern. Stop the disputed content and contact staff. Staff will arrange a suitable continuation or scene resolution; a boundary request does not automatically erase unrelated in-character consequences.
Cheating, Exploits & Technical Integrity
- Cheats, unauthorized mod menus, aimbots, wallhacks, malicious scripts, packet manipulation, and tools that provide an unfair advantage are prohibited.
- Do not exploit bugs, duplicate items or vehicles, abuse animations or collision, manipulate hit registration, or deliberately disrupt server performance.
- Report suspected exploits privately to staff. Do not repeat, distribute, or demonstrate an exploit on the live server without explicit authorization.
- If a bug affects a scene, preserve evidence and request assistance. Do not use technical failures as permission to gain an advantage or erase consequences.
- Do not connect to restricted systems, access another member’s data, or test server security without explicit authorization.
vMenu, Spawning & Fleet Controls
Menu access is a technical permission, not permission to use every available feature during roleplay.
- Spawn only vehicles, weapons, equipment, and character models approved for your role. Restricted fleet vehicles, uniforms, liveries, and equipment require the relevant authorization.
- Do not use teleportation, noclip, god mode, invisibility, player blips, spectating, health restoration, or armor restoration to gain an advantage. Staff tools are limited to authorized staff duties or approved testing.
- Do not repair, clean, replace, delete, or respawn a vehicle during a pursuit, collision, investigation, or other active scene to hide damage, remove evidence, or avoid consequences.
- Do not change characters, clothing, plates, weapons, or loadouts through menus to bypass a search, restraints, recognition, or inventory limits. Any permitted change must be supported by believable roleplay.
- Spawn vehicles in a clear, suitable location. Do not spawn on players, block roads, create duplicate active units, or abandon unnecessary entities.
- Use the approved fleet assignment and spawn process where available. Take-home assignment permits approved off-duty storage and later use; it does not authorize unlimited replacements, unauthorized transfers, or use of another member’s assigned vehicle.
- Staff may remove unattended entities for performance or safety. Cleanup does not automatically end an investigation or remove a character’s responsibility.
Scene Integrity & Fair Participation
- Stay in character during active scenes unless staff pauses the scene or a real-life safety concern requires a pause. Use the designated OOC or support channel for disputes.
- Do not force another player’s response through emotes. Describe attempts and observable facts, allow a reasonable response, and do not fabricate evidence or claim automatic success.
- Do not join an active pursuit, robbery, hostage incident, traffic stop, or emergency merely because you saw it in a stream, heard OOC discussion, or want action. Participation needs a believable in-character connection.
- Do not repeatedly return to provoke the same player, camp respawn locations, target someone because of an OOC dispute, or manufacture reasons to restart a resolved conflict.
- Do not use another character to rescue your own character, retrieve their belongings, transfer scene knowledge, or bypass discipline. Keep each character’s knowledge and relationships separate.
- Staff, not individual participants, decide whether a disputed scene must be reset or voided. Preserve the scene and evidence where safe while requesting help.
Disconnects, Restarts & Returning to Play
- If you crash or lose connection during a scene, reconnect as soon as reasonably possible and notify staff or the involved participants through the approved support channel.
- Resume the scene from a fair point determined by staff. A disconnect, scheduled restart, or server crash does not automatically clear an arrest, injury, investigation, or other consequence.
- If you cannot return, notify staff when able and explain the interruption. Unavoidable emergencies and verified technical failures should be assessed separately from intentional combat logging.
- Do not start a major scene immediately before an announced restart when it cannot reasonably be completed. Follow any staff-announced restart restrictions.
- Do not go AFK to avoid interaction. If you must leave during an active scene, notify participants and seek staff assistance when practical.
Injuries, Incapacitation & Character Death
- Roleplay injuries based on the event and continue them through treatment and recovery. A health bar, respawn, or repaired vehicle does not by itself establish that your character is uninjured.
- An unconscious or incapacitated character cannot transmit tactical information, identify suspects in real time, fight, drive, or perform actions inconsistent with their condition.
- Medical personnel describe findings and provide treatment; players should cooperate in establishing believable injuries. Neither side may impose permanent disability or permanent character death without the character owner’s agreement or an established, previously accepted community process.
- Being downed is not automatically death. The New Life Rule applies after roleplay death is established and respawn or scene release occurs. Its 30-minute exclusion begins at that point; staff may extend scene exclusion until the original scene ends.
- The New Life Rule does not permit returning on another character, directing others to retaliate, or recovering lost incident knowledge from OOC sources.
- Do not use suicide, respawning, or a death declaration to escape arrest or another active consequence. Staff will resolve disputed outcomes.
Pursuits, Collisions & Vehicle Contact
- Account for the vehicle’s type, road surface, weather, visibility, traffic, and damage. Performance upgrades do not justify impossible handling or sustained driving after disabling damage.
- Roleplay significant collisions and injuries. Stop or adjust your driving when the vehicle could not realistically continue.
- Purposeful ramming for disruption or an easy win is prohibited. A trained, department-authorized pursuit intervention is permitted only when allowed by the applicable SOP and supported by the circumstances; it is not a general exception to VDM.
- Do not use water, map boundaries, interiors, inaccessible terrain, or despawning to exploit pursuers or erase a vehicle.
- Aircraft and watercraft require appropriate authorization and believable operation. Do not use aircraft as weapons or crash them intentionally without approval for a controlled event.
Robberies, Hostages & Criminal Escalation
- Establish a believable motive and meaningful interaction before escalating. An insult, minor traffic collision, refusal to talk, or routine traffic stop alone does not justify lethal violence.
- Do not use a cooperating friend, alternate character, or fabricated NPC as a hostage to manufacture negotiating leverage.
- Give hostages a realistic opportunity to comply. Do not demand account credentials, real money, personal information, OOC actions, or outcomes participants cannot control.
- Do not force transfers of permanent businesses, character ownership, or protected property through a spontaneous scene. Follow any published property and robbery systems.
- Do not repeatedly rob, kidnap, or attack the same person without a continuing, believable story and an opportunity for the other player to participate fairly.
- Kidnapping on-duty responders, attacks on emergency facilities, organized mass-casualty incidents, explosives, terrorism scenarios, and coordinated major events require advance staff approval. Prohibited sensitive content remains prohibited even during an event.
- Follow announced staffing, cooldown, participant, and equipment limits. If no applicable limit is published, obtain staff guidance before organizing a major incident.
- Official corruption, evidence tampering by department members, and misuse of restricted government equipment require advance leadership approval as a storyline. Approval never permits OOC abuse.
Emergency Services, CAD & Evidence
- Do not access, search, disclose, or alter CAD records unless authorized for your role and the roleplay purpose. Access to a screen does not mean your character is entitled to its information.
- Reports, citations, warrants, medical records, and evidence logs must accurately reflect the roleplayed event. Do not invent observations or change records to secure a preferred outcome.
- Preserve chain of custody and give other participants a fair opportunity to investigate, seek counsel where supported, or challenge evidence through roleplay.
- Body-camera and dash-camera evidence must follow the community’s published equipment rules and the camera’s plausible view. OOC footage is not automatically an in-character recording.
- Do not commandeer emergency vehicles, uniforms, radios, or restricted equipment without an approved scenario and believable access.
- Provide dispatch with clear, relevant traffic. Do not jam channels, transmit while realistically unable to do so, or use emergency communications to harass others.
Safe Zones, Priorities & Event Controls
- Safe zones prohibit starting criminal activity, attacks, or provocation. They may not be used to shelter from an already active pursuit or to taunt others without consequences.
- If an active incident reaches a safe zone, request staff guidance and avoid further escalation around uninvolved players. The zone does not automatically cancel the incident.
- Honor announced areas of patrol, priority holds, peaceful periods, scene caps, and restricted locations. Do not begin a competing major incident during a hold.
- Event approvals apply only to the agreed scope, location, participants, and time. They do not waive community conduct, consent boundaries, or asset protections.
- Staff should communicate temporary restrictions clearly and lift them when no longer needed.
Staff Accountability & Conflicts of Interest
- Staff are subject to the same community standards. Rank, donations, friendships, and departmental position do not grant immunity.
- Use staff powers only for moderation, support, approved testing, or server operations. Do not use staff information or tools to benefit your character or preferred group.
- Where practical, a staff member directly involved in a dispute must refer the decision to an uninvolved staff member. Urgent action may be taken to stop harm or disruption, followed by independent review.
- Document material disciplinary decisions, the rule involved, relevant evidence, and the reason for the outcome. Share case details only with those who need them for review.
- During a live scene, operational staff directions govern the immediate response; they remain reviewable afterward. No instruction may require disclosure of passwords, personal information, real-world payments, or participation in prohibited content.
- Do not retaliate against a member for a good-faith report, appeal, boundary request, or complaint about staff.
Reports, Evidence & Appeals
Use the designated staff support or reporting channel. If the complaint concerns the person receiving it, request an uninvolved senior staff member.
- Include the approximate incident time, relevant player identifiers, a concise account, the rule you believe applies, and available clips, screenshots, or logs.
- Keep original evidence and enough surrounding context to explain the incident. Do not fabricate, alter, selectively present, or delete evidence to mislead a review.
- Do not publicly shame members, organize mass reports, pressure witnesses, or repeatedly contact individual staff about the same case. Good-faith reports are welcome even when a violation cannot be confirmed.
- A person accused of a violation should have a reasonable opportunity to explain their account when circumstances permit. Immediate restrictions may be used to stop ongoing harm.
- Appeals should identify the decision being challenged, explain the claimed error or disproportionate outcome, and include any new evidence. An uninvolved reviewer should handle the appeal where practical.
- An appeal does not suspend a restriction unless staff explicitly says so. Do not evade restrictions while awaiting review.
- Members need not install invasive software, disclose passwords, or provide unrestricted access to personal devices to submit or defend a report.
Disciplinary Outcomes & Rule Changes
Staff should consider severity, intent, impact, available evidence, prior history, and willingness to correct the behavior. Outcomes may include coaching, a warning, removal from a scene, restrictions on roles or tools, temporary suspension, removal from staff or a department, or permanent removal.
Discipline is not a guaranteed warning ladder. Serious harassment, doxxing, cheating, deliberate asset theft, or severe disruption may justify immediate removal. Similar cases should be treated consistently, and the reason for material differences should be documented.
In-character penalties and community discipline are separate. An acquittal does not resolve an OOC rule violation, and staff discipline does not automatically determine an in-character criminal outcome.
Leadership should publish material rule changes with a version or revision date and communicate them through official channels. New restrictions should not be applied retroactively to conduct that was previously permitted; existing rules still apply to ongoing conduct.
Questions about an unclear rule should be raised before undertaking a high-impact scenario. Examples illustrate the rules and do not create loopholes for equivalent disruptive behavior.
Member Acknowledgment
Participation in Sarasota Initiative requires reading and following these standards, applicable departmental SOPs, and clearly announced event restrictions. Members are responsible for reviewing published updates. When a departmental policy conflicts with these community standards, the community standards govern; staff should clarify the conflict.
