» Advertisement «

by Joseph "Greypawn" Pishgar

PREFACE

It has been brought to my attention through the perseverance of individual hierarchical entities functioning within the confines of the system that there is a distinct and marked lack of dissemination of empirical information regarding the discipline you refer to as “The Coder”.  This lapse in foresight on the part of Zion is not unexpected, but nevertheless mildly irritating.  Inasmuch as I am disinclined to impart statistical and systemic information, I am reluctant to withhold the aforementioned due in part primarily to the strain placed on an otherwise efficient database dynamic by less… informed initiates.

Initially, the existence of a Coder within the system is not geared towards the lesser being, as construct and substance must be maintained within given parameters or incidents may precipitate unfortunate situations.  True mastery of the general art of “coding” is not common among humankind, primarily due their predilection for physical constraints and dross unwillingness to engage in perception beyond the normal boundaries of such materialistic trappings.   Definitive quantities of temporal investment must, in stride, be made towards progress in the field of code manipulation; however, I am certain that you will find the resultant abilities of construction applicable to your personal situation and aspirations.

If you find yourself questioning the relevance of the delineated release of this information, remain aware that this coda serves a solitary purpose.  That is, to facilitate the frictionless acclimatization of novice Coders to the precise design mechanic of “Coding”, and you may of course, discontinue your digestion of this document’s contents at any time.  Do remain cognizant however; failure to comply with the guidelines illustrated herein will only ultimately result in rampant personal mediocrity.

Firstly, a large proportion of the newly realized have misinterpreted previously established definitions for what the coding system of the Matrix is and how it works.  While I cannot fault societal linguists for their lapse in grammatical acumen, I can lay to rest a nominal selection of verbiage.  I will temporarily dispense with higher phraseology towards this end.

TERMS

Coder-

An individual in possession of the majority of the abilities that lie within the Coder discipline.

Code-

1. Verb: To activate and utilize the abilities of a Coder.

2. Noun: An item which is fashioned after compiling the fragments and subroutines which can then be used or compiled to make real items within the Matrix.  There are two types of code that can be used; Item Code and Ability Code.  Item Codes usually have multiple charges and can be used to compile more than one usable item from.  Ability Codes the same Ability Codes you load into memory that allow access to more abilities and disciplines.

Code Bit: Numerically designated item procured from missions and enemies killed, or purchased from a vendor.  Code Bits are the basic resources required for “Code Fragments” and “Subroutines”.

Code Fragment:  A glyphic item that is created from Code Bits or looted and is one of the required resources of an Item or Ability Code.

Subroutine:  A different variety of code fragment, specific to the type of item or ability code being created.

Compile:  The method by which a Code Fragment  or Subroutine is created from Code Bits, and also how Ability Codes and Item Codes are created from Code Fragments and Subroutines, as well as the act of using the “charges” on an Item Code to make an item.

Decompile:  Performed with the Decompiler Tool, decompiling allows the Coder the chance to learn the Recipe for an item, as well as turning unusable items into usable Code Fragments, Subroutines, or Bits, if the recipe is already known.

Recipe:  Knowledge of how to compile things and the requirements.  Some Recipes are granted as ability levels in Write Code grow, while others must be learned from decompiling items within the Matrix.

MODUS OPERANDI

Fundamentally, creation and destruction of everything existing within a non-static state within the Matrix has been the under the purview of the system, though this quintessential feature may prevent catastrophic alterations to primary code, it does not prevent minor ones, whose propagation is the sole aims of the “Coder”.  Fashioning usable material within the Matrix is simply a matter of allocating enough resources and determining a functional course of action. 

Every “Coder” that would pursue the advancement of technique should have in possession three essential elements of the discipline.  The Code Analyzer, The Compiler Tool, and the Decompiler Tool are integral to the activities of a Coder seeking to formulate even the most simplistic of Matrix equations, let alone forge a perceivable aspect of the system into being.  It is standard practice to retain each of these devices within a short-cut based system, such as the Hotbar.  Commencement of coding should begin with the activation of The Code Analyzer, which will permit access to a searchable information panel displaying the various forms of possible craftables available.  At this juncture, the “Coder” may initiate construction of Code Fragments or Subroutines out of Code Bits.  In addition, any selectable item that can be created will display its necessary requisite resources in the bottom-right of the Code Analyzer display.  “Right-clicking” on these requisites can allow the “Coder” a shortcut to fashioning the needed fundamental elements of whatever desired code, finalizing the task by selecting Compile after the fragments and subroutines have been actualized.

Following this protocol will consume a predetermined nominal quantity of $Information, as it is integral to the process.  Code is produced utilizing this method.  The Compiler Tool or the Loading Area will facilitate the production of the actual item of substance.  Item Code is constructed with a predetermined quantity of charges, usable for creating up to, but not to exceed the number of allocated items.  Ability Code however, is produced ready to execute and load into available memory.  Compiling within the confines of the system of the Matrix will result in an increased $Information cost and failure rating as opposed to the Loading Area, as this is designed to assuage additional systemic anomalies. 

Supplementary Recipes apart from the predetermined ones gained through ability enhancement must be procured through the proficient employment of the Decompiler Tool.  A learned Coder will avail himself of the Decompiler at every given turn, utilizing its pragmatic ability to consume an item an in turn, bestow the knowledge of the recipe of creating the aforementioned item or select resources in the form of Code Bits or Subroutines if such a recipe is already possessed.  As per executable parameters, every compile-able piece of code must have one class code fragment and one subroutine, with varying quantities of additional fragments as necessity deems, based solely on the level of the item in question.

Bear in mind, these are indistinct prefigures regarding the overarching subjective science of code manipulation, primarily focused on materializing desired additions.  Of course, for the purposes of summation, this primitive, extensively abridged synopsis will do.  I cordially solicit and encourage addendums to this work.

MAXIMS (tips)

Conduct Coding operations in gratis for fellow Matrix denizens.  Offering the services of a “Coder” for basic resource and $Information costs will increase your proficiency in the applicable skills.  Concordantly, it will amass you a measure of the distinctly human disillusionment, primarily being… notoriety.

Remain close to Hardlines, as doing so will permit expedited egress to Loading Areas, where code can more reliably be transmogrified into items.

Everything you do not personally utilize should be immediately processed through the Decompiler Tool.  Doing so as habit will precipitate a robust collection of recipes and the emergence of a resource stockpile over time.