Don't have an account yet? You can create one. Registered players can create up to three free characters to battle, team up with your friends and explore the worlds of the Nexus! To create a character once you have registered, click on Game Map at the top of the page.
This man was once extremely fat, but now the skin hangs loosely from his body in creased, dusty folds. His lips have pulled back from his teeth, exposing a long-rotten gumline. Despite the fact that his eyesockets are hollow, he appears capable of sight. He is wearing a Black Cloak, a Glow-in-the-dark Skeleton Pants, a Plate Cuirass, and a collection of trapped spirits that weave through the eye sockets of, a Silver Skull Ring. His eyes are a sinister blood red. The faint whispering of ghostly voices can be heard in their presence.
Liemannen has 3 augmentations: Ocular Enhancements | Utility Operations Key | Soldier Boosts. Seems like they give me extra eyes.
Or perhaps, my eye sockets are empty and the sinister blood red eyes are on some different place.
Joined: Jan 19, 2010 Posts: 2278 Location: Charlotte's Bakery University
Posted: Wed Aug 25, 2021 7:22 pm Post subject:
The Doylist explanation: Aspect text is just text under the data hood, and it'd be a ton of work for almost no reward (and some player annoyance penalty) to have specific aspects forbid specific status effects, even if that would make sense with the text.
The main problem (IMHO) is that these two parts come from two different sources (aspect vs credit store "items") and it is actually unclear to me which one should be more important.
Credit store trinkets should theoretically be more important ("I paid for it, so I want to actually see it on my character!"), but what if the aspect also comes from credit store? Which one should override which, then?
There are probably some other special cases that I cannot imagine right now.
So, in short, I am not suprised at Kandarin's reply, this feature feels like one of those nasty "iceberg" ones that look easy at first glance but turn out to be a tangled mess of conditions and other code under the hood.
Joined: Jan 19, 2010 Posts: 2278 Location: Charlotte's Bakery University
Posted: Thu Aug 26, 2021 8:10 am Post subject:
Badziew wrote:
So, in short, I am not suprised at Kandarin's reply, this feature feels like one of those nasty "iceberg" ones that look easy at first glance but turn out to be a tangled mess of conditions and other code under the hood.
We'd have to code up a whole apparatus just to prevent people from using stuff. And if the goal of the day is something that starts with "code up a whole apparatus to..." there are a hundred backend things that could use the coder time more.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Forum FAQ
Search
Usergroups
Profile
Log in to check your private messages
Log in
