- Joined
- Jun 20, 2013
- Messages
- 3
- Reaction score
- 0
Hey guys. I know this kind of topic has been done, redone and overdone and that ship repair system is unlikely to change, but I just came up with this idea, and I thought it would be a good thing to post and let you discuss on it.
So, currently, the repair system works as the repair beams will heal any physically existing damaged blocks.
What I've read say for quite a while was: Repair Beams should heal the entirety of a ship, wether the blocks are there or not. Many people found issues with it, like keeping track of every blueprint for every ship you may have, making bigger entity sizes, more lag, etc...
I think my idea is slightly different. While keeping the current repair beams to work the way they do, a new system could be added, like a Building Beams. Here is how I think Building Beams could work:
-Blueprint importing, exporting, spawning would all remain the same;
-Building Beams would NOT repair damaged blocks;
-You can only rebuild your faction's ships, if you have the right permissions to do it (permission added on faction member permissions);
-Building Beams would be 2.5x (value is subject to change) slower than Drydocks, and could NOT be automated;
-To use, you assign a blueprint to the ship you want to rebuild and then fire the beams, probably at any spot on the ship. This could be done with a command line (/blueprint assign *blueprint*) or with a button on the interface that would assign the ship you are targeting;
-Building Beam use on any ship/turret would disable the ship's systems (thrust, weapons (missiles as well) and shields);
-Building Beams would use blocks stored on the Building Ship's PlexStorages to rebuild the damaged ship;
-If a blueprint tries, for some reason, to build into an active docking port, the game won't allow it;
-After you leave the Building Ship, the blueprint assignment would be removed to prevent lag;
-Obviously, the bigger the array group, the faster it would rebuild;
Also, I do understand that the future Dry Docks that are planned would probably make this obsolete, but this system's main purpose would be to work as a portable thing that you could (for example) rebuild turrets with after a battle, if you are far from home.
Opinions? I would like to know the viability of this idea, as it could be a practical thing to have in the future.
EDIT 1: Added more conditions, to attempt fixing issues found with the idea.
So, currently, the repair system works as the repair beams will heal any physically existing damaged blocks.
What I've read say for quite a while was: Repair Beams should heal the entirety of a ship, wether the blocks are there or not. Many people found issues with it, like keeping track of every blueprint for every ship you may have, making bigger entity sizes, more lag, etc...
I think my idea is slightly different. While keeping the current repair beams to work the way they do, a new system could be added, like a Building Beams. Here is how I think Building Beams could work:
-Blueprint importing, exporting, spawning would all remain the same;
-Building Beams would NOT repair damaged blocks;
-You can only rebuild your faction's ships, if you have the right permissions to do it (permission added on faction member permissions);
-Building Beams would be 2.5x (value is subject to change) slower than Drydocks, and could NOT be automated;
-To use, you assign a blueprint to the ship you want to rebuild and then fire the beams, probably at any spot on the ship. This could be done with a command line (/blueprint assign *blueprint*) or with a button on the interface that would assign the ship you are targeting;
-Building Beam use on any ship/turret would disable the ship's systems (thrust, weapons (missiles as well) and shields);
-Building Beams would use blocks stored on the Building Ship's PlexStorages to rebuild the damaged ship;
-If a blueprint tries, for some reason, to build into an active docking port, the game won't allow it;
-After you leave the Building Ship, the blueprint assignment would be removed to prevent lag;
-Obviously, the bigger the array group, the faster it would rebuild;
Also, I do understand that the future Dry Docks that are planned would probably make this obsolete, but this system's main purpose would be to work as a portable thing that you could (for example) rebuild turrets with after a battle, if you are far from home.
Opinions? I would like to know the viability of this idea, as it could be a practical thing to have in the future.
EDIT 1: Added more conditions, to attempt fixing issues found with the idea.
Last edited: