Yea so Ive tried to just add it all to your sector file but the game dat file brainfarts again and the game fails to load, I think the problem lies with the fact you started a default MP game and not the scenario to start with sorry. Then I tried adding Akua to the scenario and that's no problem, Except you have already generated Akua in your game so adding the save file from a MP default game and merging into a scenario has a dozen different setting and thus crashes. I think the only way your going to get this to work is a new game and import everyones ships from old game that can be done and there PLY will bring there level and inventory over, bases on Akua however will be lost, yo ucan lay starter blocks and import them the old 4 file way, and you may notice I did that on the save I sent you on Akua 48 bases are spawned but they all set to public so more issues there getting ownership sorted. With scenario's if you get it from steam, when you go back to the scenario page it should have an Update button, if you hit that it should update the scenario from the TEMPLATE folder not the save file of your current game, so yes its the same as default just you have to manually click on the update button on the scenario page. That's how it works for SP, if your server is on another PC then you maybe transferring files from one to another etc. But I can leave manual instruction for dedicated servers if you have an issue just ask , we see what we can sort.
Thanks for trying to hard to help us get this set up with our saved game data. That was far above and beyond the call of duty, and I truly appreciate it. Thank you. Of course I'm bummed it didn't work, but it is what it is, right? We learned something in the process anyhow. We rent a server from GTXGaming which is where we have Empyrion, so yeah, dedicted server. Before I wipe everyone of everything they have ever gained I just want verify updating is not going to be a struggle or cause problems for players. It seems updating via the Steam scenario is simply enough for SP or individuals playing on someone elses dedicated server, but I wasn't sure how difficult it was updating the server itself. We have an internet connection slower then dial-up (1-3Mbps) so having to upload the entire scenario each time there is an update will get tedious at best. Hoping it is as simply as clicking that Update button then doing a Steam update on the server.
No shouldnt need whole thing everytime, updates usually consist of a folder change or yaml file change, should not need to upload whole scenario each time, just the files that changes , which I can list easy enough, scenarios though have a limit of 10MB, so not huge, but you must have net speeds like us here in Oz, where they say you have 7 megs of speed but really get 300kbs ! And they want 100$ a month for that ! Yep there criminals !
What version for MULTIPLAYER would I upload to our server? Would I just subscribe to the MULTIPLAYER scenario on Steam and then upload THAT to the server? UPDATE: Well, that is what we did. We subscribed via Steam Workshop and then uploaded that to the server. So far so good.
OK, so we decided to wipe the server and spawn everyone stuf back. That took F O R E V E R, but I think everyone is happy again. Question for you though: We did not realise Earth did not allow CV's before we began the game, now we have an established earth and a saved file. We changed the .yaml in the Scenario's folder, but as expected, that had no effect. Is there no way to change the fact CV's are not allowed on the planet without deleting saved game files?
Did you know in the MP Scenario on Steam there is no bottom plate in the Earth? You mine till you fall out the bottom and land on this piece of flat dirt. If you drive off the dirt into the blue, you teleport back to the surface. On the way down you run into rare ores that should NOT be on Earth. Was all this intentional? Usually one runs into impenetrable lava as a 'bottom plate' and no rare ores.
I think none of the starterplanets are allowed for CV entering, intentionally. I guess due to spare them the extra lag.
That was a condition I set so people would not overload the starters, more intended for MP public servers, it can be changed by editing all of the template yamls that will fix it for any new games, but to fix it so CVs are allowed on starters for planets already generated you need to edit the yamls in the save file for that game.
Yes there was a spelling error on one of the Ore types so rendered invisible causing the above problem, BUT ! Ive updated the scenario and corrected that so maybe you need to update your version to current, heres a link to current build. Whats Ores go where is entirely up to how you set up your scenario, there isn't a right and wrong so to speak, if you want to remove then delete these line from the terrain texture section. - [ ErestrumResource, 2 ] - [ PentaxidResource, 2 ] - [ CobaltResource, 2 ] - [ SathiumResource, 2 ] LINK to latest version http://steamcommunity.com/sharedfiles/filedetails/?id=1174524324
Updated this today and fixed the Arena start, problem with its height from terrain, it should spawn properly now with no trees in it. http://steamcommunity.com/sharedfiles/filedetails/?id=1174524324
I am unable to load into Hubble777, I get a COQ error and crash. http://www.mediafire.com/file/akj38h97803nm37/Client_180104-104623-92.log
Odd that the error is saying the planet already exists. Im assuming its having an error loading that planet because its already loaded it and maybe you changed something on the yaml after the game was started ? When did you last start a new game ? Is this an old game save ? Have you edited ANY files at all anywhere ? Have you edited the save file at all ? 2 servers running the game have no issues getting to hubble777 so from here it looks like a local file issue, without looking at all the files its hard to say, you could compress the game save and put it on dropbox I could then take a closer look if you have no solution still. 8.0 is a huge update for this scenario also, at 8.0 a new game will be needed, couple of months out still at a guess.
I didn't change anything on the yaml but this is an old save. I dont mind starting over but I guess I should wait until 8.0.
So have you updated the scenario from steam AFTER the game was started by any chance ? That could cause this issue as lots changed on the last few updates.
I just got one shot by fortress on Lucia moon at 750m, I kid you not. Fortress was not showing on maps it was so far away. Effective range of gatling on moon is 308m, so it seems to me something is way out of wack since 7.6
Config file , you can adjust all of that, I have not set up a config for the scenario yet so your running of the default one built into game, theres a HUGE re-balance going on at the moment though and we are about to get planets up to 64 times bigger than current so I want to incorporate all of that into the 8.0 update for the scenario if I can, it didn't get a 7.6 update because Im in the middle of re-doing ALL the POIs for the scenario, refreshing them and making loot a bit less abundant. So soon Jupiter, will actually be huge in my scenario, as it should be, cant wait to see what they do with the space playfields cos I expect there going to be come a lot bigger also.
UPDATE 8.0 - 8.0 is so complex vs this old version it wont be ready when 8.0 comes out, in fact the scenario is so big with so much custom stuff in it, that it could take a couple of months to complete, it comes down to how good the scenario conversion is from current to 8.0, the devs are working on all of that still, what Im trying to do is convert without changing anything on the terrain, same shape and textures, everything else I can add in manually at the simple cost of time, so yes there are plans to update it but I have no clue on the time line sorry.
Wonderful news. Take your time there is no rush. We play for recreation. On the other hand I wouldn't mind if you end up with a new scenario. Especially if it is a better way to do so, regarding conversion complexity and time consumption. The workshop is list of scenarios is thin after all.
no worries, m8 May as well make a new version for v8.0 and keep the v7.6 one for the option opt-in they will have for v7.6 like they have for v6
Thanks for the info. I love this scenario so anything you can give us would be great. Take your time.
