From 5b3b9c18554e819b2c88e22c43e38cd63333f151 Mon Sep 17 00:00:00 2001 From: Lucas Date: Mon, 21 Jul 2025 08:31:58 +0000 Subject: [PATCH] code syntax --- Home.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Home.md b/Home.md index 85206c0..4c99634 100644 --- a/Home.md +++ b/Home.md @@ -15,13 +15,13 @@ Unless you type.new() after preloading the script, which creates a new instance An interface is required to access a module, making a module process by itself some logic is possible, but it cannot store any values on itself (this is a limitation we imposed to be more perfomant), so everything must be fed to these modules as an argument through the functions. A module can 'manage' indirectly something by giving a procedure to follow always, this assure they will work with a pre-defined values and behaviors. -For instance, one can add meta-data to any Object derivated class in Godot, we can use it to store information for this module or even for other modules, this way we can later track and adjust the correct wanted behavior for our module functionality, but keep the variables only in one place, avoiding multiple .new() instances of a script. +For instance, one can add meta-data to any Object derivated class in Godot, we can use it to store information for this module or even for other modules, this way we can later track and adjust the correct wanted behavior for our module functionality, but keep the variables only in one place, avoiding multiple `.new()` instances of a script. We can keep track of metadata constants in a separate class to not mess things up, whenever we change those constants they should be updated for all modules. **NOTICE**: **Modules should avoid interacting with other modules**, they don't do nothing by themselves, we want a library of books, a book shouldn't read other books, but someone could go pick a book and use it. This is an imposed limitation. -- If we want only functions to be applied we shouldn't do .new() after loading a script. (Only use Static Functions) -- If we want a script to hold variables then we should do .new() to create a instance of it. (Can use and store variables outside Function Scope) +- If we want only functions to be applied we shouldn't do `.new()` after loading a script. (Only use Static Functions) +- If we want a script to hold variables then we should do `.new()` to create a instance of it. (Can use and store variables outside Function Scope) ![graph](module_example.webp)