From 13fdaafd002bd85072a5301e2db36838b662b38a Mon Sep 17 00:00:00 2001 From: Blixibon Date: Sat, 30 Nov 2019 15:12:14 -0600 Subject: [PATCH] Created Prefabs and workarounds obsoleted by Mapbase (markdown) --- Prefabs-and-workarounds-obsoleted-by-Mapbase.md | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 Prefabs-and-workarounds-obsoleted-by-Mapbase.md diff --git a/Prefabs-and-workarounds-obsoleted-by-Mapbase.md b/Prefabs-and-workarounds-obsoleted-by-Mapbase.md new file mode 100644 index 0000000..02d148d --- /dev/null +++ b/Prefabs-and-workarounds-obsoleted-by-Mapbase.md @@ -0,0 +1,10 @@ +This article is supposed to list common prefabs and workarounds that have been changed or obsoleted by Mapbase. This article exists to ensure mappers understand how Mapbase changes their workflow and encourage the usage of the new features. + + +## AddOutput-related + +`AddOutput` is normally used for adding outputs, but it's also capable of setting any keyvalue after the entity has spawned. This is used to change several keyvalues that could not be changed manually by other means after spawning. + +Mapbase adds corresponding inputs to some keyvalues, meaning `AddOutput` wouldn't need to be used in those cases anymore, but not every keyvalue has a corresponding input and `AddOutput` should continue to be standard practice. In fact, using `AddOutput` has been made more flexible thanks to the new `logic_format` entity, which allows the key and value to be set independently. + +(todo) \ No newline at end of file