tigercat2000
-
Posts
723 -
Joined
-
Last visited
Posts posted by tigercat2000
-
-
There is a quick way to solve this, you know. Just turn on antaghud. It prevents almost every method of respawn.
-
Unbound/BestRP had it, they run off of baycode last I checked, I vividly remember running around as a bright red IPC on their server when I played.
Unbound/BestRP code is massively out of date with baydev, if I recall correctly. This would have been easy-- before the whole organ overhaul.
-
Uh, Bay doesn't have colorable IPC's, last I checked.
I don't think this is even feasible; Skin color is handled at the external organ level; IPC's use robotic external organs; Robotic external organs do not get colored.
-
Well aside from the massive absurdity that was paying $500 to port LINDA to paradise (you guys really did that?)
I'm glad to hear the problems with EMP's not damaging mechanical body parts (hearts and eyes in particular) and emitter fields not damaging you, are simply bugs.
It was a code bounty, and I will point out that only the head admins get to control where donation money is spent. In the end, it was refused.
-
I am so confused right now, doesn't it bother them having a non functional atmos-system?
If only i would have known what it meant when there was this conversion to Linda going on. I honestly don't understand how that PR went through, we practically downgraded the sort of working-ish atmos-system we had to something that was fundamentally flawed and basicly proven not to work.
It's been brought up before on tg when switching to ZAS gets dicussed, some players don't like the idea because "it means a random assistant can break a window in maintenance and space the entire station." Of course, bay had that 'issue' solved literally years ago, by placing emergency airlocks around, and it was never an actual issue in practice.
Other players didn't like it because they felt like space was already too deadly - this coming from a time when you could down a cup of coffee and spacewalk even without your internals for a few minutes.
And as for the PR going through - I mentioned the reasons why, earlier, when I was ranting. It goes through because a coder hasn't enough good sense to understand what he's actually doing with the changes, and because any feedback from the players is completely ignored and disregarded. Coders know best, and you don't get to disagree.
Recall a long time ago, tasers used to require multiple shots to stun someone, with each shot slowing them down progressively further. It worked well, everyone was satisfied with it; fox decided it needed to change. After some voting where the playerbase said they didn't like the change, the coders gave a sort of 'who gives a shit what you think'; fox went back to the drawing board for a month or so while we were stuck with tasers we didn't want, then foisted a slightly new variation of the tasers we didn't want on us.
And in playing recently, I've noticed a few other changes - emitter fields are no longer lethal, EMP's no longer damage mechanical limbs, many non-sec/non-antag weapons are extremely unrobust (including the crossbow which takes upwards of 8 shots to kill someone) that just makes the game feel horribly hugbox to me now, and that's in addition to a cowed and timid playerbase too scared of bans to actually have fun.
Excuse me? What the hell are you talking about?
LINDA was planned for months; There was a 500$ bounty of donation money out for anyone that ported it. All of the coders at the time, unanimously agreed that we needed and should switch to LINDA. It was priority 1, which was over -tg- mining along with a whole bunch of other things.
Emitter fields haven't been touched in months. EMP's definately do damage mechanic limbs, I have no idea what you are talking about with that.
Most importantly, this can't be stated enough times: This codebase is not a democracy. It is not on github for players to mob-mentality changes; It is on github for anyone to contribute to.
We don't ban for no reason, we have very well established rules, and they are there for a good reason.
-
If bay does decide to kill off virus2, I guess -tg- diseases would be the only option left; I don't think we should preemptively nuke it and move, though.
-
Hate server
Top fucking kek.
-
Hell no.
-
Nonononononononononononononononononononononono.
That's my response. If we want disease reagents or some such, we should upgrade virus2, not nuke it and use -tg-'s system.
-
Would you be opposed to making it fast enough that it would be realistic to re add the ability to make people fall and fly around when the pressure in a room rapidly depressurizes?
That was the best part of ZAS.
LINDA will never do that. Not without turning it to process every tick, or something ridiculous like that, which is "crash the server" territory.
-
Kevak, not that simple. We can't just swap back and forth between ZAS and LINDA; We would have to undo months of work to enable ZAS again, which isn't an accurate representation of how it would run
-
10. The appeal is handled by different admins than the banning admin, to reduce bias.
10a. The banning admin can add factual information (such as evidence - screenshots, chatlogs, etc.) to clarify things, but otherwise cannot/does not post in the thread
10b. Admins (excluding banning admin and any other admins otherwise involved directly) take an anonymous vote on accepting/denying the appeal, their conclusion will be posted in the thread and the thread closed
this is misinformation, and not how appeals work at all
-
This isn't feasible without porting bay's hardsuit system, and porting bay's hardsuit system would require someone willing to spend hours fucking with it, since it is so damn incompatible with everything.
-
PR numbers are assigned in order, so the only way to prevent from taking a special number is by looking for the most recent number in open and closed pull-requests and issue reports.
But, it is sometimes unavoidable to take a certain PR number that others would rather have, and it's not a big deal anyhow, just some fun when people do manage to get it and do something with it.
-
Alex is technically correct, the issues section is not just a bugtracker.
But it does piss off most of the coders if you put feature requests in there, when we have a suggestions form, it gets a lot harder to sort through when there are tons of "what if"'s in there.
-
If no coders want to code it, and the person making the suggestion can't code it, nothing to do about it.
-
Most suggestions here die either because:
A. No coder takes a liking to it
B. It's simply not feasible with BYOND
C. It's an insane idea.
-
Looked for the worst resolution of a little sister, then fucked with it in photoshop until it fit.
-
Nothing has been "removed" from duct-tape. I ported it primarily as a crafting ingredient, from Baystation. I know HippieStation has a much different version.
-
-
3. Since we have the new AI radio where you can access channels via shortcuts like :c we could finally get rid of :h for holopad. If you are projected on a holopad you should default to talking via holopad and not talk locally at your core. The need to talk locally at your core has been reduced to the occasions where someone is standing inside your core or when coms are out and you have to talk via intercoms again, which would both still be possible, just not while you are visible as a hologram.
Not quite that simple. The holopad speech code is a bit insane, iirc, and it bypasses the language systems with magic.
-
We actually could speed LINDA up fairly easily, just one value.
However, the performance impact from that is extremely significant, and problems would arise as pipes stopped working as fast as atmospherics proceessed, and things like the rooms not equalizing would still be an issue. We aren't going to get ZAS-like atmospherics using LINDA, it's not designed to be that violent.
-
Autopsy code is insane enough as-is, and for that matter, broken enough.
-
shudders
I rather hope it doesn't rest in peace. It should rest in hell, where caelcode belongs.
Allow IPC's to change their body color.
in Suggestions
Posted
It's definitely not that simple. I spent about an hour looking into this, and yes, I did try to just enable the has_body_color flag; It doesn't work.
Why don't I just give a detailed explanation of why it doesn't work?
So, first off- the HAS_BODY_COLOR flag does not actually control if you see the body color preference; it's snowflaked into races checks. But that's a simple solution. So, moving on.
You select a body color; When your character is made, their r_skin, b_skin, and g_skin variables are set according to the color you selected.
From there, it moves to the icon generating phase.
Human base icons are now generated at the organ level; https://github.com/ParadiseSS13/Paradis ... an_icon.dm
When humans want to make a new icon, first they check if anything has changed, or if they can use a cached icon that was already made. https://github.com/ParadiseSS13/Paradis ... #L231-L347
The specific part of this check that handles the actual base body, their arms, chest, head, so on, is here: https://github.com/ParadiseSS13/Paradis ... #L278-L297
That code calls organ.get_icon, which is here; https://github.com/ParadiseSS13/Paradis ... m#L72-L113
Colored parts are handled in organ.get_icon, specifically, right here; https://github.com/ParadiseSS13/Paradis ... on.dm#L108
If you notice, that part is behind an else; First, it has an if(skeletal), which means it returns the skeleton icon if that mob is supposed to be a skeleton.
Then, second, it has an else if (status & ORGAN_ROBOT), which returns just the robot icon, without ever calling the part that blends skin tone.
In order to fix this, we would have to add a color blend behind the else if (status & ORGAN_ROBOT) check; But, we can't do that. If we did, tajara and everything else with a skin color would color robotic limbs, which isn't desired.
Is that a good enough explanation of why this isn't feasible?