-
Posts
1,448 -
Joined
-
Days Won
132
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Death
-
There's been a tremendous trend in AI-generated content in this space, so we felt it was essential to get ahead of it before it spirals out of control. We've seen quite a bit of feedback on our official stance against content made primarily using AI, so before we go full send, we want to make sure we're making the right call. Our current stance on AI content is as follows: Submissions generated entirely by AI are not allowed. However, AI-assisted content is welcome if it enhances your creative process and that any AI usage is clearly disclosed in your product description. We've been more lenient towards product thumbnails and free content where we felt the author was making a reasonable effort to learn. With that being said, I personally feel like it's getting out of control, especially for thumbnails. While we likely won't prohibit the use of AI-generated images, we want to set a clear quality threshold so the site doesn't become a wash of generic looking content. Personally, I feel the biggest concern at the moment is AI-generated plugins, especially those that are paid. I dislike the idea of someone trying to profit from content they did not make, nor are they capable of maintaining outside of their reliance on AI. Full disclosure: I find AI to be extremely helpful, and I use it quite often, but I use it as a tool to improve my process, not completely replace it. Let us know your thoughts about this. Are we being too harsh, or are we making the right call? This may seem pretty obvious from the perspective of a developer, but that's because we understand the code and know how cooked a lot of these AI-generated plugins are. It would be great to have a consumer perspective.
- 109 replies
-
- 19
-
-
-
Is this still an issue on the latest version of Carbon @steampunkvalley?
-
@Answer
-
It seems the author was responsive to comments, so I recommend giving them a bit more time to respond to your support request. I'll ping them here so they're aware of your outstanding support request. @Keirox
-
- 196 comments
-
- #rust plugin
- #custom rust plugin
-
(and 2 more)
Tagged with:
-
This is why we typically recommend having values pre-filled as it's impossible to know without knowing the structure of the class. I'll help in this case though. Static NPCs in this case, is a Hashset of NpcPresetLocationConfig: public string presetName { get; set; } public string navMeshPresetName { get; set; } public string position { get; set; } Knowing it's a list of that class, we can build an example entry: "Static NPCs": [ { "presetName". "navMeshPresetName". "position" }, { "presetName2". "navMeshPresetName2". "position2" } ], The structure for Regular Npcs is the exact same, it's a Hashset of NpcPresetLocationConfig. I have no clue what any of these values do, but if you do, you should know how to fill it in. I imagine this was done intentionally as it's not implemented yet. But wanted to share this in case you experience this in the future, so you know generally how to populate an empty list inside of a config or data file.
-
@cameron
-
@dustyhansen @dutchess Is this still an issue?
-
@averageatbest was this resolved?
-
Just checking if you were able to resolve this @frizzo420?
-
Looks clean!
-
- 196 comments
-
- #rust plugin
- #custom rust plugin
-
(and 2 more)
Tagged with:
-
There's been progress but no where near done.
-
Were you able to resolve this issue?
-
Hey @Frostmourne I've moved this thread to the correct place. Is this still an issue?
-
Were you able to resolve this issue?
-
@imthenewguy Not sure if this was ever resolved so bringing to your attention just in case.
-
Were you able to resolve this? If so mind sharing?