UI Arrangement

I don't think you should ever give players the ability to insert a plug-in it could be abused. I think they're better off just making it a cash shop item for people that do not like the default UI. Though personally i like the default UI.

Often times games have their UI textures saved as simple image files in the game directory. It's trivial to modify these images to get a different look. Of course that won't allow you to move or resize any of the functional elements but every bit counts.

"

Zidjian escreveu:

I don't think you should ever give players the ability to insert a plug-in it could be abused. I think they're better off just making it a cash shop item for people that do not like the default UI. Though personally i like the default UI.

At most an API could be used to analyze combat data. If that stream is provided in such a manner.

I don't think you understand how plugins work, or that you cannot prevent such things due to a process called code injection. Giving an API is just a friendly and safe way to integrate external code, however code can ALWAYS be introduced into a process via injection.

Well zeto i never said i knew how it worked. So you're 100% positive it could never be misused?

Also Chris has stated that he won't support modding so a plug in in my definition is modding.

So for example lets say i want to replace the default image in the background of the inventory to a spell damage counter. Say Spell X beats Spell Y or Spell Y losses to Spell Z. This could be inserted into the image with a simple text editor and replace the current background. Then instead of having to know the spells counters you simply look at it on your UI.

Ah problem solved.

Content is more important for me as well. However i always like to have options... Crysis 2 is just a nightmare for me for example :)

"

Chris escreveu:

"

zeto escreveu:

I don't think you understand how plugins work, or that you cannot prevent such things due to a process called code injection. Giving an API is just a friendly and safe way to integrate external code, however code can ALWAYS be introduced into a process via injection.

Runtime modifications like this would probably be detected as third party tools. I'm sure you understand why we have to have a policy against those :)

yeah I totally do understand, which is why I'd like to first see as much flexibility built into the UI as possible, eventually letting people place things as they wish at the very least.

If the game gets popular enough, people will figure out ways to do code injection for 3rd party tools. Companies have attempted to stop such things for 15 years now or so and failed every time. I hope you guys just don't worry about it so much and focus on a fun game.

Bots and whatnot can ruin games, so it's always something to take into consideration, but I've also seen companies waste a lot of resources to no avail combating such things when changes to gameplay dynamics probably could have rendered such behavior moot.

In either case, giving the playerbase basic things they need is just incentive not to go poking around in the binaries... which can only be a good thing.

Nox had smart solutions, which I believe far outshine cluttering screen estate with more UI overlays.

If you took a lot damage that gets you very low on health quickly, you would scream instead of just grunt from the hit.

And there was the not so uncommon heart beat when low on health.

Also Diablo 2 showed enemy health as outline whenever you hit them, from green to red. It was very brief, I doubt everyone noticed it.