Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×

Comment Article is misleading (Score 1) 189

The bug doesn't infect you just because you played with somebody who had the bug. They have to be hosting the game, I'm almost positive. Then for you to share it with somebody else, you'd have to host the game, etc. If you don't know you have the bug, then I could see this happening.

Still, they don't even mention if the bug is "saved". I don't think it is, there's lots of local server variables you can modify on the PC by editing RAM address values (like with Cheat Engine) and you can modify all kinds of things like making the game temporarily harder and increasing the drop rate. These values are not saved to the character. That said, badass *could* be something that is saved, but the article isn't clear. Has anybody tested? I think we're jumping the gun here, assuming the worst.

Comment Re:Why does this happen? (Score 1) 189

No, you're right, although you're not explaining it fully. The game is ad-hoc rather than central server. Instead of having dedicated server boxes which host games for clients to join, instead one player hosts a local listen server where they are both a client and server, and then everybody connects to their server. The reason why this matters is it means that if you mod your xbox and you host the game, then the server is modded. Everybody else talking about clients is full of shit.

Comment Re:Why does this happen? (Score 1) 189

This has absolutely nothing to do with trusting clients. Its the fact that the game is hosted on local servers, not dedicated servers. If the person hosting the game is modded, then the server is modded. The clients aren't trusted, but they don't have to be, that has nothing to do with it. Its the server. They don't use dedicated servers like Call of Duty, but personally I hate those.

Comment Re:Why does this happen? (Score 1) 189

I'm assuming that this happens because the server is trusting client stored data. That's approximately the same as not validating ones inputs in a fill-out-form. Why in this millennium would anyone ever trust data stored on a client without validating it first? Isn't this 2012? Or is there some other way this could happen?

Wrong. This is happening because in Borderlands 2, there aren't dedicated servers like in Call of Duty. When you play multiplayer, you host a local server yourself. Then everybody else connects to your server as a client. The server is not trusting client stored data, but the server ITSELF can be modded and compromised.

Comment Re:What kind of question is this? (Score 1) 618

Picard has the characteristics that I'd rather be myself, plus he's the one I would rather serve under if I was in Starfleet (I'd be a red-shirt anyways, and that wouldn't end well under Kirk).

I'm actually wearing my expendable "redshirt" right now xD

I personally always liked Picard better. Maybe its because TOS was already being phased out in favor of TNG, but I always thought Picard was so much more impressive than Kirk.

Kirk was a brave hero, your Flash Gordon, sure. And he was good for that.
But Picard... he was.. well, Professor X.

Comment Re:This shouldn't even be a contest (Score 1) 618

I'm with you. I kinda want to like DS9, but I just can't get into it. Meanwhile, Voyager, which is actually probably cheesier than DS9, feels less cheesy somehow. I guess I just need to have that classic Gene Roddenberry setting, a lone ship exploring the far reaches of the galaxy, encountering new aliens, etc.

Comment Re:This shouldn't even be a contest (Score 1) 618

No, rather, Kirk was a war-time consigliere, where Picard is a diplomat.

Kirk would send some red shits in, they'd die, he'd realize something, and then they'd win.
Picard would already be 4 moves ahead and would have lead you into a xanatos gambit where he can't lose.

Kirk is the action hero, Picard is the thinking man.

Comment Re:Does this imply FTL comms? (Score 1) 210

Oh gosh no. First, this does not mean that quantum bits state can be known "in advance" (whatever that means, if you detect the state before collapse, does that mean they could later collapse into a different state? If so, that's pointless. If not, then its already collapsed). The way I read the article, it doesn't mean they can observe state without collapsing, but rather can gain some information about it before collapsing by effectively stretching out the collapse into a series of gradual collapses about different axis, collapsing different parts and gaining information about them as you go. So that doesn't follow. Furthermore, even if you COULD observe a quantum entanglement without collapsing it, how does that help you with remote communications? Merely transmitting quantum information doesn't enable you to communicate in any meaningful way other than random data. You simply cannot transmit classical information (a message) via quantum information. Lets say two qubits are entangled, you still have to send one of those qubits to the other person at sub-c, so what good is having entangled qubits at that point? There's no way to entangle two qubits, send one to someone, and then control the collapse, which is what would be necessary for FTL comms. Even if you could observe it, that isn't good enough. Sorry, as cool as FTL comms are.

Comment ITT Quantum Misconceptions (Score 1) 210

Jeeze, I'm really starting to think that most people just shouldn't ever talk about Quantum, there's so many misconceptions and misunderstandings that trying to give people a little bit of information, since its so wildly out of context, even in the wrong context (misconceptions), that it only drives them further away from the truth, from reality. People latch onto the wrong points.

I barely understand Quantum Physics myself and I can tell that TFA makes all kinds of wild leaps in logic. Most of these things aren't true, and the way they explain the Schrodinger's Cat experiment makes the classic misunderstandings.

The reality is far less sensational: http://www.nature.com/nature/journal/v490/n7418/full/nature11505.html

Comment Define Repository (Score 1) 383

Skip the version control, and just say you need a Repository. (Both software and hardware). You need a server to save backups to (manager should be familiar with the idea of backups and why they're valuable) combined with a way to manage changes over time in case you went the wrong way on something and need to back up. Tell them its software to keep multiple, automated backups just in case. Also explain that code is very complicated, and you cannot work on the code simultaneously, so explain that multiple developers working together gives you different versions of the code that have to then be merged / blended together. To make sure that merge didn't mess anything up, you want to keep backups of all the different versions. Pretty simple.

Slashdot Top Deals

"Ninety percent of baseball is half mental." -- Yogi Berra

Working...