DarkflameServer/dGame/dPropertyBehaviors/ControlBehaviorMessages/AddMessage.cpp

#include "AddMessage.h"

AddMessage::AddMessage(AMFArrayValue* arguments) : BehaviorMessageBase(arguments) {
	behaviorIndex = 0;
	auto* behaviorIndexValue = arguments->Get<double>("BehaviorIndex");

	if (!behaviorIndexValue) return;

	behaviorIndex = static_cast<uint32_t>(behaviorIndexValue->GetValue());
	Game::logger->LogDebug("AddMessage", "behaviorId %i index %i", behaviorId, behaviorIndex);
}
Further implement Property Behavior parsing (#936) Further implements the ControlBehavior processing and adds preparations for cheat detection 2023-02-14 02:55:44 +00:00			`#include "AddMessage.h"`

Make ControlBehavior messages far more modular (#991) * Make case consistent * How modular can you go? Holy modular * Add comments * Initialize values 2023-02-16 17:30:33 +00:00			`AddMessage::AddMessage(AMFArrayValue* arguments) : BehaviorMessageBase(arguments) {`
Further implement Property Behavior parsing (#936) Further implements the ControlBehavior processing and adds preparations for cheat detection 2023-02-14 02:55:44 +00:00			`behaviorIndex = 0;`
Refactor: Amf3 implementation (#998) * Update AMFDeserializeTests.cpp Redo Amf3 functionality Overhaul the whole thing due to it being outdated and clunky to use Sometimes you want to keep the value Update AMFDeserializeTests.cpp * Fix enum and constructors Correct enum to a class and simplify names. Add a proper default constructor * Update MasterServer.cpp * Fix bugs and add more tests * Refactor: AMF with templates in mind - Remove hard coded bodge - Use templates and generics to allow for much looser typing and strengthened implementation - Move code into header only implementation for portability Refactor: Convert AMF implementation to templates - Rip out previous implementation - Remove all extraneous terminology - Add proper overloads for all types of inserts - Fix up tests and codebase * Fix compiler errors * Check for null first * Add specialization for const char* * Update tests for new template specialization * Switch BitStream to use references * Rename files * Check enum bounds on deserialize I did this on a phone 2023-05-13 22:22:00 +00:00			`auto* behaviorIndexValue = arguments->Get<double>("BehaviorIndex");`
Further implement Property Behavior parsing (#936) Further implements the ControlBehavior processing and adds preparations for cheat detection 2023-02-14 02:55:44 +00:00
			`if (!behaviorIndexValue) return;`

Refactor: Amf3 implementation (#998) * Update AMFDeserializeTests.cpp Redo Amf3 functionality Overhaul the whole thing due to it being outdated and clunky to use Sometimes you want to keep the value Update AMFDeserializeTests.cpp * Fix enum and constructors Correct enum to a class and simplify names. Add a proper default constructor * Update MasterServer.cpp * Fix bugs and add more tests * Refactor: AMF with templates in mind - Remove hard coded bodge - Use templates and generics to allow for much looser typing and strengthened implementation - Move code into header only implementation for portability Refactor: Convert AMF implementation to templates - Rip out previous implementation - Remove all extraneous terminology - Add proper overloads for all types of inserts - Fix up tests and codebase * Fix compiler errors * Check for null first * Add specialization for const char* * Update tests for new template specialization * Switch BitStream to use references * Rename files * Check enum bounds on deserialize I did this on a phone 2023-05-13 22:22:00 +00:00			`behaviorIndex = static_cast<uint32_t>(behaviorIndexValue->GetValue());`
Make ControlBehavior messages far more modular (#991) * Make case consistent * How modular can you go? Holy modular * Add comments * Initialize values 2023-02-16 17:30:33 +00:00			`Game::logger->LogDebug("AddMessage", "behaviorId %i index %i", behaviorId, behaviorIndex);`
Further implement Property Behavior parsing (#936) Further implements the ControlBehavior processing and adds preparations for cheat detection 2023-02-14 02:55:44 +00:00			`}`