Hello Galactic Survivalists! We have some changes & fixes now released on the public branch. As always please note: Report bugs and issues for the public release right over here: https://empyriononline.com/forums/bugs.24/ Patch: 2022-04-14 v1.7.9 (B3724) Changes: - Added new config files "_PoiGroupsConfig.yaml" & DamageMultiplierConfig.ecf See "_PoiGroupsConfig_example.yaml" & "DamageMultiplierConfig.ecf" in ../Content/Configuration - DialogueSystem: Update function OpenHtmlWindow & added CloseHtmlWindow(): See Dialogues-config-and-examples.txt in ../Content/Configuration - Implemented a Join Queue system for MP servers (example can found found in the stock dedicated.yaml): Code: ### Number of players that will be put into a waiting queue if the server is full # PlayerLoginFullServerQueueCount: 5 ### If specified, the number of parallel logins to a server are restricted to this number. This is important when you expect a big number of people to login at the same time # PlayerLoginParallelCount: 5 ### Add steam ids for preferred players that will get a better position in the login queue # PlayerLoginVipNames: "steamID1,steamID2,steamID3" Fixes: - When a player has too much money in their Bank Account the Station Services don't work - Missing icons "Datapads", "ExplorerToken" etc EAH: - https://eah.empyrion-homeworld.net/download/patch-notes-emp-admin-helper-full
I don't understand what the PoiGroupsConfig.yaml does that's any different from putting your POIs into groups in creative and then calling the group in the playfield_static? Why do you need the PoiGroupsConfig.yaml? Can you tell me how it helps?
Its a file where you can define groups of POIs and can reference this group in the playfield.yaml Spairs you writeing all POIs every time in the Playfield Files
Thanks @Taelyn . I guess I'm not getting what capability this adds, because you can already define groups of POIs and reference that group in the playfield, you just have to define/assign them in creative mode. So does this make it so that you can have one blueprint in multiple groups? Because that would be a new capability, albeit I'm having a hard time finding a use case. Also, there is one place where you have to define the POIs in a group manually, and that is orbits. Will this work for Orbits to simplify their setup?
When you have a lot of playfields they invariably utilise the same blueprint groups. As a result when you need to make a change to that blueprint group you tend to have to go into a lot of files to make the same changes. So essentially it's a huge time saver for anyone that makes these sort of changes.
Yes it will work for Space aswell. For the rest exaclty like Escarli explains, just spairs time as you only have to make changes in one file, not in 500 playfield files
I am trying to mix Hangar doors with blast doors and in order to make area airtight, I cover blast doors surface area with force fields (green in the photo) on both exposed sides (top and bottom). The result fails to make area airtight and only if I cover both hangar doors and blast (one side only) seems to work. Is this working as intended or is it a bug? The attached epb is the final one.
The hangar doors "seal" which make them airtight is in the middle of their 1-block thickness, so if you put your blast doors seals (the forcefields) each side of the blast door it then leaves a wide gap above and below as seen in this screenshot (red cube is to show the 1-block thickness) : That's more than enough space for a 02 leak.
The POIGroupsConfig.yaml will work with the UseEachBlueprintOnlyOnce parameter. Will it also work to configure the AuxiliaryPOIs: and IsAuxPOI: True parameters?
Lmao. The _PoiGroupsConfig.yaml doesn't work. I troubleshot it for hours this weekend. It errors out on the first line. I posted a Bug Report in the Bug forums.
Because you cant use the file out of the box. Same you cant use the example playfields files out of the box. You have to write your own in the correct way. There example files with fake names
The instructions don't say "You have to write your own file", they say: # Rename the file to _PoiGroupsConfig.yaml # Place it in the "Prefabs" folder What about the 3 dashes on line 17? Should those be in the new file you write yourself? Or should they be remarked out? That also isn't clear sir.
Read the example file carefully. It contains 2 examples. one for the yaml file and the other for the playfield_static.yaml The file it self functions fine if make your own Best is to leave it alone atm. The complete config will change in v1.8
The 3rd person view when piloting is still a problem. Why does the camera go higher the higher the ship is? I have re build my main cv bigger, and now from the top bridge, I simply don't see the cv at all. And if you are wondering what kind of CV I have made, it is simply Ulysses 31 spaceship.
That's down to how the cv was built. You can sort it by correcting the centre point of the blueprint. By using the prefabinfo 'name of blueprint' -clearpivot command. Won't fix a build already spawned in as it changes the blueprint itself, doing so will fix it for any subsequent times.
Great advice on the -clearpivot. You can also adjust the 3rd person view with the 'page up' and 'page down' buttons, and in free look (left alt), the mouse wheel will adjust distance.
