【👏】ꜱᴜɢɢᴇꜱᴛɪᴏɴꜱ

Add a Whats new shortcut on the top main bar

1

implement a standardisation about how plugins should be uploaded, like uMod does: all plugins work the same, are extracted in the same way. This makes it great for automation. Current situations make it very hard to automate because each plugin packs their stuff differently. AKA, please professionalize.

3

a channel in discord of known bugs of the web, so you would know if you have found a bug that is not known and inform about it.

Stevie senpai

a channel in discord of known bugs of the web, so you would know if you have found a bug that is not known and inform about it.

Added #【🐞】ʀᴇᴘᴏʀᴛ-ᴀ-ʙᴜɢ

1

Suggestion from: Dream Doctor Suggestion: Setup some "developer" role to see the discord channels without "guest" users being able to view the channels to remove the support type related questions for tech support. The goal would be forcing the tech support questions into the other discord and keeping ArkServerAPI exclusive to development only. (edited)

5

1

Standardisation suggestion: Enforce a particular folder naming convention or store the value of the folder name that is used by the plugin. Example: The developer sets up a name on the website, like Cross Server Chat. When the ZIP is unpacked, the folder inside is named: RconCrossServerChat. This makes it impossible for procedural systems to work with. It's unreliable. A couple suggestions on how this can be solved / improved:

Enforcing a naming convention ensures the folder names are a (standardised) derivative of the website name
By allowing the developer to setup a different "unpack folder name" field, so systems can work with that.

(edited)

2

AnotherMax

Standardisation suggestion: Enforce a particular folder naming convention or store the value of the folder name that is used by the plugin. Example: The developer sets up a name on the website, like Cross Server Chat. When the ZIP is unpacked, the folder inside is named: RconCrossServerChat. This makes it impossible for procedural systems to work with. It's unreliable. A couple suggestions on how this can be solved / improved:

Enforcing a naming convention ensures the folder names are a (standardised) derivative of the website name
By allowing the developer to setup a different "unpack folder name" field, so systems can work with that.

(edited)

This should be fairly easy to implement. Developers should upload their files and then the zip file inherits the name of the dll.

5:18 PM

That’s what npm does at least (afaik)

5:19 PM

There’s a lot that could be done with some standardization, including dependency resolution.

Standardisation suggestion: Put up a suggestion (or ideally a preset) for developers to add a config.json with their default configs. This allows 3rd parties to reliably fetch a default config. Currently the config examples are posted inside the plugin description. But because this isnt always on the same place (or under the same title) this cant be fetched automatically in a reliable way.

Another standardization, we need to stop putting the api into version.dll

5:25 PM

Using version to load the api is fine

5:25 PM

But the api itself should be a separate dll

5:26 PM

This also simplifies traversing dll files to create dependency chains

5:26 PM

As right now plugins are linked against “version” and not “arkapi”

5:26 PM

So instead of version -> plugins

5:26 PM

It would be version -> api -> plugins

Please add FAQ's https://ark-server-api.com/forums/threads/faq.19/ Back to header or even footer of the website this page is really useful

2

5:22 PM

5:23 PM

or

(edited)

Suggestion 「 Approved 」

Suggestion From: @BearGryllsTV Suggestion: Add "F.A.Q (Frequently Asked Questions)" back to the header and footer. Link: https://ark-server-api.com/forums/threads/faq.19/

2

1

Suggestion 「 Under Review 」

@GSH | MrOwlSky #【💌】ʜᴇʟᴘꜰᴜʟ-ʟɪɴᴋꜱ has outdated github link

3

1

2:50 AM

Suggestion 「 Under Review 」

Change the "Permission" label on the permissions plugins when someone type /groups. I know that is text for the "server" but admins are mistaking groups and permissions because of that label.

2

1

Suggestion 「 Under Review 」

I mentioned this before to Wetbatman a while back, and he liked the idea, but I don't think it went much further than that. Using the real time save/unload/load ability with the PluginName.dll.arkapi file works great, but sometimes it's more convenient to perform the update on next server restart. Could we get something like a PluginName.dll.arkapinext extension that would do just that? Many thanks!

3

1

Suggestion 「 Under Review 」

while porting arkserverapi to ark 1.5 you should probably add linux support (it would be nice)

6

2

2