OpenFusion/src/CustomCommands.hpp

#pragma once

#include "core/Core.hpp"

#include <string>

namespace CustomCommands {
    void init();

    bool runCmd(std::string full, CNSocket* sock);
};
[refactor] Refactor ChatManager * Extracted all commands into CustomCommands.cpp * Moved all chat-related packet handlers into ChatManger.cpp * Cleaned up redundant includes * Unified handler naming scheme * Made all command handlers in CustomCommands.cpp static 2021-03-12 19:07:26 +00:00			`#pragma once`

[refactor] Move files to core/ and servers/ subdirectories CNProtocol, CNShared, CNStructs and Defines are now in core/. CNLoginServer, CNShardServer and Monitor are now in servers/. core/Core.hpp wraps all the core headers except for CNShared.hpp. Defines.cpp has been renamed to Packets.cpp, and so has its corresponding namespace, but not the header file. This is in preparation for upcoming changes. 2021-03-17 19:07:40 +00:00			`#include "core/Core.hpp"`
[refactor] Refactor ChatManager * Extracted all commands into CustomCommands.cpp * Moved all chat-related packet handlers into ChatManger.cpp * Cleaned up redundant includes * Unified handler naming scheme * Made all command handlers in CustomCommands.cpp static 2021-03-12 19:07:26 +00:00
The great re-`#include` Was getting frustrated by the inconsistency in our include statements, which were causing me problems. As a result, I went through and manually re-organized every include statement in non-core files. I'm just gonna copy my rant from Discord: FOR HEADER FILES (.hpp): - everything you use IN THE HEADER must be EXPLICITLY INCLUDED with the exception of things that fall under Core.hpp - you may NOT include ANYTHING ELSE FOR SOURCE FILES (.cpp): - you can #include whatever you want as long as the partner header is included first - anything that gets included by another include is fair game - redundant includes are ok because they'll be harmless AS LONG AS our header files stay lean. the point of this is NOT to optimize the number of includes used all around or make things more efficient necessarily. it's to improve readability & coherence and make it easier to avoid cyclical issues 2022-07-16 23:19:40 +00:00			`#include <string>`

[refactor] Refactor ChatManager * Extracted all commands into CustomCommands.cpp * Moved all chat-related packet handlers into ChatManger.cpp * Cleaned up redundant includes * Unified handler naming scheme * Made all command handlers in CustomCommands.cpp static 2021-03-12 19:07:26 +00:00			`namespace CustomCommands {`
			`void init();`

			`bool runCmd(std::string full, CNSocket* sock);`
			`};`