Architect Archive
Thread: 2 Ideas for Architect Items
Smart_Darwin wrote:Since neither of these ideas will ever be implemented, it is fun to speculate on what would be cool and whatnot. I like both these ideas, but in particular #2. However two issues would have to be resolved before in s realistic.
1. If a spraypaint idea would be used, I can see one drawback that would keep this on the shelf. I see unsavory images used as spray very often. While these are not offensive to me, I can see where others might find them so. This problem is manageable in CS because server admins self-police. If they don't like it, your go to banned city. I don't see that happening in SWG.
2. Most pics in my hard drive are non-starwarswy. Given the relative scarcity of corellian corvettes in the US, I can't imagine being able to snap any pics with a starwars feel (trust me, no one wants to see me ina Liea costume). Again, this is one of those problems I bet SOE would have a problem with.
Any ideas on how to solve these issues?
The biggest problem is that where custom skins and sprays are used for example in CS the player using it is online and logged into the game.
In SWG most of the time the source for the picture would be unobtainable as the player wouldn't be in game.
The idea of in-game screenshots has come uprepeatedly over the past few years -- a lot of people (including me) would enjoy having this capability. (I like the idea of in-game journalism.)
But we've also batted this idea around long enough to have identified some technical issues with implementing it. A couple of them have already been mentioned, but one hasn't.
Namely: If you let everyone have any number of screenshots, you dramatically increase the number of unique items that have to be stored on the server. It's not just the size of these images; it's the sheer number of them that the server would have to start keeping track of.
There are ways to cut back on this number -- we couldrestrict how many screenshotsany one character can have created at any one time, or restrict who can have have them (possibly by tying the ability to a skillbox) -- but such restrictions would be unpopular. Andno matter what, it's a lot more unique objectsthat would have to bestored.
So as much as I'd enjoy seeing this idea implemented, I don't expect to see it any time soon.
Still a neat idea, though. ![]()
--Flatfingers