4 minutes ago, SrMiller said:

Its selfhosting on windows?

yes

https://nodejs.org/en/blog/release/v18.13.0

37 minutes ago, MaLai said:

yes

Did you install the npm packages? I really suggest you to host it on any host. Can share you one for 0.50/month with enought resources for this bot.

22 minutes ago, SrMiller said:

Did you install the npm packages? I really suggest you to host it on any host. Can share you one for 0.50/month with enought resources for this bot.

Installed 18.13 its still not working. Npm Packages are installed. Sorry we are not interested on another subscription also we have a dedicated windows server.

 

PS C:\Users\Administrator\desktop\discord2skinbox> node app.js
Loaded Pending Skins: 2
RCON Connection Established for server at 45.138.49.49:27025.
Ready! Connected as Hansi#5040
node:events:491
      throw er; // Unhandled 'error' event
      ^

ReferenceError: rcon is not defined
    at Client.<anonymous> (C:\Users\Administrator\desktop\discord2skinbox\app.js:214:64)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Emitted 'error' event on Client instance at:
    at emitUnhandledRejectionOrErr (node:events:394:10)
    at process.processTicksAndRejections (node:internal/process/task_queues:84:21)

Node.js v18.13.0

Hey,

I fixed it myself. For other people who got this problem this is the fix:

The problem is there:
 

        if (isStaffMember) {
            if (isApproval) {
                try {
                    for (const rcon of rconConnections) {
                        let addSkinCommand = '';
                        if (pluginSkins === 'lskins') {
                            addSkinCommand = `lskins add ${skinId}`;
                        } else if (pluginSkins === 'skincontroller') {
                            addSkinCommand = `addskin ${skinId}`;
                        } else if (pluginSkins === 'skinbox') {
                            addSkinCommand = `skinbox.addskin ${skinId}`;
                        } else if (pluginSkins === 'custom') {
                            addSkinCommand = `${customCommand} ${skinId}`;
                        }
                        await rcon.send(addSkinCommand);

                        const acceptMessage = ` **Skin Accepted on ${rcon.server_name}** \n\nSkin ID: ${skinId}\nAccepted by ${member}`;
                        client.channels.cache.get(logs).send(acceptMessage);
                    }
                } catch (error) {
                    console.error(error);
                    requestMessage.channel.send('Error adding the skin.');
                }
            } else {
				                
                const rejectMessage = ` **Skin Rejected on ${rcon.server_name}** \n\nSkin ID: ${skinId}\nRejected by ${member}`;
                client.channels.cache.get(logs).send(rejectMessage);
									
            }
            requestMessage.reactions.removeAll().catch(error => console.error('Error removing reactions:', error));

            const pendingSkinIndex = pendingSkins.findIndex(skin => skin.skinId === skinId);
            if (pendingSkinIndex !== -1) {
                pendingSkins.splice(pendingSkinIndex, 1);
                savePendingSkins();
            }
        }
    }
});

