[MOD] Coppis Additions (NEW)

[Prisma501]

hmm, no. installed the old mods (3.6) and am getting the same errors now :/ and yes, i did shut the server down and deleted the .bin file ^^ dang

Are you by any chance running botman or servertools servermanager? Coppis has grounddistance check and flying check but does not run them from within coppis. Botman uses those commands though and servertools has a own implementation and both run them periodically.

If 3.6 gives same errors i presume there is something else causing it. If you do manually do command "pug" in console, do you get the same error?

Cheers

-edit- only recognizable from coppisadditions is PlayerGroundDistance and it looks like it cant get a player to check in the online player list. The other errors seem to be related to that and indicate something is not running allright on the server. Its a dedicated server right?

 

[ecv]

using botman, yes. the troublemaker is the steamnetworks thing though, the other Errors don't really affect anything it seems. The latest pugs went through fine too

 

[Prisma501]

using botman, yes. the troublemaker is the steamnetworks thing though, the other Errors don't really affect anything it seems. The latest pugs went through fine too

Do you maybe have a player with a bad inet connection? It kinda looks like this has been around forever. Even found your post from 4 hours ago with the advice i wanted to give (disable unet)

Maybe disable botman for a little while and see if that helps. Telnet traffic (usually to much of it) can cause servers to act very badly is my experience.

Wish i could be of more help.

Cheers

 

[ecv]

heh, can't disable botman, without a lobby our server is pretty much useless, since we are about epic builds. A single griefer would cause more harm than disconnects I thank you for your help though. This error appears even for me, and i have a perfect connection. five steps to the hoster and pings around 20-40ms. We've had it with 3 players online and with 24. It's just not apparent what the cause might be

Thing is, we've been running this for almost two years, setup is always the same. procedure is always the same. players are mostly the same too *g* We do get like 20 new players a day. The last instance had 1000 unique users in a month and such a problem never occurred. I'm absolutely stumped

 

[ecv]

latest crash:

[s_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.

Setting breakpad minidump AppID = 251570

Unhandled Exception: System.InvalidOperationException: out of sync

at System.Collections.Generic.Dictionary`2+Enumerator[system.Int32,EntityPlayer].VerifyState () [0x00000] in <filename unknown>:0

at System.Collections.Generic.Dictionary`2+Enumerator[system.Int32,EntityPlayer].MoveNext () [0x00000] in <filename unknown>:0

at CoppisAdditions.LocationTracker.RunWhoLocationThread () [0x00000] in <filename unknown>:0

mmap(...PROT_NONE...) failed

eac_server.so [x64] :: OnLoad()

Stacktrace:

at (wrapper managed-to-native) System.GC.InternalCollect (int) <0x0005e>

at (wrapper managed-to-native) System.GC.InternalCollect (int) <0x0005e>

at System.GC.Collect () <0x00020>

at GameManager.GJ () <0x00be6>

at GameManager.Update () <0x00014>

at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0x0005e>

Native stacktrace:

/home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x91772) [0x7f9c5c752772]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0) [0x7f9c5dd260c0]

/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf) [0x7f9c5cf03fff]

/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x7f9c5cf0542a]

/home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x19fb07) [0x7f9c5c860b07]

/home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x1a0e5a) [0x7f9c5c861e5a]

/home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x197673) [0x7f9c5c858673]

/home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x1987f2) [0x7f9c5c8597f2]

/home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x198981) [0x7f9c5c859981]

/home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x198cf7) [0x7f9c5c859cf7]

/home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x198d41) [0x7f9c5c859d41]

[0x4072574e]

 

[ecv]

a'ight, we set up another instance without a bot, getting the errors and bad pings there as well, tried it with a mere eight players

 

[Prisma501]

a'ight, we set up another instance without a bot, getting the errors and bad pings there as well, tried it with a mere eight players

Well considder me stumped too

Coppis is at 126 downloads now for version 4.4 and as it seems this is not happening to anyone else. It somehow states that steam is not running which could lead to the rest of the errors but i truly dont know

Cheers

 

[insG_Drifter]

Well considder me stumped too
Coppis is at 126 downloads now for version 4.4 and as it seems this is not happening to anyone else. It somehow states that steam is not running which could lead to the rest of the errors but i truly dont know

Cheers

I noticed the error line Steam API and wonder if it’s related to the api change steam recently made that affected Allocs server tools. Just thinking out loud since I’ve not tested.

 

[ecv]

we have, out of desperation, disabled EAC and enabled unet again (don't ask me why, we are trying everything imaginable.) we are now getting the standard unet errors, but no ping-jumping, no connection troubles and much better pings in general. at least so far

 

[Prisma501]

I noticed the error line Steam API and wonder if it’s related to the api change steam recently made that affected Allocs server tools. Just thinking out loud since I’ve not tested.

It would if i did some sort of steam openid authentication from within coppis. And i dont use it at all.

But i think the direction is correct. Something about steamworks.net or unet or eac is off in this case.

Steam is defo fiddling on their backed last few days.

Cheers

 

[ecv]

so far it's all running fine for the last three hours. still getting this one

2018-04-08T19:40:46 123.215 INF Error in PlayerUnderground.Run: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
 at System.Collections.Generic.Dictionary`2[system.Int32,EntityPlayer].get_Item (Int32 key) [0x00000] in <filename unknown>:0 
 at CoppisAdditions.CustomCommands.PlayerUnderground.Execute (System.Collections.Generic.List`1 _params, CommandSenderInfo _senderInfo) [0x00000] in <filename unknown>:0

and this:

Unhandled Exception: System.InvalidOperationException: out of sync
 at System.Collections.Generic.Dictionary`2+Enumerator[system.Int32,EntityPlayer].VerifyState () [0x00000] in <filename unknown>:0 
 at System.Collections.Generic.Dictionary`2+Enumerator[system.Int32,EntityPlayer].MoveNext () [0x00000] in <filename unknown>:0 
 at CoppisAdditions.LocationTracker.RunWhoLocationThread () [0x00000] in <filename unknown>:0

but it's not affecting gameplay apparently

 

[Prisma501]

so far it's all running fine for the last three hours. still getting this one

2018-04-08T19:40:46 123.215 INF Error in PlayerUnderground.Run: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
 at System.Collections.Generic.Dictionary`2[system.Int32,EntityPlayer].get_Item (Int32 key) [0x00000] in <filename unknown>:0 
 at CoppisAdditions.CustomCommands.PlayerUnderground.Execute (System.Collections.Generic.List`1 _params, CommandSenderInfo _senderInfo) [0x00000] in <filename unknown>:0

and this:

Unhandled Exception: System.InvalidOperationException: out of sync
 at System.Collections.Generic.Dictionary`2+Enumerator[system.Int32,EntityPlayer].VerifyState () [0x00000] in <filename unknown>:0 
 at System.Collections.Generic.Dictionary`2+Enumerator[system.Int32,EntityPlayer].MoveNext () [0x00000] in <filename unknown>:0 
 at CoppisAdditions.LocationTracker.RunWhoLocationThread () [0x00000] in <filename unknown>:0

but it's not affecting gameplay apparently

Do you know how often botman runs that command of coppis (pug)?

And it still give no error if using it manually? If not than maybe its somewhat of a botman <-> coppis communication prob?

Both errors seem to indicate that enumerating over the list of online players throws an error. But thats standard query stuff. Maybe its the simultaniously querying that causes conflcts.

You could maybe try to disable locationtracking (loctrack enabled false) or the underground check in botman so see if both error stay away.

Cheers

-edit- i may have found a possible explenation for the error. If a player is disconnected or disconnects during the check it could be missing in the dictionary and throw it. That wouldnt be a prob at all. Do you see any disconnects right b4 the errors?

 

[insG_Drifter]

It would if i did some sort of steam openid authentication from within coppis. And i dont use it at all.
But i think the direction is correct. Something about steamworks.net or unet or eac is off in this case.

Steam is defo fiddling on their backed last few days.

Cheers

That’s what made my question it. Didn’t think the API was used here but we just went through that with Allocs so just popped into my head. Steam has been doing lots of crazy backend stuff. I use Steam logins on my website and that got blown up. Took about 5 minutes to fix but still an annoyance. :smile-new:

 

[Prisma501]

Update!

Version 4.5 (2018.04.17)

Fixed:

- checkloot command: bug that emptied the chest upon using the command (BIG thanks to RagnarokPVP for finding and reporting it)

Added:

- rlp2 command: remove specific or all claimblocks of a player without the need of player(s) being near. Chunks will autoload.

- pblock1 commmand: put block at given position without the need to reload the chunk (as per smegzor's request).

Servermanagers can use it to build structures block by block with an audience to watch it happen.

- fixdeathloop command: fix a player's ttp file that has been corrupted on dying. (Thanks to AZeDo for finding out which bytes to replace (

))Commands: cp-fdl <steamid> or fdl <steamid> or fixdeathloop <steamid>

Works with on,- and offine player.

Cheers

-edit- i was going to wait with updating until 17 arrived but the checkloot bug was bad enough to bring out one more. Thanks again RagnarokPVP for reporting. Next update will be when A17 hits us.

 

[Ragnarok]

No thank you sir for all the hard work and great additions you bring to this game! Looking forward to A17 and the future of coppis additions.

 

[Prisma501]

Update! Big change on the "safe" command!!!

Version 4.6 (2018.04.27)

Fixed:

- safe command: now its possible to undo traderprotection (unbreakable blocks) on an area!!! Protect and Unprotect blocks, prefabs, bases etc at your will. Even works on existing traders (wanna redecorate them? Just do it!)

Changed:

- pblock command: removed the obsolete rotation parameter (command allready has direction functionality)

- safe command: using quantity system instead of coordinate system when using qnt parameters (same as new pblock)

Enjoy!

Cheers

 

[Andre051988]

Hello

You have a Discord channel where i can geht info about your mod faster? I use Discord everytime that where a big help for Updates or Support

 

[Blight]

Fixed:

- safe command: now its possible to undo traderprotection (unbreakable blocks) on an area!!!

Awesome! =)

A question, think you know "djkrose's Scripting Mod" and that feature "dj-regen" (reset a small zone/chunk) or?

Is it possible to ignore claimed zones with that command? So we can reset the world or huge zones without destroying the bases.

Can you code something like that? xD

 

[Smegzor]

Small suggestion (don't take this as criticism - it's not) but you recently removed the rotation component of pblock which is fine but as it is an evolving project, may I suggest a better way to drop it would have been to silently ignore it if present rather than invalidate the command. I have to release an update as it breaks several commands in the bot. I haven't yet tested if your change is backwards compatible but I'm doing that shortly.

[Edit] No it is not backwards compatible. I will have to check for which version of Coppis and have 2 versions of my code.

 

[Prisma501]

Small suggestion (don't take this as criticism - it's not) but you recently removed the rotation component of pblock which is fine but as it is an evolving project, may I suggest a better way to drop it would have been to silently ignore it if present rather than invalidate the command. I have to release an update as it breaks several commands in the bot. I haven't yet tested if your change is backwards compatible but I'm doing that shortly.
[Edit] No it is not backwards compatible. I will have to check for which version of Coppis and have 2 versions of my code.

Yeah. Didnt think of botman while removing the param. Its no prob to restore. Will do in next update. There is something i have to check and fix anyways for neg qnt params so it will be ignored silently in 4.7.

Cheers