tigercat2000
-
Posts
723 -
Joined
-
Last visited
Posts posted by tigercat2000
-
-
re: we 510 now
thread therefore not necessary, lockity lock
-
there's literally no reason to use the singularity as-is
it's way more dangerous and provides 1/10th the power
-
I don't know that this is even slightly possible. The job controller doesn't even start before the antag selection is complete.
-
we 510 now
Do we have to update our clients to the 510 beta version now?
for the best possible experience, yes
it's not strictly required however
-
we 510 now
-
Why not just use [field]s? You can enter [sign] into a [field], as far as I know.
-
Seriously, this needs to be dismissed outright.
510 isn't a magical "fix to all lag" as the sensational headlines love to say. All we use it for is replacing the overhead of btime in our process schedulers- It means that things like Atmospherics and Mobs will properly throttle themselves with no overhead costs, therefore helping the server recover from a bout of lag- It doesn't change our network connections, which is the major cause of movement lag.
The only other thing it does is improve tree lookups, which only mildly helps performance. We aren't going to suddenly run like -tg- with 510.
-
more maps aren't going to happen, metastation was fucking a pain enough on it's own and it's still not fully operational
-
Not true, we've moved to beta versions before, there's nothing stopping us from doing so again.
Currently, we are just waiting around because 510's beta still has some issues, and we'd kinda like to see what other codebases are doing with it.
That, and, no one has bothered to fix the conflicts with the current 510 work we have, so.
I think there may be some miscommunication there?
https://github.com/ParadiseSS13/Paradise/pull/3763
Here's a 510 fix that was stopped in the pipeline from hitting the 510 branch.
It's not a fix. It doesn't fix the merge conflicts, all it does is add a feature which is fairly controversial.
-
Not true, we've moved to beta versions before, there's nothing stopping us from doing so again.
Currently, we are just waiting around because 510's beta still has some issues, and we'd kinda like to see what other codebases are doing with it.
That, and, no one has bothered to fix the conflicts with the current 510 work we have, so.
-
Hot damn. No one has ever used it?
It allows you to control vents n' shit via a terminal, it's pretty cool, but also kinda difficult to use, since we never ported shit for airlock controls.
-
Never let me have wizard robes.
-
Xenobiology cannot spawn aliens that can infect other players. The gold cores can only spawn simple animal xenos, which have no organs, and can only blindly attack.
-
On the other hand, we do have Vulps, a purely cosmetic reskin of Taj which are barely different than humans at all.
I'm sure curious why you're throwing shade when you personally made:
Snowflake: The race.
40% brute resist, can't be knocked down, instant-aggressive grabs, for not being able to wear glasses and having a token additional "weakness".Powergamer: The race.
Stop throwing petty descriptions around, both of you. Attacking someone's work because you don't like their opinion is not acceptable.
-
It's clearly shown in the error, "btime.dll not found but is enabled, world shutting down."
Is btime.dll missing from your repo? It needs to be in the same directory as the paradise.dmb.
-
Take what fits, improve para, and chuck the rest. There is no moral quandry with reverse-engineering code for quality additions, we're not cloning goonstation and it's not going to sap their playerbase if we work to better ourselves.
We are not going to take anything from Goonstation until their staff have recovered and we are able to gain permission to use it. Taking the code from the leaked source without their permission would be blatantly violating our AGPLv3 and CC-by-at licensing, which weakens our own protection.
-
Jesus christ.
Baystation style surgery is not staying around, even if the entire fucking organ PR was thrown out. It is not an expandable system, we can't continue improving our code with it in place, because it's such a fucking terrible system that making more surgeries is one of the most difficult things to do in the code.
Be glad we don't use surgery rags, and bother to have any sharp object work.
-
Two ships shouldn't share one dock, which is why it doesn't current dock where the admin shuttle does. That, and, arrivals is a pain in the ass to modify with the shitty mapping tools.
-
You're god damn right actually.
But I swear there will be some asshole goodytwoshoes shitbag scientist that calls sec on you for vandalism one day.
Because it is vandalism?
-
Also why do we have three entire species that we can never see in any normal round unless a bored admin gets a break?
Why do we have anything that can never be seen until an admin decides to use it? The ACJ? The RIGSuits?
They are for events, when someone decides to do so.
-
Not happening. Nucleations were made specifically as an admin-only race.
-
No new posts in a week, No posts from original author in even longer. Moving to resolved, please open a new complaint if you have any more concerns.
-
It would be 6 lines to completely remove fat people being able to eat other people. Tiny.
But I will fucking fight to the death over not removing it. The code is fine. People abusing it get banned. People who find something creative to do with it, great for them. People are salty at getting killed or fucking think that removing one thing out of the thousands of equally ridiculous things, or those that just look at it and go "eww vore" because the vore servers based their code off the original code here from bay.
-
My bullshit tolerance for the day hit it's limit, sorry. Don't remove things because of a one off event.
kill this shitty thread
in Suggestions
Posted
how the hell do you interpret "touching a light burns you" to be "it's just there to piss people off"