Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Doing it can sometimes make the server crash due to the strain it puts on the server, which may be why it uses the last save when it comes back.
If it takes longer than a few minutes, which it shouldnt, go ahead and restart the server.
Try to keep in mind how many Dinos that command has to get rid of, its alot.
just try to do it before the next auto save cycle
cheat saveworld
cheat destroywilddinos
cheat saveworld
cheat quit
and then start up your server again and let it do the repopulation on boot up. The first saveworld is just in case it does crash your server, to prevent having to rollback more than a couple of minutes.
Its not so much the actual destroying of the dino's that lags the server, its loading all the dino's back in. The server needs to reload all those wild dino's from absolutely nothing and u can imagine how many dino's are on the ark. Wipe the dino's but tell everyone to stand completely still after so they not spawning in too many dino's at once as it needs to render all those new dino's in, hence the crash
Best thing to do is to do the wipe and walk away... come back after 30min, walk outside get some fresh air... a really long bathroom break, etc.