Merchant Archive
Thread: Merchant Barker module (also on DE board)
DataOutlaw wrote:
To get a "persistent" droid, you set it up and tell it to stay or patrol, group with it, then run out of range which is usually about 200m or so. You need to be far enough away that it shows up in your group listing as "out of range" Once you have that you can shuttle away and the droid remains.
Ouch, sounds irritatingly difficult. It would be really nice to set it up outiside the Starport (usually a good spot) and then take off from there.
This will be a really difficult setup procedure in a city without close neighbors.
I wonder if SOE is going to state and enforce any action against bait and switch advertising? It is illegal in most real world communities. Without a tie back to the vendor, it is easy enough to do just by accident if you raise a price (and the old price does not appear on the re-stocking window).
If B&S is going to be allowable, I wonder how widespread it will become. An out-of-the-way vendor advertising prices 10% lower than actually charged could gain a lot from it, at the cost of everybody's advertising losing credibility. Gresham's law implies it will become very common.
Message Edited by Haruspex77 on 03-05-2004 10:53 AM
Haruspex77 wrote:
It has been a month and a halfsince SOE " posted a fairly detailed plan" for Publish 8, that didn't cover the important details on the Merchan Barker droid. I had issues about those details, as have others.
Has anybody heard anything? Any discussions on the correspondent boards at least?
DocSavag wrote:
[snip]
I know they are working on several modules for publish 8 and I assume that the merchant one is one of them. I don't have any details about the implementation and doubt I will have until they go to test. That is just the way things work around here. As soon as they go to test I"ll try to get one of them and report about the features so we can make suggestions
That could be too late if their first draft is as bad as I think it could be. See my worst case description at:
http://forums.station.sony.com/swg/board/message?board.id=droid_engineer&message.id=76484#M76484
It could easily happen, and if it were released to test that way, the kindest act would be to put the module out of its misery. It would be too broken to be fixed, and nothing but a spam generator if released to live,
GoCanes wrote:
Funny post... ^_^
I thin the best possibility [snip]
I did write it in a light mood, but unfortunatly except for the values of some parameters exagerated for effect, I would not be at all suprised to see it implemented like that if the coder only got the information in TH's description to us. All the features there are the simplest sounding version of what was described. The result is laughably bad.
I want to be sure that the development management is exercising some control over their product, and know how foolish they will look if they allow the coding team to take the path of least resistance.
Your assumption about my background is wrong, the original probot nerf hit just as I was about to take Novice Droid Engineer, and I decided on Architect to keep me busy until DE was fixed. I'm still waiting, but I am a droid user and a supporter.
I hope that they will be able to accept some input once the result hits TC, but they haven't really changed function much at that point in the past, just parameter values usually. And Doc is saying they are stonewalling requests for prior info. One thing I am pretty sure of, you won't be able to have more than one active at a time. With luck, you might still be able to call a creature pet to hunt with while the one droid you are allowed is barking.
Haruspex77 wrote:
One thing I am pretty sure of, you won't be able to have more than one active at a time. With luck, you might still be able to call a creature pet to hunt with while the one droid you are allowed is barking.