Deprecated: Function bp_core_get_user_domain is deprecated since version 12.0.0! Use bp_members_get_user_url() instead. in /home/lotj/www/wordpress/wp-includes/functions.php on line 6170
Deprecated: Function seems_utf8 is deprecated since version 6.9.0! Use wp_is_valid_utf8() instead. in /home/lotj/www/wordpress/wp-includes/functions.php on line 6170
Deprecated: Function seems_utf8 is deprecated since version 6.9.0! Use wp_is_valid_utf8() instead. in /home/lotj/www/wordpress/wp-includes/functions.php on line 6170
-
-
November 17, 2007 at 12:10 am #329
This new slicer skill, as its name implies, will copy a navchart that has been loaded into a ship’s navicomp. Now, there’s a restriction here, to prevent random slicer X from obtaining an infinite number of restricted charts.
Either:
a) Limit the number of times a slicer can do this per hour or per day.
b) Arrange it so that slicer X can only make one copy of chart Y from the same ship’s naivcomputer. Period. This won’t stop them from making additional copies from other vessels with the same charts.
-
November 17, 2007 at 1:45 am #3217
kudos for actually suggesting restrictions, but it seems to me (without being a code wizard) that you could exploit this by just changing the ship’s name to recopy over and over. if you can work a way around that, then i’m all on board
-
November 17, 2007 at 4:31 am #3222
There’s got to be some sort of internal function whereby each ship has a unqiue, unchangeable ID. Otherwise ownership/pilot/upgrades/fuel level/etc. would be reset as soon as you rename a ship. Make the limits based on that identifier, and not the name, even though the skill itself would use the name.
-
January 6, 2008 at 5:08 pm #4138
I like this idea. It would make slicers alittle more badass. No one takes a slicer seriously in game anyway.
-
January 6, 2008 at 5:42 pm #4141
I actually had an idea much like this, although I can’t seem to find it. I’m guessing it was removed due to the similarity to yours. But it was just like this, although there was a downfall. If you failed the skill roll, then you’d get a corrupt navchart. That’d like, mess up your datapad, or screw up the ship systems within it. Actually, that’s a good idea. It’d screw up your navcomputer. Causing glitches throughout the ship. Or something of the sort. But either way I love this idea, this’d make slicers very important, during wars. Infiltrate the Imperial ranks as a rebel, steal their charts and distribute them thoughout the galaxy or something, would be a great addition.
-
January 6, 2008 at 6:34 pm #4145
I like this idea and was actually surprised when I first found out about navcharts that this wasn’t already a skill. The problem I see, as Fishy pointed, is abuse. I would definatly want to see this as a top tier skill, so that everyone with a few slicer points on their race don’t automatically get it too.
-
March 19, 2008 at 1:06 am #5369
<BUMP>
I came up with a bit of extra info to add to the dead topic.
Syntax: Navcopy <navchart>
Requirements: MSTR Datapad, Slicer level 150, a toolkit, and a blank datachip(Or message disk)Upsides: Can copy any navchart.
Downsides: Extremely hard to master. Failure will result in a corrupt navchart that can shut down the hyperdrive of a ship. Which makes it inoperable until fixed.Maybe impliment two more skills. One to counter navcopy(Navcomp locked by code like doors) And another option to ship maintenance to repair hyperdrives.
-
March 19, 2008 at 2:38 am #5373
My idea for it: You can only copy ORIGINALS (ie generated by whatever chart mob/thing you have). You can only copy an original x times (3, maybe). So basically, if you manage to get an original chart, you can make 3 duplicates, which are uncopyable. If you get a duplicate, you can install it, but not copy it.
-
March 21, 2008 at 8:39 pm #5517
As much as I love this idea, I am hesitant to give level 150 slicer’s another great thing. Why not introduce this more towards level 150 pilots? It seems that once you hit 100, unless you get the feat, you are kinda a master pilot. Why not give something extra to pilots?
Other than that, I totally agree there should be a copy limit to the original. Protecting it, however, does seem a little unnecessary in my opinion.
-
March 21, 2008 at 10:47 pm #5522
Yeah, it could fit into piloting. Since pilots would be more likely to be able to interpret navigational data than slicers.
-
March 22, 2008 at 1:05 pm #2674"Rojan QDel":2bmhcfan wrote:My idea for it: You can only copy ORIGINALS (ie generated by whatever chart mob/thing you have). You can only copy an original x times (3, maybe). So basically, if you manage to get an original chart, you can make 3 duplicates, which are uncopyable. If you get a duplicate, you can install it, but not copy it.[/quote:2bmhcfan]
Your limitation would be abused. Clans with hidden sectors would post the original, copy it three times, delete the original, and then use the copies, rendering the skill useless to the enemy.
-
March 22, 2008 at 3:31 pm #5527
Good point. Any other ideas? <!– s:P –><img src="{SMILIES_PATH}/icon_razz.gif" alt="
" title="Razz" /><!– s:P –>
-
March 22, 2008 at 8:35 pm #5528"Final_Fantasy_Lover":1u4tgugs wrote:"Rojan QDel":1u4tgugs wrote:My idea for it: You can only copy ORIGINALS (ie generated by whatever chart mob/thing you have). You can only copy an original x times (3, maybe). So basically, if you manage to get an original chart, you can make 3 duplicates, which are uncopyable. If you get a duplicate, you can install it, but not copy it.[/quote:1u4tgugs]
Your limitation would be abused. Clans with hidden sectors would post the original, copy it three times, delete the original, and then use the copies, rendering the skill useless to the enemy.[/quote:1u4tgugs]
I think that should be allowed, otherwise the clans would be left completely vulnerable. With the capability of removing the original copy, you’d have to steal a ship in order to get to the sector. Well, not everyone is clever enough to actually delete the original.
Plus, if you posted the original, copied it three times, then the opposing clan wouldn’t be able to copy it again anyway?
-
March 23, 2008 at 6:29 pm #5541"Rojan QDel":apoucru2 wrote:Good point. Any other ideas? <!– s:P –><img src="{SMILIES_PATH}/icon_razz.gif" alt="
" title="Razz" /><!– s:P –>[/quote:apoucru2]
Instead of limiting whether a copy can be copied or not, why not simply limith the number of times a slicer can execute the command in a set period of time? If you make the skill a lvl 150 ability, it would be INCREDIBLY unlikely that any clan would have more than one person capable of doing it on hand at any given time.
Also, for failures, why not cause it to create a navchart that leads to a random deep-space sector? Hilarious little waste of effort if they screw up and use a botchedly copied chart.
-