I've been digging for a few hours, and cannot find anything related to this, so finally had to cave and post this here. Any help to the culprit would be greatly appreciated.The file 'C:/TCAFiles/Users/Sowexy/5475/7DaysToDie_Data/level0' is corrupted! Remove it and launch unity again![Position out of bounds! 320140 > 320136]
(Filename: Line: 273)
UnloadTime: 5.100445 ms
0.000 Version: Alpha 9.3 (b5) Compatibility Version: Alpha 9.3, OS: Windows 64 Bit
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
0.004 Last played version: Alpha 9.3
Yeah I zoom in and go by the landclaim block location on alloc's map. If it is near the edge of an adjacent block or it's a big base I keep the adjacent blocks too.LT. I'd suggest to check the Region files and make sure to zoom in so you can see whether they have parts of a claim in another region file as this would be a way to cut a claim in 2. The whole claimed range will still be claimed but they may have lost parts of their base.
However, like Alloc said the players need to make sure the totality of their base is protected by claim blocks.
Thanks a lot for this great tool Alloc.
Take care all,
Neo
Ignore those, they seem to not be causing any issues.Getting this error when I upload the DLL's to the server....
I'm still using an earlier version of your webserver folder simply for this feature.Yep, this will probably become an option in a future release.
You can have both, Like I did.I'm still using an earlier version of your webserver folder simply for this feature.Would be nice to try out your new map features but if I have to pick between players getting a map and me getting an admin map, well the players win![]()
Hey thanks for that LordIcon! Unforunately I'm using managed hosting at a datacenter so i can't do installs... only ftp uploadsYou can have both, Like I did.
Use Allocs for the Admin features.
And use this one for the players.
http://7daystodie.com/forums/showthread.php?14947-Export-discovered-map-to-png
You know switching the server files won't stop people from using the API directly? So if you run a more recent version of the mod and do not have it set protected anyone who know about this can query e.g. the whole playerlist or claims.I'm still using an earlier version of your webserver folder simply for this feature.Would be nice to try out your new map features but if I have to pick between players getting a map and me getting an admin map, well the players win![]()
Their queries fail.. I've seen them fail in console (or so I thought)You know switching the server files won't stop people from using the API directly? So if you run a more recent version of the mod and do not have it set protected anyone who know about this can query e.g. the whole playerlist or claims.
Public+protected access will be quite easy as soon as I switch to Steam auth but that's probably not gonna happen before a10.
Alloc what would be the best blocking to the API? Would a .htaccess work or something of the sort? I am currently running the API from my home PC and my webhost so I am currently wondering what the best protection would be.You know switching the server files won't stop people from using the API directly? So if you run a more recent version of the mod and do not have it set protected anyone who know about this can query e.g. the whole playerlist or claims.
Public+protected access will be quite easy as soon as I switch to Steam auth but that's probably not gonna happen before a10.
Nope, because using the current webfiles would fail when they do not have access to the API.Their queries fail.. I've seen them fail in console (or so I thought)Your original webcode had none of the new functions in it.
Wouldn't it be very easy to just add a line of code for webserver2 or something of that nature?
What exactly do you want to achieve?Alloc what would be the best blocking to the API? Would a .htaccess work or something of the sort? I am currently running the API from my home PC and my webhost so I am currently wondering what the best protection would be.
Was thinking of adding this .htaccess inside the web folder.Nope, because using the current webfiles would fail when they do not have access to the API.
What exactly do you want to achieve?
Block all access to the web stuff? -> disable the web server by removing the webserver-folder
Block all access to the API? -> web page won't work that way either, so see above
Block access just for unauth users? -> enable authorization with the "protect" file
Anything else? Tell me what![]()
# This file prevents that your .php view files are accessed directly from the outside
<Files ~ "\.(htaccess|php)$">
order deny,allow
deny from all
allow from localhost
allow from 127.0.0.1
allow from MYIPHERE
allow from WEBHOSTIPHERE
</Files>
Yea I need to set something up so the API and Map is completely blocked and only allow by IP, Maybe if you get around to it you can make it so that a file is checked and if your IP or anyone you want to have access to the API and maps IP is in this file then they can have access and if the IP is not in there then no access at all. Of course localhost/127.0.0.1 would be set as default.Yeah, something like that is only possible with a firewall, the .NET web server classes do not allow to limit the access. Well, I could add an IP block later on the request handling itself of course but there's nothing like that for now![]()
See here under activation, part in boldBTW you talk about setting a "protect" file but there is no protect file in the folder is this something I have to make or am I missing something?