lpc-coding-style

What problem does it solve?

LPC coding style and formatting conventions ensure that all LPC work in the oxidus-mudlib project adheres to a single, readable standard, reducing onboarding time and merge conflicts.

Core Features & Use Cases

• Spacing and indentation rules (2 spaces, no trailing spaces, single trailing newline).
• Bracing style, control-flow formatting, and idiomatic LPC patterns to improve readability.
• Naming conventions and access modifiers (camelCase, private by default, __ prefix for file-global vars) plus documentation conventions.
• Use Case: When starting a new LPC object or updating existing modules, consult this guide to align with project conventions.

Quick Start

Consult this guide before writing or modifying any LPC code to ensure consistent project-wide style.