安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
(100th Comment lol)
and also the bones?
can you make it so you can also see if an entity emits sounds similar to the "Entity Sub Materials - [id] path", but with the sound file the entity plays, and also tells you the pitch and volume of it as well? the reason behind this is because i also use Wiremod, and i'm getting sick and tired of playing needle in a haystack.
That would be one or more of your addons that misuse HUDPaint hook.
1. func - lua/weapons/gmod_tool/stools/rb655_easy_inspector.lua:487
2. DrawHUD - lua/weapons/gmod_tool/stools/rb655_easy_inspector.lua:1126
3. unknown - gamemodes/sandbox/entities/weapons/gmod_tool/cl_init.lua:54
Happens when you inspect world entitites. I tried on func_door_rotating
The reason why I didn't put the text and decided to go with tooltips for that info is because I didn't want to stretch the tool panel into oblivion, so you can see all the info without scrolling. Same goes for a box for GetTable(), I don't want to stretch it even further and I don't feel it fits this tool.
I don't feel like the color needs a visual representation because you can already see it on the entity you have selected.
I will fix the HitPos thing.
It would be nice to see actual text above the text boxes telling us what each box is for.
It would be nice to have a little box showing the colour of the object for the Color() box.
The click sound when changing through the options should be on the client only. (Don't see a reason for the sound being serverside/shared.)
It would also be nice to have a box for Entity:GetTable()
Finally I think the code should be cleaned up so that it's easier to read and understand. (Comments and stuff.)
-the tripwire mechanic should be more like a laser sensor wich "activates" the selected key when something passes through the laser
-model similar to the laser stool models
-some laser models, including and invisiblile one
-adjustable delay between passing the laser and activating the selected key.
I am paciently waiting for your answer
-model similar to the well known Emitter tool
-volume and hearing range of the emitted sound
-a loop option for the emitted sound(ex: in the normal mode, after you pressed the selected start key, the sound is emitted by the emitter, and after it ends you can press again to emit again. With the loop function, you press the start key, and the emmiter loops the sound clip until you press again the chosen key, wich now, acts like a stop key.)
-a browse menu, from wich you can select sound files in the local storage
-a save button, to save the sound clip, to skip the whole "browsing the computer" step
PS: I dont know if a limit of lenght should be implied or not