With the update tweaks you've done to the snipe verb, would it also be possible to fix the functionality of zoom spy gear such that we can use it to spy though areas that have been deliberately been made to not be sniped into?
It's kind of crappy not being able to use said spy gear for some of the most popular parts of the city.
Until retinal scanners and hand print scanners can be bypassed by use of severed or gouged parts - the only viable way to commit espionage/subterfuge is to be a faction member. Due to the overwhelming meta of heavy handed consequences (Which may or may not be factual) - this continues to be fairly non-existent.
I think we should take a good look at what slows down conflict topside and try to rectify it. The overall feeling I get is not just a theme of desperation and untouchable ness of topside/mix dynamics but an actual reality - this makes for a pretty dull game dynamic.
There was a bug where we were spawning %color items. This was due to us overwriting an items name after it was set without taking color into account, which wasn't something we needed to do. I've removed that extra step and this should fix the issue.
This will fix anything in an order carton now that hasn't already been spawned. If you have a %color item that you want fixed, put in a service request.>>
Question. As a tailor, I've experimented with trying to make clothing that does dynamically change its name with whatever color its been dyed to, such as a red shirt, periwinkle gloves, midnight black socks, etc. It has ALWAYS come out as having %color in the title when finalized.
Is this currently only something that the system can do as it is creating standard clothing, is there a specific syntax you have to use to get that %color out of the name of the clothing item, or FOIG?
Also, would it be possible to be able to comment on public @bugs while keeping OOC names anonymous on the public-facing side? As of now I believe it's only 'public comment with your name attached' or 'private comment that no one but admin sees'. Maybe there could be a 'Original poster' label that shows up when the person who submitted the @bug comments on the @bug report.
Sometimes their is a serious knowledge gap between what/why features/code exists and lack of IC/OOC documentation makes bug/feature unclear at times wherein a public bug can quickly allow someone with context to send an xgame or xhelp accordingly.
If I put Original Poster as a tag then people will know who submitted the bug, which I was looking to avoid. Open to other ways of doing it, but trying to keep IC names out of it while also making it possible OOCly to know who the other people commenting are, so it doesn't get confusing when reading comments.