Our code has been leaked...

[apophis775]

What I've been able to confirm, is that it was NOT Minijar that did the leak, but someone who hacked his account.

All staff members, are to use different passwords for Github (if they have Github) and the forums, and reddit.

If anyone gets a link to where the code is posted, please alert staff members.


Thank you, and expect further information soon.


Also, it should go without saying that you should not assist in distribution or discuss the contents of the illegally distributed code. Doing so on the forums may result in bans, and any information also falls under "Secret information", meaning it will be reported to the reddit staff for deletion.

Thanks for your patience with this, once I finish work on this film I'm on I'll address this more properly .

[Dreviore]

It's a shame it was leaked.

[slc97]

Is anything going to be done to forum members who downloaded the source?

[DMAN]

Shit happens, clean it up and carry on wayward son, you'll have peace when you're done. Peeps who nabbed it shouldn't be punished for taking the opportunity out of the chaos to do so, but the hacker duder should get his ass canned to hell. :^) I just hope shit goes smoothly.

[slc97]

I don't know, I think that if people downloaded the code after knowing it was an unsanctioned leak, there should definitely be some kind of consequence to that. It's justice. It's what Batman would want, dude.

[Neray]

kind of consequence to that

> free licence in native SS13 code base
> consequences for taking it
Laughed as hard as in goons leakage situation, when they started screaming about calling in da cops.

It's justice

There's no justice in our world, my friend. Yeah, I know, that's sad.

Anyway, it's a shame folks still don't use 18+ passwords at github. Plus, best way to keep code safe is to never upload it to version-control sources, or at least keep it on local machine in offline mode. But, welp, that's my opinion.

[apophis775]

My biggest concern, is that this will lead to min-maxing. Which is the whole reason we were closed source to begin with, to prevent that.

[slc97]

I'm just saying that if we have people on this forum who are openly admitting to downloading copies of this after it being stated that it was not a sanctioned release, that's stealing directly from the coders, devs, and apop who worked their asses off to code this place. There should be at least a slap on the wrist for that.

[apophis775]

Well, we are starting the process of reworking how all the damage works, so expect huge delays in other projects now, but anything they have will shortly be useless. We've been putting this off, but now that the damage values are out there, seems like we might as well.

[cdru]

Looks like there will be massive amounts of drama, maybe some Streisand effect

[Lorenzo_The_Marauder]

That's pretty shit, the code was kept secret to keep people from making the game worse by knowing the damage values and stuff right? Glad to see it's being taken care of asap.

[Neray]

but now that the damage values are out there

Like if someone cares about damage values in CM. Well, alright, it's quite obvious that shotgun slug does more damage than 9mm pistol bullet. It won't help you by any means, since RNG will fuck up your aiming and everything will still depend on your robust skills. Same for armor.

[Steelpoint]

I fail to see how people can't already min max.

With such a limited selection of weapons and attachments its really, really, easy to figure out the better weapons and attachments to use. Especially considering there's only one attachment in the game that boosts your weapons damage, and each weapon slot usually only has one or two accuracy attachments.

Maybe if Marines had access to dozens of weapons and attachment options then that could be a issue.

Edit: I've never understood this obsession over disliking people knowing things like damage numbers. What does knowing that the M41A bullets deal xx damage per bullet?

Absolutely nothing changes.

[coolsurf6]

The worst of this is now everything is bloody delayed and there go the Researcher update and the Sulaco Remap for what another month or two. Like come on guys, whats makes you think that stealing something that is meant to be hidden for the sake of RP a good thing? All you've were done is make us wait even longer and give the fucking owner even more work. This is just fucking stupid and these people should just delete all of what they have so it's back to being hidden!

[Neray]

This is just fucking stupid and these people should just delete all of what they have so it's back to being hidden!

Gonna...save...this...somewhere...oh god...my brain...it hurts...

[coolsurf6]

Gonna...save...this...somewhere...oh god...my brain...it hurts...

:3

[Iatots]

So what server is next on the leak chopping board? Aurora? Yog? ... vore?

[Sligneris]

So what server is next on the leak chopping board? Aurora? Yog? ... vore?

Too bad, all of these are already open source.

[EMT_321]

It might be nice for people who were weighing jumping in as a mapper/coder to see the general standards they would be held to.

[monkeysfist101]

It might be nice for people who were weighing jumping in as a mapper/coder to see the general standards they would be held to.

The general standards for anyone with a Reddit account is that Reddit is super easy to hack and you shouldn't have your Reddit password the same as any of your other passwords.

[lcass123]

I found the source and messaged apop , not going to release it but it's really easy to find. This needs to go down the goon route of allowing people to submit code changes otherwise rival servers may just start springing up.

[EMT_321]

The general standards for anyone with a Reddit account is that Reddit is super easy to hack and you shouldn't have your Reddit password the same as any of your other passwords.

I mean the leaked codebase itself, not account security.

[MilesWolfe]

Its like apop said, as time goes on the code will become worthless as we update the game so fourth.

[Fritigern]

My biggest concern, is that this will lead to min-maxing. Which is the whole reason we were closed source to begin with, to prevent that.

I find this an odd statement, since it doesn't take much trial and error to figure out what does and doesn't work effectively even without hard numbers. Having actual values out there would finally make it easier for us, the players, to show the devs where mistakes have been made and noob traps exist without having to argue all the time. But it's whatever at this point.

[ZDashe]

I find this an odd statement, since it doesn't take much trial and error to figure out what does and doesn't work effectively even without hard numbers. Having actual values out there would finally make it easier for us, the players, to show the devs where mistakes have been made and noob traps exist without having to argue all the time. But it's whatever at this point.

I believe the whole point of shying away from min-maxing is a gameplay design decision to let players enjoy the game, more so than enjoy winning. Sadly, a sizable amount of players still get hung up on the "ideal loadout" and fixed mindset of how to win battles as a marine. This will lead to the typical playstyle we see too often nowadays, which is fairly obvious without me spelling it out.

Just a food for thought: Have you noticed that newer players who overcame the basic mechanics make better squaddies?

Self-discovery and learning is one of the fun part of games. With min-maxing it extinguishes that element.