Okay, I recently had a cool idea: Using EUDs to detect if a player, in most cases, Player 1, is a certain IP Address, this would allow you to make your map unplayable unless you are in the game, stopping games from being leaked, also, this method would allow you as a map maker to tell the player that it is a beta version, so they would know to look for another version.

At this point, all I need is the address for Player 1's IP Address, if we can get that, we can make it work, I've asked Zynastor if he can provide it, since Oblivion detects IP addresses, so maybe I can get it from him

lmao. Why not detect your username? 0x66FE28 is the first player to join the game's name (aka host). Add 0x22 for each next player. I use those in my table to see who has downloaded and who hasn't.

A player's own IP address isn't recorded as far as I know, so it can't be read.
You're better off using the name of the player.

Please don't bring up "spoofers".


Actually you could probably just create a non-eud "password" solution. If players think they can just look at the triggers, then what's stopping them from changing the IP Address in the first suggestion?
Given X larva, morph each larva into zerg units in the correct order.

Honestly, a single EUD trigger is a whole lot easier than coming up with a password system, though it doesn't allow others to host the map.

Well, you could easily make a simple password system, give them like 6 civilians and 10 beacons and they have to have the right amount on the right beacons, although that would waste locations. I would detect player name, however, I am thinking spoofing could do it. I'll see what Zynastor says about IP Addresses, maybe I'll have to go with the name.

You can always make a new account with names. Ip addresses are harder to get around.

yes, you can always make a name "rockzar8oywe" but would you know to do that?

Hmm. Depends on how clever they are. I'd work it out after 2 games, especially if my mates could still join and I could join other games. IDK if the bnet nubs are up to that.

Okay, so you play a map with the original guy as host. You then host it yourself. You press start, it goes, and instantly crashes/desyncs/defeat. From this series of events, you would gather that it bans you based on name/IP? Not even I would think of that. The only way I would figure it out is by opening the map and looking at the trigger, or have someone TELL me that's how you avoid it.

It wouldn't have to be you who hosted. I would, like I said, guess something was up if it was only me or specific persons getting dropped. I would probably try a name change next.

Everyone gets dropped unless the host is the original creator.

What's the point anyway? There's no need to protect your map since you're the only one who knows how to finish it, and everyone here knows that you made it. Just include a string "Contact user@something.com for bugs" and if anything you'll get more feedback and everybody wins.

prevents pubs from re-hosting it and spreading it/overwriting newer versions, in the case you don't update the version number.

The point is so an almost finished map doesn't get leaked and spread to the public, spreading a crappy version. Take what happened with Minigame Party for example, took a good month and a half to get rid of the majority of the leaked copies being hosted, I figure if I can fix that by adding a single trigger, why not do it?

Agree. I looked in to this when I made a quick VB program to log players you have played with. Your own IP is always 0.0.0.0.

Besides, talked to Zynastor and apparently IP addresses aren't stored statically in memory, so EUDs to detect them are a no-go, I guess it's names I'll have to go with.

I don't believe you should worry about protection to this degree until you've at one point made a map popular to warrant protection.

Post has been edited 1 time(s), last time on Oct 30 2009, 4:15 am by FaRTy1billion. Reason: Unrelated, flaming.

If it's really necessary, couldnt you use eud's to detect a password, like, where you type it in? That way only the mapmaker knows the password for early testing and such... Although i dont really know much about eud's, from what i've heard this seems like it could be a logical choice.

text detection desyncs, since it isn't shared all the time. I think this one would be a nightmare to trigger, but only because I don't know exactly how to do it off the top of my head.

It isn't shared, but there is ways around it. It's not really a nightmare to trigger, it just takes a bit... You have to read all 11 lines and for each of those read for possible username lengths. Each of those triggers should set a switch...