Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
The short answer is: there's no way to protect your map from a professional mapper. Or just as somebody in Internet said: 'You want to protect your map? Then never release your map!'
VMEX, most popular map decompiler, won't decompile your map if your map contains any entity with key 'no_decomp' set to '1'. But there're loads of hacked/cracked copies of VMEX which just don't care about this key. Actually, I can write my own decompiler if you find a way to defeat VMEX.
You can only try to make decompiling as difficult as you can:
1. Set 'no_decomp' to '1', at least no noob will be able to create a '_final_pro_megaultra_remix_2012_fix' of your map;
2. Use custom textures/models, so cracker will have to get them first using Pakrat. If you don't wan't to use custom textures because of their size, then just use custom VMT-files;
3. Put all important one-type logic entities in the one point, so they will look just one entity in Hammer. You can also put them inside the wall/floor so that they won't strike cracker's eye;
4. Hammer and CS:S have different points of view on how entities should be connected through I/O system. There're some ways to make logical connections which will be displayed as broken in Hammer, but actually they will work in game. Cracker may think that these connections are broken and there's nothing to investigate;
5. Entities can be spawned, deleted and teleported in-game. Use this ability to dynamically create and move entities in the places they should be, this will puzzle decompiling;
6. Let's pretend you have created some complex system which you don't want to be stolen, say a vehicle with all entities to control it and players view. So you have a model of this car, some buttons and logic entities around it. Select one important logic entity and put it far away from the car, on the other side of map. If cracker tries to select the car and all entites around it, he will not select this one important entity. He we'll have to understand each entity to find out what is missing. If I was a cracker, I'd rather make my own vehicle than trying to understand how yours one works.
These are most common tricks.