From b7aa25b48e06a803d70672f8e0b1b6e63e09ec44 Mon Sep 17 00:00:00 2001 From: Ben Forge <74168521+BenCheung0422@users.noreply.github.com> Date: Wed, 25 Mar 2026 04:07:15 +0800 Subject: [PATCH] EFP 14: Create: Feature Enabling Platform (FEP) --- efp/efp014/main.xml | 41 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 efp/efp014/main.xml diff --git a/efp/efp014/main.xml b/efp/efp014/main.xml new file mode 100644 index 0000000..137fa0b --- /dev/null +++ b/efp/efp014/main.xml @@ -0,0 +1,41 @@ + + + + + + + + +
+ +

+ Due to the mechanisms and properties of TerraModulus, resulting games produced based on it may be + across several genres from sandbox survival to closed world role-playing. Therefore, ensuring + the potentials of mechanisms being feasible to be implemented is important. Thus, FEPs should be + proposed to confirm the possibilities of features or interfaces of certain functionalities. +

+ +
+
+ +

+ When proposing FEPs, most likely those would be outlines on about what kinds of features shall + be implemented and supported. However, certain working examples may also be available to examine + whether the requirements of an FEP proposal are fulfilled to complete. + Also, since those exact features and requirements are likely subject to change and update, they + may not be proposed via EFPs but filed Repository Issues. +

+

+ Works about a certain FEP should be done on the corresponding Issue. Only authorized Team Members + are allowed to file such FEP tracking Issues, but other Community Members are allowed to propose + FEP drafts and Team Members may formally file a FEP Issue aligning and possibly extending the drafts. +

+

+ When FEPs are completed, they may be standardized and informed via EFPs. Extensions of such FEPs + may rely on new FEPs or updating EFPs, for further features and functionalities. +

+ +
+ +