The PixelPH City Code
PixelPH’s independent Serious RP rulebook: written for our city, our systems, and our long-term roleplay standard.
The standards that guide every decision, scene, and character inside PixelPH.
PixelPH is built around long-form character stories, not scorekeeping.
Choose the action that creates believable roleplay even when a game mechanic offers an easier advantage.
Winning a scene never overrides continuity, fairness, or the consequences created by your character’s choices.
Behavior expected from every member across the city and official community spaces.
Treat other members with basic respect in the city, Discord, streams, and support channels. Harassment, targeted abuse, discriminatory remarks, and slurs are not acceptable.
Keep each Discord channel on purpose and do not use community spaces to leak in-city information, spoil active stories, or advertise unrelated communities. Stream promotion belongs only in the designated creator channels.
Use an appropriate account/display name. If staff asks you to change an offensive name, do not return with the same or another deliberately offensive name.
When a dispute needs staff review, move it to the ticket system instead of turning public channels into an argument.
Streaming does not remove your responsibility to protect other players’ roleplay. Commentary may be critical, but personal attacks, discriminatory language, public ban discussions, and OOC pile-ons are not acceptable.
Viewers must not feed a streamer information their character has not learned. Streamers must not use chat, clips, another broadcast, or viewer messages to gain an in-city advantage.
Do not spoil another player’s storyline or backseat a creator unless they have clearly asked for gameplay help. Support creators without using streams as an intelligence source.
Use a support ticket for questions, reports, appeals, or situations that need staff review. Opening a ticket is the correct process and should not be mocked in character or out of character.
Staff members who are actively roleplaying should be treated as their characters unless they explicitly enter an administrative interaction.
Disagreements should remain mature. Finish the scene when possible, preserve evidence, and let staff resolve the rule issue afterward.
These are the standard PixelPH bindings used by the current city setup. Players may remap supported controls through FiveM settings.
To change supported controls, open Settings → Key Bindings → FiveM. If you disconnect during an active scene, notify the involved players through the proper support channel and reconnect when possible.
Fair-play standards covering client modifications, exploits, and outside transactions.
Visual improvements are allowed only when they do not provide information or visibility that a normal player would not have.
Forbidden advantages include removing vegetation or props for visibility, unnaturally bright nights or water, amplified positional footsteps, hit/kill effects that aid combat, or display settings intentionally used to enlarge practical targets.
Keep client-side changes cosmetic. If a modification changes what you can detect, see, hear, target, or avoid during gameplay, do not use it.
Third-party software, injected tools, cheat menus, or modifications that create an unfair advantage are prohibited.
Do not duplicate items, abuse bugs, bypass intended restrictions, animation-cancel restraints, force players through geometry, or deliberately use mechanics in a way that defeats the intended roleplay system.
Characters under the same player may not be used as a pipeline for money, property, items, or information. Creating alternate characters to move wealth back to another character is treated as severe exploitation and may result in permanent removal.
If you discover an exploitable bug, stop using it and report it privately to staff.
PixelPH assets, currency, items, properties, services, or advantages may not be privately bought or sold for real-world money or value.
Both sides of an unauthorized transaction may be permanently removed. Only official, platform-compliant PixelPH purchase channels may be used for approved offerings.
Rules that protect believable characters, information boundaries, injuries, and continuity.
Active roleplay communication must stay inside approved in-game systems. External calls, private chats, or other third-party communication cannot be used to coordinate a live scene.
A clear, working microphone is required. Test it before entering the city.
Voice alteration is not permitted as a combat/criminal concealment tool. A distinct character voice may be considered only when it remains understandable and has been cleared through the appropriate staff process.
Racist or discriminatory conduct is not part of acceptable PixelPH roleplay.
Create a believable character name that could reasonably exist in the setting. Meme names, celebrity copies, deliberate wordplay, and names designed only to provoke reactions may be rejected.
If staff determines that a character identity does not meet the city standard, follow the rename or character-review process provided through support.
Stay in character while a scene is active. A rule concern does not give either side permission to stop roleplay; complete the scene when possible and report it afterward.
A covered or convincingly disguised person cannot be identified solely because you recognize the player’s voice.
Do not disconnect to escape an active scene or its consequences. If a genuine crash or connection loss happens, notify the involved side through the approved support channel and return when possible.
Events from another FiveM city do not exist in PixelPH. Relationships, wars, debts, deaths, and information must be established here.
Whitelisted employees must look and act appropriate to their duty role. Whitelisted job access, confidential information, licenses, doors, or job mechanics may not be used to provide criminal organizations an unfair shortcut.
Aim for believable realism without turning scenes into impossible real-world simulations; GTA mechanics have limits, but obvious mechanical absurdities should still be avoided.
Keep real-life and administrative conversation out of active character scenes. Do not disguise OOC statements with coded phrases, locations, “thoughts,” or similar wording.
Knowingly breaking a rule because the mechanical result benefits you is still a violation even if you are willing to accept a later punishment.
If another side breaks character or a rule, continue the scene when reasonably possible and submit evidence afterward. One side’s violation does not authorize the other side to violate rules in return.
Administrative sanctions are OOC information. Your character cannot know that another player was banned, suspended, warned, or placed on an administrative cooldown unless there is a legitimate in-character explanation for their absence.
Describe only what your character could observe—for example, that someone has not been seen recently.
Do not publicly accuse players of cheating or staff misconduct without going through the evidence process. Capture the relevant context and submit it privately.
Do not announce that someone is staff while they are roleplaying. Their administrative role does not become character knowledge.
Discord messages, emails, clips, and other external material cannot be used as live-scene intelligence unless the information was delivered through an approved in-character system for that purpose.
Keep personal disputes and OOC drama away from character interactions.
Props and deployable objects must support a believable scene. Do not spam objects, block essential access without roleplay justification, create impossible structures, or use props to gain combat/visibility advantages.
Remove temporary objects when the scene is finished whenever the system allows it.
Pets and animal characters must be used in a way that fits the setting. They cannot be treated as disposable combat tools, scouts, blockers, or mechanic exploits.
Sexual assault and rape roleplay are prohibited. Content involving sexualization of minors is prohibited without exception.
Do not create a character whose entire purpose is repeated random murder, mass casualty scenes, or lethal “bounty hunting” with no meaningful story framework.
Staff may stop scenes that cross community-safety boundaries even when all participants claim they were “in character.”
Your character may act only on information learned through legitimate in-character experience or approved in-character systems.
Do not use streams, Discord, map watching, another character, spectator information, OOC conversations, or prior knowledge from outside PixelPH to locate people, identify plans, or make decisions.
Information must have a believable chain from the character who learned it to the character using it.
Do not force outcomes that deny another player a reasonable chance to respond, and do not exploit GTA/FiveM mechanics to perform actions your character could not plausibly accomplish.
Examples include abusing animations, restraints, carrying, geometry, inventory timing, vehicle mechanics, or scripted interactions to bypass an active roleplay response.
Use /me or the appropriate interaction system when an action requires the other player to understand or respond to what your character is doing.
Give other players room to participate. Robbery, conflict, interrogation, and confrontation should create a scene rather than reduce another player to a loot container or target.
Do not repeatedly hunt the same person, chain-force scenes, or use game systems only to deny another player meaningful roleplay.
Treat your character’s life as valuable. Serious threats, dangerous injuries, overwhelming force, and obvious tactical disadvantages should affect your decisions.
Do not choose suicidal actions merely because respawning is mechanically available. A believable character should seek survival unless the established story provides an exceptional reason otherwise.
When another party has clear control of a situation—such as a weapon trained on you at close range—respond to the danger realistically.
Do not draw a weapon, rush attackers, or manufacture an escape solely because the game allows a fast input when your character would reasonably fear immediate harm.
Fear RP does not require automatic surrender in every conflict; it requires decisions that match the actual risk, cover, distance, numbers, and established scene.
If you use the full respawn/forced-respawn route after being incapacitated, your character cannot remember the final events that directly caused that incapacitation and may not immediately return to continue the same conflict.
If EMS successfully treats and revives you within the scene, you may retain reasonable memory, but your injuries and medical treatment still matter.
Being deliberately disposed of in a way that forces a full respawn may justify a stronger memory loss. Extreme uses of this mechanic must have serious roleplay justification and remain subject to staff review.
Actions that ignore established context, manufacture conflict without believable cause, or use mechanics to shortcut the story may be treated as low-quality or failed roleplay.
The standard is not perfect realism; it is coherent character behavior, fair participation, and consequences that make sense inside the PixelPH world.
An unconscious character cannot hold a normal conversation. Use only the interaction methods specifically intended for medical roleplay.
After serious injury, roleplay the effects for roughly 10–30 minutes depending on severity and treatment. Do not leave the hospital and instantly seek revenge.
Do not return to the location of the same active conflict for at least one hour or while the scene remains active, whichever protects the continuity better.
When EMS asks for injury information through /me or an equivalent system, answer consistently with what happened. Do not use unconscious/downed states for taunting, dancing, or OOC trash talk.
Standards for escalation, criminal scenes, emergency services, crew limits, and restart protection.
Randomly attacking or killing another player without a valid roleplay build-up is prohibited. Vehicles cannot be used as weapons without a scene-based reason that makes the action believable.
Before lethal force, there must normally be clear interaction, escalation, or an established conflict that gives the other side a reasonable understanding of the danger.
A downed player cannot simply rejoin the same firefight after being revived or respawning unless the applicable recovery rules clearly allow it.
Gunplay should be the consequence of a story, not the default opening move. Verbal confrontation, demands, pursuit, negotiation, and other escalation should be used when the situation reasonably allows them.
Do not force a shootout because you want a PvP result. The scene should explain why lethal force became necessary.
EMS roleplay must be respected. Give medics time to assess, treat, transport, and document injuries without turning every medical interaction into a shortcut back to combat.
Do not pressure EMS to ignore injuries or revive players solely to continue an unfinished fight. Medical personnel must also avoid using job powers to unfairly influence criminal conflicts.
Police interactions must be played as roleplay scenes, not as a scoreboard between criminals and officers. Comply, negotiate, flee, resist, or escalate based on the actual situation and your character’s story.
Officers must use their job powers, information, and force within the city’s police procedures and the same general fairness standards that apply to other players.
Do not manufacture police attention solely to trigger a chase, shootout, or response. Repeatedly circling, taunting, ramming, or committing meaningless acts in front of officers for reaction is not valid escalation.
Plan criminal scenes with believable objectives and an exit strategy. Hostages must be genuine participants in the scene, not friends planted only to satisfy a mechanic.
Do not intercept another crew’s active heist simply to steal the mechanic or force PvP. Do not camp robbery locations waiting for someone else to start them.
If a location is designed as a robbable residence or business, owners cannot use ownership as a blanket immunity from the intended robbery system.
Keep POV/evidence from shortly before the heist through its conclusion when participating in major criminal scenes.
When a BOLO or investigation identifies your appearance, reasonable disguise changes are allowed; repeatedly transforming identity beyond believable limits to erase consequences is not.
Do not kidnap, rob, or intentionally take lethal action against the same player more than once within 12 hours unless both sides have agreed to continue an established story.
A planned escape should begin before choosing gunplay. If a second getaway method is part of the plan, allow a meaningful pursuit first; roughly 10–15 minutes is the expected minimum before switching when circumstances allow.
Small-scale heists should not rely on top-tier supercars purely to invalidate police pursuit. Once police have arrived, the active crew may not rotate extra people in, resupply from outsiders, or add new support to the scene.
Designated red zones may allow criminal-versus-criminal KOS under their specific rules; this does not create automatic KOS authority against police.
Standard PvP criminal activity is limited to four active participants on one side. Count everyone contributing to the scene: people inside, lookouts, radio support, hackers, getaway drivers, and outside shooters.
Automated heists may use a different participant limit only when the heist system or an official PixelPH rule explicitly states it.
Once the four-person scene is active, outside friends or organization members cannot feed live information, replace members, provide resupply, or join the confrontation.
Remain in character around scheduled restarts. A restart is not a reason to rush unfinished business, dump consequences, or start a scene that cannot reasonably conclude.
Do not begin non-automated illegal activity during the 30 minutes before or the 30 minutes after a scheduled restart. Automated timed content is exempt only where the system is specifically designed to run through that window.
A restart does not erase an active story, pursuit, debt, conflict status, or organization agreement. Resume appropriately after the server returns.
Do not use a vehicle trunk/raised trunk, animation state, or similar mechanic as artificial cover or protection during a fight.
Negotiation demands must be reasonable for the scale of the robbery and should create playable options for both criminals and police.
Saying that there are “no police online” is not an in-character justification for ignoring scene rules or starting otherwise restricted content.
Gambling may only use systems and locations approved by PixelPH and must remain compliant with FiveM/Cfx.re platform requirements.
Do not organize real-money wagers, external betting, or exchanges that convert in-city outcomes into real-world value.
Do not sit at hospitals, spawn points, heist locations, drug areas, trap houses, or other predictable hotspots solely to farm arrests, robberies, kills, or repeat interactions.
Police or groups should not hold an illegal location for more than about 15 minutes solely waiting for someone to appear without prior roleplay or investigative reason.
Do not log out or spawn around property/illegal locations to gain positional advantage. After a major fight, allow the other side to receive treatment and avoid provoking the same side for at least one hour.
Rules for recognized groups, leadership, representation, territory, partnerships, and organized conflict.
Organizations must use fictional identities appropriate to PixelPH. Names and branding of real-world criminal gangs, militias, terrorist groups, or syndicates are not allowed.
A newly recognized organization enters a 30-day probation period. During probation, two organization-related strikes may lead to disbandment or an extended probation, depending on staff review.
New groups are expected to build contacts, suppliers, reputation, and influence through roleplay rather than receiving instant access to the criminal ecosystem.
Repeated group violations can lead to organization sanctions or termination. Confirmed involvement of multiple members in cheating, exploit abuse, or unauthorized real-money trading may trigger immediate termination and loss of organization perks.
Passing probation does not guarantee permanent recognition; staff may consider roleplay quality, consistency, and activity.
Organization leaders are accountable for the culture they create and the people they formally bring into the group.
Leaders are expected to explain city rules, control organized scenes, and address members who repeatedly create violations. Depending on the incident, sanctions may apply to the individual, leadership, or the organization as a whole.
An established organization must maintain at least six active members.
Members with fewer than 200 hours of meaningful city playtime may not participate in organization shootouts or other major gang scenes. Staff may also review recent activity and idle patterns rather than relying on a single displayed hour count.
Long-term inactivity can result in loss of recognition, turf, or spray access. Turf itself cannot be sold.
Prospective members may socialize and build a recruitment story, but they cannot be rushed into major organization conflicts. Formal access to the organization/turf marks recognized membership.
Only members who were genuinely active before a conflict may participate in an organization war; players returning only for the war are not eligible. As a guide, staff may review activity during the prior week.
Each organization should maintain a consistent visual identity for formal conflict, including its approved colors and one primary conflict mask/representation. Custom organization masks require staff approval.
During an agreed organization war, participating members must use the declared representation so both sides can identify combatants. Vehicles used as formal war vehicles should follow the organization’s declared color scheme.
Do not lend your conflict identity to outsiders so they can masquerade as participants. If both groups use similar colors, choose additional clothing distinctions before engagement.
An organization’s first spray/marking should establish its home territory before expansion outward. Markings must be visible, plausible, and placed without abusing service vehicles or impossible locations.
Players who are not part of a recognized turf organization may not remove organization markings. Rival groups should not erase markings casually; removal should follow roleplay escalation and can serve as a formal step toward conflict.
Government property cannot be claimed through sprays. Business owners may remove markings placed on or immediately around their establishment.
A turf organization may use up to six members to defend criminal activity occurring inside territory it actively protects, even when the attacking criminal crew is subject to the standard four-person limit. A group cannot both claim protection of a local robbable location and repeatedly rob that same protected location itself.
For a robbable location inside your turf, choose a consistent stance: actively protect it with the territory-defense allowance, or leave it open to everyone including rivals.
Treat a recognized main turf as an inhabited stronghold even when only a few members are mechanically online. Do not drag unrelated conflict into another group’s home turf simply to exploit online numbers. Staff may adjust or remove turf when needed for balance or roleplay quality.
Organization wars require continuing roleplay between the involved groups. The leaders should establish who is participating, how contact will occur, and what conflict conditions are understood.
If a group deliberately avoids all meaningful interaction for five days while a formal conflict remains active, staff may treat it as conflict evasion. Public social-media posts by themselves do not count as meaningful engagement.
Any punishment length for conflict evasion is determined by staff based on the case; PixelPH does not publish a placeholder sanction value.
Formal organization-war engagements use either a six-person or ten-person roster per side. The chosen roster covers all radio communication, live information, scouting, tips, and direct combat support for that engagement; outsiders cannot contribute.
Intermediate 7v7, 8v8, and 9v9 war formats are not used under this framework. If a side cannot field the agreed maximum, leaders should resolve the format before engagement rather than adding people mid-scene.
KOS between the two organizations exists only when both sides have explicitly agreed to it and participants are wearing the declared organization representation.
The opening conflict scene should begin with interaction. A formal “talk” meeting uses the six-person roster and full representation. Kidnapping, hunting, or smaller conversational setups remain under the standard four-person criminal limit unless another official rule applies.
A war does not require constant fighting. Either side may pause for the day; do not force repeated shootouts simply because the conflict is active. The tension and consequences should continue through roleplay between engagements.
A formal organization war needs a developed in-character reason. Petty provocation, deliberate baiting, or a random RDM/VDM incident is not enough by itself to justify a war.
Wars must have a defined path to conclusion and cannot run indefinitely. The active war period may not exceed five days unless staff explicitly approves a story exception.
Winning a fight does not authorize humiliation of downed players. No repeated mag-dumping of bodies, dance/emote taunting, OOC insults, or hospital camping. Give the opposing side at least one hour to recover before seeking another direct engagement.
Vehicle contact must remain proportionate to the scene. Repeated or deliberately destructive ramming that disregards survival is prohibited. Raised trunks or similar vehicle states cannot be used as artificial combat cover.
Alliances must grow from actual roleplay and cannot be created overnight simply to gain numbers in a war.
Partnerships should be temporary rather than permanent power blocs; a relationship built over roughly one to two months is a reasonable benchmark for a meaningful alliance.
If an allied organization will participate in an active war, the opposing organization must be informed through the agreed conflict process.
Entering another player’s or organization’s private property carries risk. Owners may use reasonable force to defend themselves and the property when the intrusion creates a credible threat.
Police entry into organization property requires the same lawful in-character basis expected for other searches, such as probable cause, a valid warrant, or an immediate legal exception supported by the scene.
A conflict with police does not automatically become an unrestricted organization war. Any escalation must arise from the actual police action and remain subject to city rules.
A third organization may enter an active organization war only as a genuine third party. It cannot secretly function as reinforcements for one side; if it joins as a third party, both original organizations are treated as opposing forces.
Do not enter another organization’s territory solely to manufacture a shootout, repeatedly taunt members into firing, or force escalation over trivial reasons.
Police may lawfully observe and patrol organization areas for profiling or investigative roleplay when they have a legitimate in-character purpose. Presence alone is not gang baiting.
How to report issues, provide evidence, use support channels, and follow platform requirements.
PixelPH staff can assist with rule questions, technical problems, reports, and suggestions. Staff members are volunteers, so non-urgent cases may take time.
Provide complete context and allow the assigned staff member to review the case rather than opening parallel conversations with multiple staff members.
Open one ticket per issue and keep updates inside that ticket. Do not DM or call staff directly unless a staff member has invited you to do so.
For player reports, use HOME to capture the player ID when possible and submit the relevant context, video, screenshots, or links. Evidence should normally be provided within 24 hours of the incident.
Tickets must remain civil. Both sides may explain their perspective, and staff may move discussion to voice when clarification is useful.
You may report a scene you witnessed even if you were not a direct participant, provided you have usable evidence and enough context for investigation.
Appeal eligibility depends on the sanction notice. Staff will not disclose another player’s private sanction details, and ticket contents should not be redistributed publicly.
For an active in-city technical issue, use the approved OOC/help method with a short factual description without derailing the roleplay around you.
Refund requests caused by bugs, desync, or unexpected system failure must follow the evidence and refund process published in the PixelPH guide/support channels.
PixelPH operates under the rules of the FiveM/Cfx.re platform and applicable Rockstar policies. Platform requirements take priority over any local rule that conflicts with them.
This includes restrictions involving monetization, intellectual property, cheating, exploits, real-money transactions, gambling, safety, and acceptable platform use.
Platform violations may lead to PixelPH sanctions in addition to any action taken by Cfx.re or Rockstar. Refer to the official platform policy pages for the current requirements.
