Jump to content
SubSpace Forum Network

Goldeye

Member
  • Posts

    10
  • Joined

  • Last visited

Goldeye's Achievements

Newbie

Newbie (1/14)

  1. Hi I have a feature request for a utility that would be extremely useful for SSCE Hockey Zone. We use eLvl Attributes to list the coordinates on the map that don't really define a region -- just a point. This is great because we can store the data relevant to a map inside the lvl itself. For example, we record the locations to enter and exit the penalty box -- or to drop the puck -- this way. If there was a tool that let you select a tile, enter a name, and then created a pair of attributes using that point's coordinates, it'd save us a lot of time. Here's how I'd have it work. 1. Select the tool 2. Click the tile (Example: 510,520) 3. Dialog box pops up asking for a name. (Example: Freq0Box) 4. DCME generates two attributes -- X and Y (Example: Freq0BoxX=510; Freq0BoxY=520) Potential features: 1a. Make a check box to choose tiles vs pixels 1b. Make drop/combo boxes to add or subtract pixels from X or Y. Thanks for the consideration.
  2. I'm not sure what triggers it, but some actions seem to get cleared off the undo/redo list. For example, if you do actions A,B,C,D, then try to undo all of them, it might undo D,C,and A, but not B. If I notice a cause I'll tell ya.
  3. DC is a descriptor for a voltage pattern, though. You can say 'connect to an ASSS' but you can't say 'look for a DC'
  4. You're so cold. I'll try to figure out how to fix the library problem (I think I know how).
  5. Here is a (20MB) i686 linux build of Discretion 3.2. Edit: Dropped it in sourceforge: https://sourceforge.net/project/showfiles.p...lease_id=672062 You must already have SDL, SDL_ttf, SDL_net, and SDL_image installed, or install them on your own. (apt-get install) Instructions: 1. tar xzvf Discretion.gz 2. cd Discretion 3. sudo cp libaedGUI-0.1.8a.so.1 /usr/lib/ 4. bin/discretion The third step is temporary until its handling libraries a bit better. Try Single Player mode first; Discretion Wars seems to be causing image trouble in Linux atm, but it does connect.
  6. From the TW history: Wow, TW hated him huh? Although he did his share of hacking, he also released the first freely available bot, which sparked advancement for all the smaller zones that weren't lucky enough to have access to TWBot and Powerbot.
  7. This would be just in the nick of time. I'm trying to get some asss work done from my mac and getting in the zone would be a big plus. Let me know if I can do any work to help port it.
  8. Um. Ironically, that might be awaiting refactoring from Bak. On the other hand, mingw/dev c++ might be working (and he mentioned possibly switching to mingw.)
  9. It's now set up with the GNU autoconf suite so compilation should be as easy as ./configure; make; make install But be sure to read README first -- it won't install to your expected location so you might want to use ./configure --prefix=somedir The svn is at https://ss-discretion.svn.sourceforge.net/s...t/ss-discretion and is easily viewed by browser just at http://ss-discretion.svn.sourceforge.net I've only tested it on mac but it should work on linux Only the client builds on -nix atm. The server, not so much. It's a pretty big svn setup atm since library dependencies and the like are included. If anyone wants to try to get it to properly configure and make those deps work from the root ./configure
  10. Cerium's idea is what I've had in mind. Closed source security that is simply tedious to break. Security through obfuscation to the point where it's just not worth it. A simple way to make it extremely challenging is to have the results of tests sent to the server and keep the server-side handling private. Private as in the binary itself shouldn't be openly available. An easy way to do this is to have a central server (say, the biller?) process and verify the integrity of output from the module. Give the security module numerous tests for any form of covert tampering. Check for binary integrity, a debugger attached, proper functioning of parts of modules, etc. Send the results, which should be different each time (using a different 'encryption' technique' for each test) over to the central server. If something's abnormal, cut them off so they have no way to test their hacks. Given, that would then be as easy to avoid as a ban, but such inconveniences can go a long way. The point is that it typically takes a lot longer to get past a well designed security algorithm than it does to make it, so the few people who try to get past it will be putting in a lot more effort than it takes to combat. In the first place, security not much more complex than continuum's shouldn't even be needed/released until people do try to get past that.
×
×
  • Create New...