Jump to content

VSChatBot - A Discord bot integration for VS servers


Capsup

Recommended Posts

So problem solved!!! EvilToaster found that mu Ubantu Linux Server needed a Mono package update. Server was running Mono 4.0 I use Akliz server hosting and they upgraded to Ubantu 20.04 and Mono 6.0. VSChatbot now works flawlessly! 🤩

  • Like 1
Link to comment
Share on other sites

On 2/9/2021 at 4:20 AM, CJHKnight2 said:

So problem solved!!! EvilToaster found that mu Ubantu Linux Server needed a Mono package update. Server was running Mono 4.0 I use Akliz server hosting and they upgraded to Ubantu 20.04 and Mono 6.0. VSChatbot now works flawlessly! 🤩

Glad to hear that! I have no idea how you guys figured it out based on that error message, but sweet.

Link to comment
Share on other sites

On 2/11/2021 at 6:57 PM, Evil Toaster said:

Also, the library "DSharpPlus" is incompatible with Windows Server 2008 in my experience🤔

That sounds like a bit of a .NET Framework thing though. Windows Server 2008 isn't officially supported by Microsoft any longer, so I'm not too worried about that. It's probably a good indicator that it's time to upgrade your OS too. :)

Edited by Capsup
Link to comment
Share on other sites

7 hours ago, Capsup said:

That sounds like a bit of a .NET Framework thing though. Windows Server 2008 isn't officially supported by Microsoft any longer, so I'm not too worried about that. It's probably a good indicator that it's time to upgrade your OS too. :)

The funny thing is, the .NET Framework the required versions are available on this OS, and it does not work. In general, I am a "guest" with elevated rights on that server, so I have no such opportunity. 🤭

Link to comment
Share on other sites

On 12/26/2020 at 9:12 PM, momai Alex said:

Good day!

Great mod, thanks!

From wishes:

On 1/10/2021 at 3:55 PM, momai Alex said:


12:54:31 [Server Notification] Entering runphase LoadGame
Version: ??????????????? ?????? artEA#8001 v1.14.0 (Stable)01/10/2021 12:54:31: Critical error occurred
System.NullReferenceException: Object reference not set to an instance of an object
  at DSharpPlus.DiscordClient.SendMessageAsync (DSharpPlus.Entities.DiscordChannel channel, System.String content, System.Boolean tts, DSharpPlus.Entities.DiscordEmbed embed) [0x00006] in <73bf8d85ff3e42158583ab7e0be5fd9f>:0
  at vschatbot.src.DiscordWatcher.sendDiscordMessage (System.String message, DSharpPlus.Entities.DiscordEmbed embed) [0x00001] in <0dd8f803229d46d8922633b2f9b3fa75>:0
  at vschatbot.src.DiscordWatcher.Event_ServerStartup () [0x0000d] in <0dd8f803229d46d8922633b2f9b3fa75>:0
  at Vintagestory.Server.ServerEventAPI.OnServerStage (Vintagestory.API.Server.EnumServerRunPhase runPhase) [0x00025] in <785327a3fe2e4d2ebe5e223bef6e3faa>:0
  at Vintagestory.Server.ServerSystemModHandler.OnBeginGameReady (_wTXE2v1LflyYDnwkuDFOLi4HPJm savegame) [0x00000] in <785327a3fe2e4d2ebe5e223bef6e3faa>:0
  at Vintagestory.Server.ServerMain.EnterRunPhase (Vintagestory.API.Server.EnumServerRunPhase runPhase) [0x0009a] in <785327a3fe2e4d2ebe5e223bef6e3faa>:0
  at Vintagestory.Server.ServerMain.Launch () [0x002b4] in <785327a3fe2e4d2ebe5e223bef6e3faa>:0
  at ?????????????????????????????????????????.????????????????????????????????????????? () [0x000ce] in <46462d398d354fd8929b482784f4efa0>:0
  at _eVFDVqwXngafMmcD9boVPO86iWx._hbMghNVJIKTGI5zBx3SuxRG1XDI (System.Threading.ThreadStart ) [0x00007] in <785327a3fe2e4d2ebe5e223bef6e3faa>:0
-------------------------------
Crash written to file at "/home/server/data/Logs/server-crash.txt"

Unhandled Exception occurred
Version: ??????????????? ?????? artEA#8001 v1.14.0 (Stable)01/10/2021 12:54:42: Critical error occurred
System.NullReferenceException: Object reference not set to an instance of an object
  at DSharpPlus.DiscordClient.Dispose () [0x00056] in <73bf8d85ff3e42158583ab7e0be5fd9f>:0
  at DSharpPlus.DiscordClient.Finalize () [0x00000] in <73bf8d85ff3e42158583ab7e0be5fd9f>:0
-------------------------------
Crash written to file at "/home/server/data/Logs/client-crash.txt"

[ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
  at DSharpPlus.DiscordClient.Dispose () [0x00056] in <73bf8d85ff3e42158583ab7e0be5fd9f>:0
  at DSharpPlus.DiscordClient.Finalize () [0x00000] in <73bf8d85ff3e42158583ab7e0be5fd9f>:0
Unknown command line option: '--arch=32'

 

:((

1) Add all notifications to the config. To customize them.

2) It would be nice to be able to ban from the discord, for users with the desired role.

I fought for a long time. The problem was in the pi-hole dns
Do not use it if you have Docker.

Link to comment
Share on other sites

On 1/10/2021 at 3:55 PM, momai Alex said:

12:54:31 [Server Notification] Entering runphase LoadGame
Version: ??????????????? ?????? artEA#8001 v1.14.0 (Stable)01/10/2021 12:54:31: Critical error occurred
System.NullReferenceException: Object reference not set to an instance of an object
  at DSharpPlus.DiscordClient.SendMessageAsync (DSharpPlus.Entities.DiscordChannel channel, System.String content, System.Boolean tts, DSharpPlus.Entities.DiscordEmbed embed) [0x00006] in <73bf8d85ff3e42158583ab7e0be5fd9f>:0
  at vschatbot.src.DiscordWatcher.sendDiscordMessage (System.String message, DSharpPlus.Entities.DiscordEmbed embed) [0x00001] in <0dd8f803229d46d8922633b2f9b3fa75>:0
  at vschatbot.src.DiscordWatcher.Event_ServerStartup () [0x0000d] in <0dd8f803229d46d8922633b2f9b3fa75>:0
  at Vintagestory.Server.ServerEventAPI.OnServerStage (Vintagestory.API.Server.EnumServerRunPhase runPhase) [0x00025] in <785327a3fe2e4d2ebe5e223bef6e3faa>:0
  at Vintagestory.Server.ServerSystemModHandler.OnBeginGameReady (_wTXE2v1LflyYDnwkuDFOLi4HPJm savegame) [0x00000] in <785327a3fe2e4d2ebe5e223bef6e3faa>:0
  at Vintagestory.Server.ServerMain.EnterRunPhase (Vintagestory.API.Server.EnumServerRunPhase runPhase) [0x0009a] in <785327a3fe2e4d2ebe5e223bef6e3faa>:0
  at Vintagestory.Server.ServerMain.Launch () [0x002b4] in <785327a3fe2e4d2ebe5e223bef6e3faa>:0
  at ?????????????????????????????????????????.????????????????????????????????????????? () [0x000ce] in <46462d398d354fd8929b482784f4efa0>:0
  at _eVFDVqwXngafMmcD9boVPO86iWx._hbMghNVJIKTGI5zBx3SuxRG1XDI (System.Threading.ThreadStart ) [0x00007] in <785327a3fe2e4d2ebe5e223bef6e3faa>:0
-------------------------------
Crash written to file at "/home/server/data/Logs/server-crash.txt"

Unhandled Exception occurred
Version: ??????????????? ?????? artEA#8001 v1.14.0 (Stable)01/10/2021 12:54:42: Critical error occurred
System.NullReferenceException: Object reference not set to an instance of an object
  at DSharpPlus.DiscordClient.Dispose () [0x00056] in <73bf8d85ff3e42158583ab7e0be5fd9f>:0
  at DSharpPlus.DiscordClient.Finalize () [0x00000] in <73bf8d85ff3e42158583ab7e0be5fd9f>:0
-------------------------------
Crash written to file at "/home/server/data/Logs/client-crash.txt"

[ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
  at DSharpPlus.DiscordClient.Dispose () [0x00056] in <73bf8d85ff3e42158583ab7e0be5fd9f>:0
  at DSharpPlus.DiscordClient.Finalize () [0x00000] in <73bf8d85ff3e42158583ab7e0be5fd9f>:0
Unknown command line option: '--arch=32'

 

:((

I fought for a long time. The problem was in the pi-hole DNS
Do not use it if you have docker

Link to comment
Share on other sites

  • 1 month later...
  • 5 weeks later...
On 3/29/2021 at 2:21 PM, zybillo said:

hello, the bot does not respond to commands, the game chat shows warnings about storms, and does not respond to commands . What can it be?

I realize this is a month later, but this sounds like what would happen if you do not have the config properly setup to connect to Discord. Did you follow the installation instructions in the OP and make sure you got the connected message as expected?

Link to comment
Share on other sites

Yes, all the settings are as in the description, I deleted the bot and put it on a new one. After starting the server, the bot works for some time but does not execute commands, and then it completely turns off. I have been using the bot for several months, everything was fine, but now it has deteriorated for two months.

Link to comment
Share on other sites

11 hours ago, zybillo said:

Yes, all the settings are as in the description, I deleted the bot and put it on a new one. After starting the server, the bot works for some time but does not execute commands, and then it completely turns off. I have been using the bot for several months, everything was fine, but now it has deteriorated for two months.

If you're saying it used to work, but now no longer does, I'm not really sure what I can tell you to be honest. There hasn't been any updates to the code in that timeframe, so it must obviously be something else that has had an impact on the stability of it. Can you zip up your entire logs folder once it starts not responding and then PM it to me? Maybe the logs can tell us more of what is happening.

Link to comment
Share on other sites

  • 1 month later...
On 7/20/2021 at 11:34 AM, Sypher Tendervine said:

When using the !time command, the bot seems to think that it's Spring, even in the dead of winter.

 

w/ Latest 1.15.1

The bot will only report the current calendar time at the default spawn location.
The world is much like Earth, so it doesn't have spring and winter at the same time everywhere. Are you perhaps quite far away from the default spawn?

Otherwise you will have to provide me a world copy where you stand at the default spawn and the bot reports something different from the in-game calendar, so I can recreate it.

Edited by Capsup
Link to comment
Share on other sites

  • 1 month later...
39 minutes ago, Julius van Vern said:

I think it wasnt in the Mod database

Declaring it "abandoned" seems to open the door for someone else to pick it up and keep it working. Hope someone does. It has become an important part of many multiplayer server communities.

Link to comment
Share on other sites

  • 2 weeks later...
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.