Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
Also just to clarify. Crash means the server stopped and is no longer on the list.
Timeout means the server is up but your unable to connect, if you had been connected your connection gets droped.
Did you try re-installing the mod?
About the only way the mod could get into an infinate loop if it some how got confused and was removeing and adding from the same object. Additionally even that can't happen unless someone activates the stone. There is no active code unless the user requests it to do something.
While I don't think it's possible for it to be adding/removing from the same object I'll see if there are some additonal safe guards I can put in.
The state of the object and any action it's taking is not saved so a reboot would intereupt any action and it would not auto-resume.
1) If there are a large number of corpses or death caches in your world, like with any other command that has to procress a large number of objects it takes so much time that the clients will timeout, but the server stays up using max cpu until the procress that is running finnishes.
This isn't something I can do much about with this mod. It would be possible to make a utility that could check for this problem and report back it's findings, it would run a little lighter so it wouldn't take as long but you still might get disconnected while it ran.
2) Someone is spamming the command causing it to run over and over and over. I'm going to add a forced delay to help prevent this if it's happening.
In either case someone has to be activating a stone for the condition to start.
But it did work before your update... But hey, keep up the good work, it did work... :-)
But I do beleive the issue is resolved.
STATS -
Solo play
No other mods at all, muchless active
Stone tools, Bow & arrows, basic resources, and my Dinos that deid because I wasn't there.
Description given
I realize the dinos are my fault for dying but I still blame you. Its all good though, you seem to be a good modder from the reviws, so thanks. Maybe it is just a problem with solo play. It's happened to me before.
Thanks for your hard work and good luck.
(^_^)
Blessed Be
I will work on some status messages.
Playing on the standard "The ARK" map and version is 1.0.8
Sorry for the delay, life happened and smacked me in the back of the head.
(^_^)
Blessed Be