Skip to content

Repository files navigation

PleX Code Banner

2026 UPDATE

This Repo is in the process of recovery and development. some of the Table of Contents might be missing or broken. I had dealt with Repo Corruption and AI screwed me over. Very Angy Dev Please be patient with me during this period of recovery, dispite certain buttons and pages not working this project has been developed and maintained by **JUST** me.

If you want to help sponsor this project and what to help feel free reatch out

Donate using Liberapay

The Core Philosophy

Tip

PleX is NCOM’s native programming language.
It does not follow traditional programming models or derive from existing languages like C or Python.
Instead, PleX was designed from the ground up as a direct interface between software logic and physical systems.

Important Distinction

Caution

This is NOT the old 1970s Ericsson PLEX language used in telecom switches. PleX is 100% new, modern, and unrelated.
The name comes from “Complex” — simplified into a language that feels direct, physical, and intentional.

Caution

.plxcode files ARE NOT Perl Files .plxcode will be seen as NCOM Systems Programming Language. Perl will Not be allowed to press legal suit from NCOM Systems class distinction that separates from ".plx perl files"

Permitted Use

You are granted a limited, non-exclusive, non-transferable right to view this repository for personal, non-commercial use only.

📋 Table of Contents

Needed Assets/Libraries


The "Deliberate" Doctrine

  • Deliberate NOT Assumed: All commands are direct seizures of hardware. Nothing is implied.
  • Possession vs. Variable: You do not "declare variables" to hold data. You "possess" (Argu~!!) a physical hardware lane.
  • Top-Down Possession: Scripts act as a "Hail" (handshake) to the system and end with an "Execute/Sign" (locking the state).
  • Inert Hardware: The system assumes the machine is "stupid" and inert. It will do nothing until forced by a "Bolt" (~!!).

The "Zero Experience" Advantage

The creator had no prior coding experience, avoiding traps like "loops" or "if/then" statements. Instead, they built a system based on Intent, Possession, and Force.

  • No Memory Leaks: Lanes are physically occupied (Possessed). They cannot leak because they are "held" until signed off.
  • No Syntax Errors: Kinetic Input ensures the shorthand (|__>) always expands to the correct logic symbol (╰──➤).

BEHOLD THE "╰──➤"

Note

The Power behind this character carries more meaning and use then thought!

"╰──➤" can mean
WHEN
IF
THEN
FI
OR
ELSE
BUT
FOR
GET

Caution

You will NEVER Find ╰──➤ by itself!

Note

you will ALWAYS Find it "Paired" with a "header/bolt command!

Examples

Build | UI
╰──➤ images
╰──➤ Buttons 

OR

Hail | Logic 
╰──➤ Argu~!! ...

OR

Import | @assets
╰──➤ /!! markdown

OR

UI | Nav Bar
╰──➤ pill-shapped ( corners rounded = 24x )

Kinetic Input & Vocabulary

Tip

Plex uses "Kinetic Shorthand"—rapid keystrokes that the Plex’er (background layer) instantly transforms into geometric glyphs. This map represents a physical path for electricity.

The Glyphs

Glyph / Command Description
Build~ Preparation command similar to import. Signals the system to prepare for file creation or check for updates before execution.
Build~!! Absolute build command. Forces the system to immediately execute the build or import operation.
~!! Directive operator. Functions like a priority override (similar to sudo). Forces a command to execute immediately rather than being treated as a suggestion.
Hail~!! Pull-active declaration. Instructs the system to prepare and retrieve any resources required for the next command.
Call~!! State check command used to verify files, resources, or system actions.
Sign~!! Authentication command. Requires an .attributes file to store official signatures and identity data.
Argu~!! Defines logical arguments or structured reasoning inputs.
Math~!! Declares a mathematical logic block or computation.
Sniff~!! Search or scan command, typically used for detecting or querying physical sensors.
|~| Link operator. Connects logic to a specific attribute, state, or data reference.
|!!| Hard-guard operator used to prevent invalid calls, logic conflicts, or execution errors.
╰──➤ Flow operator that defines execution paths. Used for hierarchical command structures and logical branching (replacing constructs like IF, AND, OR, WHEN).
╰──| Output operator. Emits or returns system feedback or results.
Mark~!! Bundle pulse command that communicates directly with hardware layers. Often auto-corrects to |~|~!!.
Show~!! Display command combining output and visualization (similar to print + display).
UI~!! Declares a graphical interface block.
Pulse~!! Direct signal transmission command, typically used with send | Pulse~!!.
\\\ Direct shell command invocation.
Logic~!! Declares a direct logical state or evaluation block.
Store~!! Command used to store data or state information.
@ Reference operator used to mention or access a file (example: @.attributes).
Panel~!! UI component command used within UI~!! blocks.
Check~!! Validation command used to confirm system state, arguments, or logic correctness.
TAG~!! Creates a .TAG file used for metadata or signature storage.
Link~!! Link command automatically normalized to |~|~!!.
Script~!! Runs a specified range of lines from code. Example: Script | [1-16] RUN.
[""] Represents an empty value or placeholder field.
Bundle~!! Groups multiple commands into a structured execution bundle.
/!! Comment or notes marker similar to code comments.

Caution

now there are certain commands that will automatically be autocorrected!

Origital Command Autocorrected
Link~!! To |~| an exsption it may change to |~|~!! this would be used as a safeguard where it will have safty handle "optional"
Hail~!! To Hail |
Build~!! To Build |
Show~!! To Show |
Send~!! To Send |
Bundle~!! To Bundle |

Caution

Pulse~!! will be the ONLY exception to this rule because it is a dirrect metal command where you may see n~.

Pulse~!! n~ /f |~| @0xFAF1_NF-0

where it will register as:

n~ |~| @0xFAF1_NF-0

this is beause it has send a dirrect pulse to the CPU as a packet via channel line

The Dictionary of Force

  • Sniff: scan or search for phisical devices or components
Sniff | Devices[Local]
╰──➤ Bluetooth [@_TI-Bluetooth-comp](|~|~!! @_#c.e22ld_K[LC])
  • Hail: The initial handshake call to a system. this tells fetch something simular to Sudo or Winget or pacman.

Architecture: Brain, Body, and Manifesto

Plex separates logic from physicality to allow universal compatibility.

  1. .plx (The Brain): this is NCOM's official programming language filetype.
  2. .attributes (The Body): acts as a address book for links, arguments, and assets like images ext. the use case of this serves better without having to find every single stupid link or asset with just using @attributes where it will grab that needed asset EXT:
Hail | @attributes
╰──➤ |~| GlassUI.khon
  1. .mf (The Manifesto): A sparse virtualization index. It uses "Zero-Copy Access," pointing to data offsets on the disk rather than loading files into RAM.
  2. .bun OR .Retard (The Bundle): Compressed raw data streams, often used to store math code or logic states. this is filetype is act as a way to tell the PC, "Hey don't screw this up stupid" it uses this as a zero trust basis to prevent any errors EXP:
Math | Logic
╰──➤ Argu~!! 
   ╰──➤ X | Value 
   ╰──➤ Y | Value
   ╰──➤ X | 2
   ╰──➤ Y | 4
╰──➤ Argu~!!
   ╰──➤ X + Y | 8
   ╰──➤ 8 | x + Y 
   ╰──➤ 8 | combined value

About

a brand-new programming language built for direct intent commands - site is broken

Topics

Resources

Code of conduct

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Sponsor this project

Packages

Contributors

Languages