ストアページ
Space Engineers
全て スレッド スクリーンショット 作品 ブロードキャスト 動画 ワークショップ ニュース ガイド レビュー

Space Engineers

ストアページ
Space Engineers >  ワークショップ > Kreegのワークショップ
176 人が評価
(ARMCO) Starwars Master File
説明 スレッド0 コメント84 変更履歴
   
アワード
お気に入り
お気に入り
お気に入りから削除
Type: Mod
Mod category: Modpack, Planet, Other
ファイルサイズ
投稿日
更新日
2.228 GB
2019年7月27日 18時26分
2021年5月11日 2時50分
26 項目の変更履歴 ( 表示 )
作成者
Stollie
オフライン
Kreeg
オフライン
Kreeg や他のユーザが作成した 1055 件のコレクション を全て見る（全てが公開されているわけではありません）
24,111 ユニーク訪問者数
10,370 現在の登録者数
700 現在のお気に入り数

サブスクライブしてダウンロード
(ARMCO) Starwars Master File

Kreeg 作成の 1 件のコレクション
ARMCO Starwars Project Rebirth
10 アイテム
解説
Master File, for the ARMCO Starwars Project Rebirth.
This dependency file, is not intended for use by itself - but is used by the ARMCO Mods.
It will by itself, allow spawning of components, resources, voxels, and planets.
However, contains none of the equipment to use Any of that.

As a Dependency Mod, this is automatically loaded upon using mods that require this.
So you do not need to slot this into your world's mod-list, Don't worry about it.
Just ensure you have actually download it at least once.

This Master File, is designed around Rebirth's requirements & set-up.




Content

  • Resources & Voxels from the Starwars universe, in Space Engineers
  • Planets including those directly from Starwars Lore, with custom biomes & trees.
  • Resource & Component system, allowing finer tunning for balance, and a robust salvage mechanic.
  • Shared Assets, across the Project, reducing the file sizes of Project mods, making it easier to use the full project!

Main Project Link: ARMCO Starwars Project Rebirth
https://steamproxy.net/sharedfiles/filedetails/?id=2007374461

Legal
Star Wars, the franchise, is owned via Disney.
Rights Reserved properly to Disney & their respective owners, for such concepts, sounds, and similar matters.

Disclaimer:

All Rights to the content within, as per Steam statements & legal code, declare the original Author, IE Kreeg, owns their own model assets, code work, and all files of their own design & creation.
These ownership rights & controlling rights do not extend to Keen, nor any 3rd party, nor are invalided by any external force.
Your "usage" rights, are limited, and do not grant nor extended nor imply any rights to control, ownership or similar.
All code sections are owned by their respective parties: An example being scripter CS code, belongs to the scripters whom made it, and are referenced.
Keen has no rights nor ownership to any content or assets created by me or others involved this project.
Steam & Keen guidelines state this legal fact.

Anyone who fails to understand this, or attempts to illegally clone, acclaim ownership, illegally take control or similar to the mentioned assets in any manner,
Can, be DCMA'ed by Me, to legally take all such attempts down with legal force.
If you have a problem with this; You can go read Steam's exacting legal documents on the matter.
I am nicer than most, do not make me waste my time Going after theives.
84 件のコメント
< >
Kreeg  [作成者] 6月2日 8時08分 
Essentially no.
Master file itself hasn't broken however.

-- on another note : Enenera has new SW mods, so there's always those
kpoopert 6月2日 8時01分 
are the ARMCO star wars mods still being worked on, or are they cancelled or on hiatus?
Kreeg  [作成者] 2月12日 16時11分 
Unsupported mode, was added weeks after. After weeks of it being unremovable with no off-switch
In addition, I do not approve of my user base being harassed to remove & uninstall my mods.
Let alone after I had left WC, to suddenly have it flip off my workshop.

So no, turning it off isn't good enough.
They can fuck themselves.
Perryax 2月12日 16時09分 
Granted this feature is NOT elegant at all, but it can be disabled, although it will still complain when you use non WC blocks.
Perryax 2月12日 16時08分 
If you are referring to how WC deletes vanilla blocks or other non WC blocks, this feature can be disabled by using /wc unsupportedmode
Kreeg  [作成者] 2月12日 16時02分 
Their new management has not removed this code, and that very same code with their dependencies is causing the two WeaponCores to kill each other.
So not only would I suffer every single bug of WC, I'd suffer every single new 'build' of WC being exclusive which means possibly dozens of dependencies trying to kill each other, even if I removed the hostile code myself, a user just has to not notice 1 single instance of WC in their mod list, and mine gets deleted from the entire game.

So I would be constantly getting invisible errors in my user error reports, from possibly a single mod using WC of any kind just shutting mine down, flashing error code that doesn't exist, while concealing itself from crash logs.

Akin to if SE itself decided randomly one day, to uninstall other space games, lock them out, and hide that it did it one day.
Kreeg  [作成者] 2月12日 16時00分 
Anything of a weapon typeID gets deleted, blocked from placement, and flashes error-code red text onto the screen detailing how to uninstall the mod that added said block.
This text & deletion is hidden from the Crash log, meaning when this thing breaks another mod it has concealed that it was the source of the problem.
So lets say I add any block with a Vanilla TypeID of say any Turret, any fixed-mount gun or a flare, that block is then instantly deleted & locked from the world automatically, and no new blueprints are allowed to have them either -- effectively stripping entire typeIDs from the game itself.

(Part 1)
Perryax 2月12日 15時32分 
hostile code?
Kreeg  [作成者] 2月12日 15時30分 
It still has the hostile code, and I am not fixing their crap.
I rather spend my time doing game development than fighting a script mod that got full of itself.
Perryax 2月12日 15時28分 
I hear Weapon core is under New management and a new mod-ID