Jump to content

Client console risky?


Recommended Posts

  • Premium

game.py

	def __Console_Enable(self):
		dbg.TraceError("Attempt to enable console #####")
		"""
		constInfo.CONSOLE_ENABLE = True
		self.consoleEnable = True
		app.EnableSpecialCameraMode()
		ui.EnablePaste(True)
		"""

I believe is better to disable these codes in release version. It's just an example to let you know what I'm talking. Let me know if you know something bad about.

Edited by WeedHex
Link to comment
Share on other sites

  • Forum Moderator

You shouldn't worry about the console because either someone will activate it, meaning that they will inject some python code or whatever, or they will not, but they will still be able to use the functions whatsoever, even if the console itself is deactivated. What I say is; in order for someone to be able to use the console, he must do some code injection, and if he is able to, even if you disable the console, he will be able to call the functions the console helps you to use.

You cannot do much harm with the console however, it's mostly for debug / admin purposes. The only thing is something about GM logo or GM detector, you can check on here, Koray shared something about it if I remember correctly.

  • Love 1

Gurgarath
coming soon

Link to comment
Share on other sites

  • Premium
7 hours ago, Gurgarath said:

You shouldn't worry about the console because either someone will activate it, meaning that they will inject some python code or whatever, or they will not, but they will still be able to use the functions whatsoever, even if the console itself is deactivated. What I say is; in order for someone to be able to use the console, he must do some code injection, and if he is able to, even if you disable the console, he will be able to call the functions the console helps you to use.

You cannot do much harm with the console however, it's mostly for debug / admin purposes. The only thing is something about GM logo or GM detector, you can check on here, Koray shared something about it if I remember correctly.

Yes, you are totally right!

For this reason I opened this thread to hear someone else opinion.

My final idea so is to remove all the console releated codes (maybe put it on _DEBUG define), removing also all the modules on binary.

  • Metin2 Dev 1
  • Good 1
Link to comment
Share on other sites

  • Forum Moderator
14 hours ago, WeedHex said:

Yes, you are totally right!

For this reason I opened this thread to hear someone else opinion.

My final idea so is to remove all the console releated codes (maybe put it on _DEBUG define), removing also all the modules on binary.

The console is 99% of the time not going to cause any harm (basically it allows to show collisions or go into minimal ui mode) or really minor harm (like about GM or module reload, stuff like this). I reckon however that this is a good idea to avoid giving access to this piece of the code in Distribute as there is no reasons to use it, basically at all and a very few admins actually use it.

  • Love 1

Gurgarath
coming soon

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

Announcements



  • Similar Content

  • Activity

    1. 5

      Effect weapons

    2. 3

      Crystal Metinstone

    3. 3

      Feeding game source to LLM

    4. 113

      Ulthar SF V2 (TMP4 Base)

    5. 3

      Feeding game source to LLM

    6. 0

      Target Information System

    7. 3

      Feeding game source to LLM

    8. 2

      anti exp explanation pls

  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.