Bak

So I wonder, do people get refunds for their tickets now or are they nonrefundable? I assume there were probably other performers to lead into him right?

I heard his multiple stops in London on his upcoming tour sold out within minutes... insane

closing the source adds very little to the security of the client. Anyways, I'm fairly certain my anti-cheat system will work, and I will encourage people to try to break it in an effort to make it more robust (after it's done, of course).

http://img.photobucket.com/albums/v622/bak2007/disc_tease_6_26_09.png I'm pretty sure I just finished the client-side anti-cheat. It basically records all interesting events into a log that it can replay to make sure the reported state matches the calculated state. All that's left now is for the server to make sure that the reported state (position packets) in the log correspond to actual packets the server got/sent, as well as actually replaying the log (either on another machine or on the server, not sure yet). Here's the list of interesting events it records: enum EventType { TYPE_SHIP_CHANGE, // player changed his ship TYPE_NEW_KEY_STATE, // player pressed / released some keys TYPE_TICK, // advance time TYPE_SENT_POSITION_PACKET, // position packet sent TYPE_TIMER_SYNC, // server <-> client timer synchronization TYPE_SHIP_CHANGE_REQUEST, // player requested ship change TYPE_OTHER_PLAYER_ENTERING, TYPE_OTHER_PLAYER_LEAVING, TYPE_OTHER_PLAYER_CHANGE_SHIP, TYPE_OTHER_PLAYER_CHANGE_FREQ, TYPE_OTHER_PLAYER_POSITION, TYPE_OTHER_PLAYER_WEAPON, TYPE_FREQ_CHANGE, TYPE_SELF_DIED, TYPE_OTHER_PLAYER_DIED, };

The problem is I don't trust my ability to come up with a complete list of "suspicious functions". It's much better to say what is allowed, rather than what isn't allowed. I also don't have a complete understanding of how python works under the hood, especially under adverse conditions of someone purposefully trying do something bad. This would require the python bytecode compiler, interpretter, and the import scanner to be bug free, which is just too much risk for an unknown amount of gain.

PerPlayerData has some bugs. New version eliminates that module entirely so the bug should go away too (I think someone else reported it in another topic). Also just finished up the a preliminary version of energy, update coming soon. I like the exhausts ... the question is, why do some of them have two playerboxes?

That's still too unrestricted for my taste. We absolutely want to prevent a zone owner from being able to do anything malicious to a client's computer. Maybe it's a better idea to figure out what sort of scripts are desired first then build a system around that.

winnar

find the bug: Particle* p = (Particle*)amalloc(sizeof(Particle*)); ... where's that bullet to the head emoticon, can't believe I'm stupid enough to do that... twice in one file at that show all emoticon's doesn't work... http://forums.invisionpower.com/index.php?app=tracker&showissue=15558

Right side -> http://img.photobucket.com/albums/v622/bak2007/disc_chal2.png

Yeah the should never get here is because, as far as I know, the system call does not work according to the spec, but nonetheless it's okay since you can manually restart the client and it works fine. The out of bounds frame is a weird one, I saw it too when others were scing. There's another safety on the right side if you're up to the task

Go in to discretion wars using Discretion in a Warbird. Make it past all the wormhole traps to the safe zone on either end of the map. Post screenshot. http://img.photobucket.com/albums/v622/bak2007/disc_chal.png

787 billion / $50,000/year = 15 million jobs for one year you could also look at the infrastructure projects and see how many ppl are working on them also you could look at unemployment projections from 6 months ago and from now and consider the difference to be jobs saved or created, unless you're saying unemployment projections are completely random and have no scientific methodology to them point is, it's not an impossible thing to estimate jobs saved

hows chaff work

I like it.

it would untrusted scripts that come from arbitrary servers that run on client computers. It must be very restricted (no examining the filesystem or writing arbitrary files). Something akin the the trigger system in Starcraft comes to mind.

except for when they changed scripture early on to match the message they wanted to send out

doesn't convergence of backpropagation rely on continuous functions (sigmoid instead of threshold)?

o no i've been spotted

ha no. notice he didn't provide leaving it as is as one of the options anyways I'm working on the anti-cheat crap now, got a week off coming up where HOPEFULLY ill be able to keep working on this and not on grad school projects (well definately not grad school projects but there always seems to be plenty to do at my parent's house). we'll see how processor intensive it is once I finish it. I got rid of PerPlayerData and replaced it with a Playerman module which keeps state about the players (which was scattered around a few modules that used perplayerdata before, now its centralized). Hopefully that'll make the system easier to use.

now the next questions is why it was split into the discretion forum

I agree perplayerdata is poorly designed... I'll probably change it to something better. if you don't like c++, you're welcome to write your modules in pure C. I'm more productive with things like STL, so that's why I chose to use C++. Scripting is a bit of a challenge, although in the long term someone might make a scripting module. In terms of code readability, I find most of the modules easy to read, even the ones I wrote years ago. There are a few exceptions I was thinking about redoing (Chat, most specifically). If the implementation scares you the header files that define the interfaces should be easy to understand, although I do think there needs to be a better system for looking up which module is needed for which functionality (like say I want to pid of the current player, which module should I use to get that information). The void* casts are only at the interface level (unless you use them in your code), in which case you can think of them as a black box that will make your module work. Alternately I think I could make my compiler issue warnings for missing void* casts, but I don't like programs that have hundreds of warnings since it makes it difficult to fine legitimate ones.

yes dis. sass fix the ships

you seem to imply that the law should determine what's right and wrong, whereas I'd argue it's be the other way around.

that's retarded. what constitutes hate speech is up to interpretation. all we have to do is say criticizing your government is hate speech and we "legally" limited free speech.