I was wondering if any of these were possibilities for the future of 4.0
1. "Rollover" Images for things like buttons.
2. "Clicked" Images for things like buttons.
3. Better border editors, such as changing colors (Another thing I would really like for buttons >.>')
4. Background image for outputs/inputs (if you can't already do this?)
I think thats it for now. o.o
Edit: To be quite honest I kinda wish we could make it so that players cannot use macros that they have created, and Only ones that the game presents.
ID:134056
 Aug 3 2007, 1:57 pm
|
|
Lifehunter wrote:
Edit: To be quite honest I kinda wish we could make it so that players cannot use macros that they have created, and Only ones that the game presents. And prevent people from customising their keyboard controls? Bad. =( | |
Being able to change what key a process is already in the game is used for (like you can with most games) and being able to add a bunch of stupid [profanity] that isn't needed are 2 different things.
| |
That wouldn't necessarily stop people from being able to use abusive macros though. There are dozens of external macro programs that will do the job as well. Even if there isn't a command line in your game, someone could probably trick BYOND into adding one.
So either way, your game still needs to be macro-abuse-resistant on its own. | |
Crispy wrote:
So either way, your game still needs to be macro-abuse-resistant on its own. Agreed, which most halfway-decent programmers are quite capable of doing. So... either we help these programmers out and do it for them, or we leave it an option, thus to not ruin those games that encourage client-side macros... Mess up half the community, or make people do their own work... Its a true conundrum... | |
I want it to be an option. I never said to totally remove the macro system, Just give us an option to turn it off.
I'm also quite pissed about ANYBODY being able to edit the skins. Its just not right man. | |
They can only edit the skins and use their own custom skin on games that dont have a custom skin on its own... if you dont want them using their own skins, upload a skin to be included with the game.
Personally, I think it enables greater functionality and gives games more individuality. What bad do you see about it? | |
Mainly, I've spent a lot of time working on my custom skin. The possibility of players being able to ruin it pisses me off.
| |
As long as your game has a custom skin, they cant. it only loads the default skin on games hosted in 3.5 or without a default skin.
| |
Jamesburrow wrote:
As long as your game has a custom skin, they cant. it only loads the default skin on games hosted in 3.5 or without a default skin. This is not true. Although their custom default skin will not load, they can still make one for that specific game. | |
DarkCampainger wrote:
Jamesburrow wrote: I'll be blunt and say this outright. This needs to change. Not only is it a headache having to walk help people fix it so they are able to play the game (after they decide to mess around with it when they have no clue what they are doing and then complain "Why don't I have a map anymore?" Not only that, but its impossible to actually update the skin as far as I can tell without having to have the user go through and manually delete it. The extended functionality for the developers is rather pointless if the player is able to take the same functionality and do with it whatever they please. | |
Nick231 wrote:
DarkCampainger wrote: That's their problem. They decided to mess with it. Tell them to delete it and reconnect. Not only that, but its impossible to actually update the skin as far as I can tell without having to have the user go through and manually delete it. When you update the skin, the user should receive this prompt: "There has been an update to the skin for this world. Would you like to replace your custom skin with the new version?" The extended functionality for the developers is rather pointless if the player is able to take the same functionality and do with it whatever they please. If the skin looks good and functions well, I see no reason why someone would edit it. | |
DarkCampainger wrote:
Nick231 wrote: It becomes the developers problem, since they come to the developer for help with it. Not only that, but its impossible to actually update the skin as far as I can tell without having to have the user go through and manually delete it. That would help, but it still wouldn't stop games from being all but unplayable if the user is to say no to something when there has been a major change (which goes back to the first point). The extended functionality for the developers is rather pointless if the player is able to take the same functionality and do with it whatever they please. People would edit it simply because they're idiots. For example I've already had one person editing the skin so that they could could add have black background buttons of the in-game HUD about 2 pixels below where the in-game HUD is. That said, its also up to the developer. If we're going to allow this, why not just distribute icons in raw .dmi format and allow players to switch them around? Why not compile the code at runtime and allow the player to change up anything they want? If the developer wants to allow people to edit the interface, fine. For those of us who don't want them to be able to, there really needs to be an option that forces the packaged interface to load. | |
So your pretty much wanting to be able to lock the .dmf file down at runtime? Or perhaps encrypt it?
Sounds like a good plan! | |
Flame Sage wrote:
So your pretty much wanting to be able to lock the .dmf file down at runtime? Or perhaps encrypt it? Pretty much yea. I imagine it could already be more or less done just by checking values of certain things, but thats a pain to do initially, and maintain as time goes by and changes are made. As far as encrypting it, just keeping it in the .rsc would be plenty I imagine. | |
-- Data