Rewriting the plugin to use the new oxide.ext.discordSolved

@evlad, I am updating the plugin to work with the new Discord extension. I know we aren't supposed to but I don't think you have been around for a number of years and lots of people need this. I am basically done restoring the plugin functionality but obviously can distribute the plugin.

@wulf, how can we make the rewrite available to people if the original dev is MIA?

Meant to say can't* distribute. 

@Wulf Can u help to redistribute this plugin? What needs to be done for this?
@MJSU Can u help to redistribute this plugin? What needs to be done for this?
@MJSU, the 1.0.0 version only worked with oxide.ext.discord 2 but doesn't work with oxide.ext.discord 3. I have since rewritten it to be compatible but not sure how to get the plugin page updated.
Daemante
@MJSU, the 1.0.0 version only worked with oxide.ext.discord 2 but doesn't work with oxide.ext.discord 3. I have since rewritten it to be compatible but not sure how to get the plugin page updated.

Daemante has updated the code for this plugin to work on version 0.3. However, since the plugin owner cannot be reached or is inactive, he wants to release this update himself. Maybe you can tell him what to do about this? @LaserHydra

HdDG6gGkOm2DRpT.png anltrn

Daemante has updated the code for this plugin to work on version 0.3. However, since the plugin owner cannot be reached or is inactive, he wants to release this update himself. Maybe you can tell him what to do about this? @LaserHydra

yeah hope , cuz we need update for it.

@MrBlue@LaserHydra Daemante has updated the code for this plugin to work on version 0.3. However, since the plugin owner cannot be reached or is inactive, he wants to release this update himself. Maybe you can tell him what to do about this?

we need it for server

MJSU
rKN920OZBiG7eh2.png anltrn

I'm sorry but this doesn't work on my server. I get an error message. 
I think the one you posted still belongs to the 2.0 plugin.

I have submitted a pull request to MJSU's repository to resolve the issue with the latest versions. In the meantime, you can manually edit the ChannelCreate object to apply the fix.

ChannelCreate newChannel = new ChannelCreate {
    Name = channelName,
    Type = ChannelType.GuildText,
    ParentId = _config.CategoryID,
    DefaultAutoArchiveDuration = 60 // Set to a valid value, such as 60 minutes
};

Did you test it and it works? I had a lot more issues than the missing DefaultAutoArchiveDuration.

Daemante

Did you test it and it works? I had a lot more issues than the missing DefaultAutoArchiveDuration.

Yes, tested on Oxide: v2.0.6333 and Discord extension: v3.1.2. Discord's API requires that the default_auto_archive_duration field be set to a valid enum value when creating channels. Since the value 0 is no longer accepted, I’ve updated the script to specify a valid duration, ensuring that channel creation requests are successful. But that fix is applied over to whatever changes are here: https://github.com/dassjosh/DiscordExtensionBeta/blob/main/Plugins/2.0/DiscordCallAdmin/DiscordCallAdmin.cs

 

Using the code from post #14 above and from github, I get the following error when calling the command in-game /calladmin

[11:21:51] > Loaded plugin Discord Call Admin v1.0.0 by evlad
[11:22:26] > [DiscordExtension] [Error]: Rest Request Exception (Discord API Error). Plugin: DiscordCallAdmin by evlad v1.0.0 ID: 17114706329991118849 Request URL: [POST] guilds/735387107022864485/channels Content-Type: application/json; charset=utf-8 Http Response Code: BadRequest Discord Error Code: 50035 Discord Error: Invalid Form Body
Discord Errors: {
"default_auto_archive_duration": {
"_errors": [
{
"code": "ENUM_TYPE_COERCE",
"message": "Value \"0\" is not a valid enum value."
}
]
}
}Request Body:
{"name":"76561198077252250_919049443167330364","type":0,"parent_id":"735387296081379358","default_auto_archive_duration":0}

Locked automatically