Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I don't encounter the problem when opening the e2 editor.
However I've done some debugging and the problem seems to be a compatibility bug with wiremod itself. This core adds a lot of e2 functions which cause a client overflow when they get loaded on the client.
I've created an issue on the wiremod GitHub, see here [github.com]. Once it's resolved this should hopefully fix your problem. Otherwise I'll have another look.
I'm aware of the crash when you reload/restart the singleplayer world. It should work on the first load though.
The current workaround is to restart Gmod completely.
There is already a GitHub issue [github.com] to track this but, however I'm not sure what the root cause of the problem is.
If your problem differs from the already existing GitHub issue please provide more information and steps to reproduce it.
However I would also like to allow each client itself to allow/block the dhtml functionality due to the previously mentioned abuse concerns.
I've tried to implement the DHTML element on the experimental branch on github but haven't found the time to continue working on this feature yet.
As mentioned before, some actual use cases for this would be appreciated so I know what to focus on.
And feel free to create a Github issue to discuss this in more detail e.g. with example code etc.
I've never used the DHTML element myself.
I took a quick look and security might be a problem. As I understand it the website gets loaded by the client that creates the DHTML element.
Therefore it allows the e2-creator to open any URL on any other player, which is something I'm not willing to implement.
That said. It might be possible to allow only the e2-owner to use DHTML elements but block it on other players or add additional features to the buddy system to explicitly allow the usage of DHTML elements.
Aside from that, there seems to be a feature that allows Javascript to execute Lua code which also might present security problems (I took note that you can disable this specific funtionality though)
I will have to look into it a bit more.
Do you have any specific use cases in mind for DHTML which would help me understand what features you need?