#Rename #game-features-system to #game-features-plugin
1 messages · Page 1 of 1 (latest)
Thanks for the suggestion. I've been thinking about renaming that channel, but I wasn't sure what would be most intuitive to the people using it. This suggestion is worth considering.
Bumping this 😅 70% of people message in the channel thinking it’s about general game feature systems, not the game feature plugin
Well it's not about "the game feature plugin", it's for using "game feature plugins".
I could be wrong but going off the channel description it is for UE5's GameFeature plugin
and if you did want to name it for the plugin that's the parent of all game feature plugins then the name would be "Game Features" which would cause even more confusion
and it was opened up for the UE5 game feature plugin
What are the sub-game feature plugins you're referring to?
You're not understanding..... A game feature plugin is a type of plugin in UE5 not the name of a specific plugin
they are defined by an engine plugin called "Game Features", but that channel is about how to use Game Feature Plugins not about the Game Features plugin
Oh I see what you're saying. The channel was opened up to discuss the GameFeatures plugin
It does encompass discussion around usages of the plugin as well though, like the modular gameplay plugin
well I'm actually saying it's about how to make your own Game Feature Plugin and not about the Game Features plugin
No it doesn't.... Modular Gameplay is another unrelated plugin and we have a channel for it too #modular-gameplay-plugin
This Plugin works hand in hand with the "Modular Gameplay Plugin". It allows you to create "Game Features", which can be loaded runtime and utilize actions to extend the game on a modular basis.
I'm just going off the description they gave the channel, which encompasses how to create them, utilize them, and its usages with the modular gameplay plugin
Modular Gameplay is another unrelated plugin
This servers channel announcement talks about how its related to modular gameplay plugin, and the documentation for game features talks about them side by side
They are used together often, but they are separate concepts and don't intrinsically have anything to do with each other
Yes I don't think I said they were?
This post was primarily bringing attention to the current name being misleading to newcomers, so even if you can defend the current name it's still bringing in the incorrect audience. I'm completely open to other name ideas
It's just been shown the current name isn't working
It does encompass discussion around usages of the plugin as well though, like the modular gameplay plugin
No if you post about Modular Gameplay in #game-features-system you're off topic and that belongs in #modular-gameplay-plugin
Just saying
That's fair I was wrong with what I said
Though wouldn't your point further the reason to call it something like #game-features-plugin?
Also we've known the name is sub-optimial since the channel was made, these names were considered initially and thought to be more confusing:
-
game-features - The thought was people would not understand what this meant at all
-
game-feature-plugins - The thought was people would think this was about a specific existing plugin (like you did)
So they went with game-feature-system to hopefully encompass the concept of user made GFPs and anything about their structure (such as the GFP specifc Data Asset in the plugin root)
So I'm not disagreeing with you, but it's a bit more complicated than you're framing it imo
What would not make sense with #game-features-plugin?
It specifies the exact plugin name to have discussion around
(Which is what I was originally trying to explain and give an example for, but I didn't realize the engine plugin was GameFeatures and not GameFeature)
I'm not saying these are my opinions... I'm just summing up the conversation from when the channel got made
Yeah....Epic should've come up with a better name for it that's less generic lol
woah blast form the past.... remember when you thought it was Lyra specific haha
Sorry trying to find the orignal convo for you
This is the thread where they got decided on:
#970067961345896488 message
It's a bunch of back and forth and we're both present, but you can go back and relive the magic if you want.
I will say my point to that was saying Lyra added new extensions to the GameFeatures plugin (New GameFeatureAction's), but I could've worded it better
I remember the conversation still and just re-read it... that is not what you were saying...
Not that it matters.
Yes Lyra has some custom Game Feature Action classes specific to that project, which is the same as any project using Game Feature plugins.
The idea is you create Game Feature Action classes to extend the action list in the Game Feature Data Asset with project specific actions.
Lyra is just an example for how to use these (and many other) systems... how good a job it does at that is up for debate
The issue is that many people (not just you) get confused and think these engine plugins that they show off the usage of are somehow related to Lyra
Maybe for these PLUGIN Channels it might make sense to prefix them instead of suffix'ing them
Didn't read the prev messages, but just thought about it
Would be nice if discord allowed some tagging of channels, so it shows in a bit of different text style:
# Tag channel-name
E.g.
# Plugin game-features
# Plugin modular-gameplay
# System enhanced-input-system
# System gameplay-ability-system
But maybe having all of those in the programming category is "wrong" and we might want to put them into a Plugins category.
Not sure if people actively read the category name though
Cause they are clearly a different concept of channel compared to the "topic" ones I think.
#blueprint
#multiplayer
#cpp
#verse
#gameplay-ai
#online-subsystems (maybe)
#chaos-physics (which would just be physics if we didn't have an old system)
are all topics or concepts. While
#epic-online-services
#gameplay-ability-system
#mass
#game-features-system
#enhanced-input-system
#modular-gameplay-plugin
seem more like individual systems to talk about.
Just throwing out food for thought @robust oasis
I like that split if we made an "Engine Plugins" category, although maybe OSS belongs in it with EOS