On:
            } else {
                const rejectMessage = ` **Skin Rejected on ${rcon.server_name}** \n\nSkin ID: ${skinId}\nRejected by ${member}`;
                client.channels.cache.get(logs).send(rejectMessage);

rcon.server_name = rcon is not defined in the code.
So I added a definition to that:

			for (const rcon of rconConnections) {
                const rejectMessage = ` **Skin Rejected on ${rcon.server_name}** \n\nSkin ID: ${skinId}\nRejected by ${member}`;
                client.channels.cache.get(logs).send(rejectMessage);
			}

Now its working.

Hey SrMiller, hope you had a good Christmas break. Also appreciate you taking the time to answer some of my questions over the holiday period. 
I've gotten the chance to actively use the plugin and it works great! 

I'd love to throw a few ideas/feature requests below from myself and others in my community for your consideration.

- URL Only Option
Currently, players can submit a Workshop Skin via a URL or the SkinID. The benefit of the URL over the SkinID, is that Discord provides a preview of the skin and an admin can quickly visit the Workshop link to check the skins meet any requirements the server might have on skin submissions. 

(Though it would be great if any SkinID displayed in any response messages from the bot could also linked directly to the skin URL)

- Approval/Reject Link Back or Amend
When approving or rejecting a submitted skin could the response be given as a reply or include a link back to the original message? This would just help quickly identify which approval or rejection the message belongs to.

- Reject Reason Option
When a skin is rejected an option that allows the admin to provide a reason. 

- Auto Reject or Mark as Duplicate
Could the bot store SkinIDs or check the skinbox data for existing IDs and auto-reject previous rejections or mark them are previously accepted? 

- Official Skins Highlight
I think this is unlikely to be possible, but I'll ask the question anyway. Could the bot highlight or in some way mark any skins submitted that are official skins? Along with an option to auto-reject those with a predefined reason.

Appreciate your time and any consideration on any of the above ideas.

Have a great New Year! 

6 minutes ago, Rise said:

Hey SrMiller, hope you had a good Christmas break. Also appreciate you taking the time to answer some of my questions over the holiday period. 
I've gotten the chance to actively use the plugin and it works great! 

I'd love to throw a few ideas/feature requests below from myself and others in my community for your consideration.

- URL Only Option
Currently, players can submit a Workshop Skin via a URL or the SkinID. The benefit of the URL over the SkinID, is that Discord provides a preview of the skin and an admin can quickly visit the Workshop link to check the skins meet any requirements the server might have on skin submissions. 

(Though it would be great if any SkinID displayed in any response messages from the bot could also linked directly to the skin URL)

- Approval/Reject Link Back or Amend
When approving or rejecting a submitted skin could the response be given as a reply or include a link back to the original message? This would just help quickly identify which approval or rejection the message belongs to.

- Reject Reason Option
When a skin is rejected an option that allows the admin to provide a reason. 

- Auto Reject or Mark as Duplicate
Could the bot store SkinIDs or check the skinbox data for existing IDs and auto-reject previous rejections or mark them are previously accepted? 

- Official Skins Highlight
I think this is unlikely to be possible, but I'll ask the question anyway. Could the bot highlight or in some way mark any skins submitted that are official skins? Along with an option to auto-reject those with a predefined reason.

 

Appreciate your time and any consideration on any of the above ideas.

Have a great New Year! 

Hey, I love your ideas and I will try to take the time to implement some of them, the truth is that they are not easy as all this would need to add a storage, but I will try to do it as soon as possible. 

Have a happy new year!

3 hours ago, SrMiller said:

Hey, I love your ideas and I will try to take the time to implement some of them, the truth is that they are not easy as all this would need to add a storage, but I will try to do it as soon as possible. 

Have a happy new year!

No worries at all, appreciate you taking the time to look and reply.

I also fully understand a simple idea doesn't always result in a simple creation process   certain platform restrictions can't be altered. 

All the best! 

Do you think the bot could handle adding collections of skins?

For example https://steamcommunity.com/workshop/filedetails/?id=3126573666

I know with skinbox you can do `skinbox.addcollection` maybe a response to the bot could mark it as a collection? 

can this be used with skinners ? 
and carbon ?

On 2/2/2024 at 10:25 AM, Rise said:

Do you think the bot could handle adding collections of skins?

For example https://steamcommunity.com/workshop/filedetails/?id=3126573666

I know with skinbox you can do `skinbox.addcollection` maybe a response to the bot could mark it as a collection? 

It is a very good idea. I'll look for it.

On 2/3/2024 at 5:24 PM, The Mad Hatter said:

can this be used with skinners ? 
and carbon ?

Actually it only works on this 3 ones. Let me the URL of the plugin you're using and i'll take a look.

On 12/28/2023 at 1:14 PM, Rise said:

Hey SrMiller, hope you had a good Christmas break. Also appreciate you taking the time to answer some of my questions over the holiday period. 
I've gotten the chance to actively use the plugin and it works great! 

I'd love to throw a few ideas/feature requests below from myself and others in my community for your consideration.

- URL Only Option
Currently, players can submit a Workshop Skin via a URL or the SkinID. The benefit of the URL over the SkinID, is that Discord provides a preview of the skin and an admin can quickly visit the Workshop link to check the skins meet any requirements the server might have on skin submissions. 

(Though it would be great if any SkinID displayed in any response messages from the bot could also linked directly to the skin URL)

- Approval/Reject Link Back or Amend
When approving or rejecting a submitted skin could the response be given as a reply or include a link back to the original message? This would just help quickly identify which approval or rejection the message belongs to.

- Reject Reason Option
When a skin is rejected an option that allows the admin to provide a reason. 

- Auto Reject or Mark as Duplicate
Could the bot store SkinIDs or check the skinbox data for existing IDs and auto-reject previous rejections or mark them are previously accepted? 

- Official Skins Highlight
I think this is unlikely to be possible, but I'll ask the question anyway. Could the bot highlight or in some way mark any skins submitted that are official skins? Along with an option to auto-reject those with a predefined reason.

 

Appreciate your time and any consideration on any of the above ideas.

Have a great New Year! 

Check last update

I will try to add your other suggestions. Thanks for the feedback.

Hello srmiller,

Are you able to make this discord bot compatible with discord forums?

On 2/13/2024 at 3:22 AM, Vinnij said:

Hello srmiller,

 

Are you able to make this discord bot compatible with discord forums?

Hey Vinni, thanks for the suggestion. I'll try to add this function soon.

I have one more, are you able to make it so that if you have more than one sever you can select what servers you want it to be on?

If I did not explain this well please tell me and I will make it better.

6 minutes ago, Vinnij said:

I have one more, are you able to make it so that if you have more than one sever you can select what servers you want it to be on?

If I did not explain this well please tell me and I will make it better.

Please can you DM me with a more detailed description? Just to make sure what you are thinking

Hey, when using the skinner plugin its adding a space to the skinimport command. So should be like this skinimport 2873813871 but it ends up like this skinimport  2873813871   [Skinner] Could not find item definition for  2873813871

9 hours ago, Ghosty said:

Hey, when using the skinner plugin its adding a space to the skinimport command. So should be like this skinimport 2873813871 but it ends up like this skinimport  2873813871   [Skinner] Could not find item definition for  2873813871

Hey Ghosty. Open a ticket on my discord or add me as srmiller and let's try to fix it.

being able to accept a collection of skins would be awesome too if possible please

10 hours ago, Bojack said:

being able to accept a collection of skins would be awesome too if possible please

Hey, I'll add this feature soon!

RCON Connection for server at 88.198.14.50:28019 has been disconnected.
Reconnecting to server at 88.198.14.50:28019...
RCON Connection Established for server at 88.198.14.50:28019.
Error: WebSocket is not open: readyState 3 (CLOSED)
    at WebSocket.send (/home/container/node_modules/rustrcon/node_modules/ws/lib/websocket.js:329:19)
    at WebSocket.sendMessage (/home/container/node_modules/rustrcon/src/client/websocket/ws.js:59:11)
    at Client.send (/home/container/node_modules/rustrcon/src/client/client.js:19:11)
    at Client.<anonymous> (/home/container/app.js:262:36)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Getting this error when trying to accept a skin 

12 minutes ago, Wajeeh Agbariya said:

RCON Connection for server at 88.198.14.50:28019 has been disconnected.
Reconnecting to server at 88.198.14.50:28019...
RCON Connection Established for server at 88.198.14.50:28019.
Error: WebSocket is not open: readyState 3 (CLOSED)
    at WebSocket.send (/home/container/node_modules/rustrcon/node_modules/ws/lib/websocket.js:329:19)
    at WebSocket.sendMessage (/home/container/node_modules/rustrcon/src/client/websocket/ws.js:59:11)
    at Client.send (/home/container/node_modules/rustrcon/src/client/client.js:19:11)
    at Client.<anonymous> (/home/container/app.js:262:36)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Getting this error when trying to accept a skin 

Hey. Can you join my discord and open a ticket? I'll help you. https://discord.gg/mWwvF78A

When I try running node app.js, I get an error that says Uncaught SyntaxError: Unexpected identifier

This is on Windows Server 2012.

can this be used for