Unknown2007-08-05 20:30:29
Hi all! So... I'm completely new to all this, just got talked into getting off of Nexus so I got zMud and set off to see what I could turn it into.
I have a bit of programming under my belt with stints in VB, Java, C/C++, and LUA but nothing really big. ^.^
Anyway, I've gotten so that my prompt triggers nicely, I've gotten a score trigger (but the gag doesn't work right!) and I've set up a couple nice wield/unwield macros and set up gauges for my HP/Mana/Ego/Power/Endurance/Willpower/EXP.
All that is nice... except that I cannot position them for the life of me! They all just kinda go, "I wanna be HERE! And I'm not moving! GRRR!"
Yeah... anyway! ^^;;;
I hope the image uploaded well... but you can see how the gauges are positioned: I want to get them so that it's:
HP Ego Endurance EXP
Mana Power Willpower
I mean, I saw a bunch of screenshots of really fancy stuff with lots of pictures and info reading out afflictions and bady part status, etc. Being able to do that would be awesome! But... I can't even make these gauges behave! ;_; Any help? Tips? Godly answers?
I tried MUSHclient, but it was confusing. Heh. Seems easier to make GUI stuff in zMud.
I have a bit of programming under my belt with stints in VB, Java, C/C++, and LUA but nothing really big. ^.^
Anyway, I've gotten so that my prompt triggers nicely, I've gotten a score trigger (but the gag doesn't work right!) and I've set up a couple nice wield/unwield macros and set up gauges for my HP/Mana/Ego/Power/Endurance/Willpower/EXP.
All that is nice... except that I cannot position them for the life of me! They all just kinda go, "I wanna be HERE! And I'm not moving! GRRR!"
Yeah... anyway! ^^;;;
I hope the image uploaded well... but you can see how the gauges are positioned: I want to get them so that it's:
HP Ego Endurance EXP
Mana Power Willpower
I mean, I saw a bunch of screenshots of really fancy stuff with lots of pictures and info reading out afflictions and bady part status, etc. Being able to do that would be awesome! But... I can't even make these gauges behave! ;_; Any help? Tips? Godly answers?
I tried MUSHclient, but it was confusing. Heh. Seems easier to make GUI stuff in zMud.
Unknown2007-08-05 21:01:28
They display in the order they're created. Create the first one on the first row first, obviously. Then, create the first one on the second row and use the 'stack' option. Alternate top row and bottom row and you should get what you want.
To give you a headstart, here's an example using Health, Mana, Ego, and Power with Health and Mana on the top and Ego and Power on the bottom:
To give you a headstart, here's an example using Health, Mana, Ego, and Power with Health and Mana on the top and Ego and Power on the bottom:
CODE
#BUTTON 0 {H: @health / @max_health} {} {} {} {@health} {} {HEART} {Size} {200} {18} {} {} {} {42} {} {Gauge||12|@max_health|@max_health / 4|0} {} "" {Explore} {} {btnhealth} {2}
#BUTTON 0 {E: @ego / @max_ego} {} {} {} {@ego} {} {PINDOWN} {Size} {200} {18} {} {} {} {93} {} {Gauge||12|@max_ego|@max_ego / 4|0} {} "" {Explore|Stack} {} {btnego} {2}
#BUTTON 0 {M: @mana / @max_mana} {} {} {} {@mana} {} {DIAMOND} {Size} {200} {18} {} {} {} {59} {} {Gauge||12|@max_mana|@max_mana / 4|0} {} "" {Explore} {} {btnmana} {2}
#BUTTON 0 {P: @power / 10} {} {} {} {@power} {} {BOLT} {Size} {200} {18} {} {} {} {110} {} {Gauge||12|10|1|0} {} "" {Explore|Stack} {} {btnpower} {2}
#BUTTON 0 {E: @ego / @max_ego} {} {} {} {@ego} {} {PINDOWN} {Size} {200} {18} {} {} {} {93} {} {Gauge||12|@max_ego|@max_ego / 4|0} {} "" {Explore|Stack} {} {btnego} {2}
#BUTTON 0 {M: @mana / @max_mana} {} {} {} {@mana} {} {DIAMOND} {Size} {200} {18} {} {} {} {59} {} {Gauge||12|@max_mana|@max_mana / 4|0} {} "" {Explore} {} {btnmana} {2}
#BUTTON 0 {P: @power / 10} {} {} {} {@power} {} {BOLT} {Size} {200} {18} {} {} {} {110} {} {Gauge||12|10|1|0} {} "" {Explore|Stack} {} {btnpower} {2}
Acrune2007-08-05 21:09:23
A different way, go to the "position/size" tab in the settings editor, and uncheck the "autoposition" check box, and put the gauges wherever you want by adjusting the position numbers.
#BUTTON 1 {Health} {} {} {} {} {} {} {} {} {} {Pos} {0} {2} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
#BUTTON 2 {Experience} {} {} {} {} {} {} {} {} {} {Pos} {0} {368} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
#BUTTON 3 {Willpower} {} {} {} {} {} {} {} {} {} {Pos} {17} {246} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
#BUTTON 4 {Endurance} {} {} {} {} {} {} {} {} {} {Pos} {0} {246} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
#BUTTON 5 {Power} {} {} {} {} {} {} {} {} {} {Pos} {17} {124} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
#BUTTON 6 {Ego} {} {} {} {} {} {} {} {} {} {Pos} {0} {124} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
#BUTTON 7 {Mana} {} {} {} {} {} {} {} {} {} {Pos} {17} {2} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
That'll put all the buttons in the right place, if that helps any.
#BUTTON 1 {Health} {} {} {} {} {} {} {} {} {} {Pos} {0} {2} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
#BUTTON 2 {Experience} {} {} {} {} {} {} {} {} {} {Pos} {0} {368} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
#BUTTON 3 {Willpower} {} {} {} {} {} {} {} {} {} {Pos} {17} {246} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
#BUTTON 4 {Endurance} {} {} {} {} {} {} {} {} {} {Pos} {0} {246} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
#BUTTON 5 {Power} {} {} {} {} {} {} {} {} {} {Pos} {17} {124} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
#BUTTON 6 {Ego} {} {} {} {} {} {} {} {} {} {Pos} {0} {124} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
#BUTTON 7 {Mana} {} {} {} {} {} {} {} {} {} {Pos} {17} {2} {} {} {Gauge||12|||7} {} "" {Explore|Inset} {} {} {4}
That'll put all the buttons in the right place, if that helps any.
Unknown2007-08-05 21:18:00
1. Fixed positions are less flexible and portable. I tried that and wasn't happy with the results when moving to different machines with different resolutions. It's also just painful to align a couple dozen buttons by hand.
2. When writing text scripts to create buttons, always use 0 as the button's number (unless maybe you just want to overwrite the existing versions of the buttons and you know their numbers already). Using 0 tells zMUD to increment starting with your current highest button number. Just another way to make buttons more portable.
3. It doesn't look like you included variables in your buttons for updating the gauges... ?
2. When writing text scripts to create buttons, always use 0 as the button's number (unless maybe you just want to overwrite the existing versions of the buttons and you know their numbers already). Using 0 tells zMUD to increment starting with your current highest button number. Just another way to make buttons more portable.
3. It doesn't look like you included variables in your buttons for updating the gauges... ?
Unknown2007-08-05 21:18:13
OK, I understand, now. This means it's going to be a super huge pain in my lower backside region to set up one of those spiffy setups that I saw some people with.
*sighs*
Well, at least I can get gauges!
Also: do you all know a good way of gagging the triggered SCORE reading (triggered when a kill is detected, for capturing XP changes.) Currently I'm using... #GAG 19 and that doesn't always gag all of it and sometimes seems to gag too much... and... GAH it's inconsistant and evil!
I wanted to use:
#GAGB
score
to capture the score, but that didn't gag anything. :/
In the end, I is confuzzled.
*sighs*
Well, at least I can get gauges!
Also: do you all know a good way of gagging the triggered SCORE reading (triggered when a kill is detected, for capturing XP changes.) Currently I'm using... #GAG 19 and that doesn't always gag all of it and sometimes seems to gag too much... and... GAH it's inconsistant and evil!
I wanted to use:
#GAGB
score
to capture the score, but that didn't gag anything. :/
In the end, I is confuzzled.
Unknown2007-08-05 21:19:23
I have a solution. Use ATCP to get your experience updates in the background and stop using auto-score!
Acrune2007-08-05 21:28:45
QUOTE(Zarquan @ Aug 5 2007, 05:18 PM) 431610
1. Fixed positions are less flexible and portable. I tried that and wasn't happy with the results when moving to different machines with different resolutions. It's also just painful to align a couple dozen buttons by hand.
2. When writing text scripts to create buttons, always use 0 as the button's number (unless maybe you just want to overwrite the existing versions of the buttons and you know their numbers already). Using 0 tells zMUD to increment starting with your current highest button number. Just another way to make buttons more portable.
3. It doesn't look like you included variables in your buttons for updating the gauges... ?
2. When writing text scripts to create buttons, always use 0 as the button's number (unless maybe you just want to overwrite the existing versions of the buttons and you know their numbers already). Using 0 tells zMUD to increment starting with your current highest button number. Just another way to make buttons more portable.
3. It doesn't look like you included variables in your buttons for updating the gauges... ?
1) True. But I play with the window maximized on one computer. So it doesn't matter to me And I've found manual buttons to be easier, and you can make it look nicer.
2) Dunno. Portability doesn't matter to me, I just do it fast as I can, and thats what doing ctrl+b gave me in the settings editor.
3) Right, just did the formatting in the right place, he obviously has update code already. I don't use gauges, so I would have had to write up the code and remember how to use them
Unknown2007-08-05 22:06:12
Zarquan... can you tell me what ATCP is? ^.^;;; I is clueless! xD
And how do you use it? xD Then again, I'd still need to capture auto-score on level gains to get my new max numbers and my new rank.
And how do you use it? xD Then again, I'd still need to capture auto-score on level gains to get my new max numbers and my new rank.
Unknown2007-08-06 01:56:27
Achaea Telnet Client Protocol (though all IRE games use it, so the name is a bit of a misnomer now, really). Nexus uses it to keep the GUI updated and you can use it, too, if you have the right software. I use LMTS, which is a modified form of IMTS (Imperian to Lusternia conversion). There are threads on it under the Project L forum, and you can do a search for more info. I use a custom Lua script with LMTS to put the percent-to-next-level right in my prompt. It's very convenient.
Unknown2007-08-06 09:58:58
I like the prospect of using LUA scripts (though for what I need just simple C is enough, probably) but is there a way to tie that into zMUD without using LMTS? I downloaded it and tried it out, but it behaved strangely on my client (two prompts, one was the original game prompt, the other was the new prompt. The old prompt had no XP, the new one had no balances) and since I figured out why my score gag wasn't working right, it's not really necessary anymore.
Though, honestly, if I go back and find out how to fix that prompt problem, I will keep it around as a tool that might be usable in the future. For now I need to figure out how the hell to set up my GUI to be... decent. So far I am extremely disappointed with zMUDs GUI uitility. It's easy to use, sure, but they could have done better than this, I think.
Aaanyway. *ponders prompt problem*
Though, honestly, if I go back and find out how to fix that prompt problem, I will keep it around as a tool that might be usable in the future. For now I need to figure out how the hell to set up my GUI to be... decent. So far I am extremely disappointed with zMUDs GUI uitility. It's easy to use, sure, but they could have done better than this, I think.
Aaanyway. *ponders prompt problem*
Unknown2007-08-06 10:54:16
Try CONFIG PROMPT REMOVE LINEBREAK. The LMTS prompt replaces the Lusternia prompt, but only if it has GA/EOR instead of CR/LF.
There is no way to use Lua in zMUD without LMTS, but you don't have to use the mapper module or the vote module. You can use just the basic MudBot with Lua.
I've customized the C code a little bit beyond what's downloadable from the project site, but it's not 100% correct and I don't know if it would really be good to upload what I have. At any rate, if you do use the mapper, avoid the 'map load' command at all costs. It's very broken and near impossible to figure out and fix. I need a proper debugger for this stuff...
There is no way to use Lua in zMUD without LMTS, but you don't have to use the mapper module or the vote module. You can use just the basic MudBot with Lua.
I've customized the C code a little bit beyond what's downloadable from the project site, but it's not 100% correct and I don't know if it would really be good to upload what I have. At any rate, if you do use the mapper, avoid the 'map load' command at all costs. It's very broken and near impossible to figure out and fix. I need a proper debugger for this stuff...
Unknown2007-08-06 19:12:25
Hiya 'gain Zar!
I tried removing the linebreak and that solved the problem! But... I miss the linebreak quite badly. =/ The odd thing is that I didn't have to remove the linebreak when I loaded up my character in a copy of Lusternia (erm.... by a copy of it, I mean in the characters window thingie in zMud...) that didn't have the tweakes I've made. But those tweaked are all done AFTER it hits zMUD, so I don't see why that should affect anything.
I thought I'd read somewhere that the LMTS adds it's own linebreak? If so that means it was adding properly on the clean install but was not adding on my setup. =/
No love. ;_;
And another question: all those interfaces that have body-shots and pictures... all those pictures are buttons, right?
Well, lets say you have the Vintruvian man picture: that is one button. How do you get multiple text-boxes at different strangely-aligned areas of that one button? O.o
I is confused. From what little I've experienced with zMUD, that seems nigh impossible. So there must be something else going on!
Thanks again everyone!
EDIT: OK so I see you can make buttons overlap, that must be what they did, with a stacked button... using custom positions..... Got it! I think. xD Thanks!
I tried removing the linebreak and that solved the problem! But... I miss the linebreak quite badly. =/ The odd thing is that I didn't have to remove the linebreak when I loaded up my character in a copy of Lusternia (erm.... by a copy of it, I mean in the characters window thingie in zMud...) that didn't have the tweakes I've made. But those tweaked are all done AFTER it hits zMUD, so I don't see why that should affect anything.
I thought I'd read somewhere that the LMTS adds it's own linebreak? If so that means it was adding properly on the clean install but was not adding on my setup. =/
No love. ;_;
And another question: all those interfaces that have body-shots and pictures... all those pictures are buttons, right?
Well, lets say you have the Vintruvian man picture: that is one button. How do you get multiple text-boxes at different strangely-aligned areas of that one button? O.o
I is confused. From what little I've experienced with zMUD, that seems nigh impossible. So there must be something else going on!
Thanks again everyone!
EDIT: OK so I see you can make buttons overlap, that must be what they did, with a stacked button... using custom positions..... Got it! I think. xD Thanks!
Unknown2007-08-06 19:37:14
LMTS replaces the GA/EOR with a CR/LF, so your client can still trigger prompts with CR/LF. If you play from somewhere that you don't have LMTS, for whatever reason, you just need to add the linebreak for that session and remove it later. I even put a trigger in Palisade that auto-adds the linebreak for people, just to avoid the dozens of people that would inevitably not read the documentation and complain that the system did nothing.
Yes, they're all buttons. Yes, the little buttons you see on the pictures are using absolute alignment. Personally, I don't find them all that useful, and they're more trouble than they're worth. Here's an older screenshot of my GUI. It's all built from a text script and is very easily re-loaded. The only thing a user has to do is put it on the right or left side to make it all line up nicely.
Yes, they're all buttons. Yes, the little buttons you see on the pictures are using absolute alignment. Personally, I don't find them all that useful, and they're more trouble than they're worth. Here's an older screenshot of my GUI. It's all built from a text script and is very easily re-loaded. The only thing a user has to do is put it on the right or left side to make it all line up nicely.
Forren2007-08-06 19:38:05
You can manually set the positions of individual buttons so they overlap with the picture button. I temporarily had a body picture in my own system before realizing how laggy it could make things.
Unknown2007-08-06 19:45:02
Buttons are typically only laggy when you assign variables to control them. If you instead use the %btnimage and %btncol functions to change the look of buttons, you speed them up greatly.
Forren2007-08-06 20:55:16
QUOTE(Zarquan @ Aug 6 2007, 03:45 PM) 431964
Buttons are typically only laggy when you assign variables to control them. If you instead use the %btnimage and %btncol functions to change the look of buttons, you speed them up greatly.
I had no variables controlling it - it wasn't the most smooth thing while mousing over, so I disabled it.
Happen to know how to easily adapt %btnimage and %btncol in Cmud?
Unknown2007-08-06 21:20:57
I haven't gotten around to doing my GUI stuff in CMUD yet. I know there are still some bugs with buttons, gauges, and the status window. Plus, I'm really hoping for zApp stuff in a soon-to-come version. I would presume they work the same way in CMUD that they do in zMUD, no?
Forren2007-08-07 12:44:13
QUOTE(Zarquan @ Aug 6 2007, 05:20 PM) 432008
I haven't gotten around to doing my GUI stuff in CMUD yet. I know there are still some bugs with buttons, gauges, and the status window. Plus, I'm really hoping for zApp stuff in a soon-to-come version. I would presume they work the same way in CMUD that they do in zMUD, no?
The options for Cmud buttons are a little different.
Unknown2007-08-07 15:06:29
Okay. I created a couple of buttons in my CMUD profile now, and doing #CALL %btncol(btndate, white, black) changed the color for me without a problem.
Forren2007-08-07 15:27:03
QUOTE(Zarquan @ Aug 7 2007, 11:06 AM) 432179
Okay. I created a couple of buttons in my CMUD profile now, and doing #CALL %btncol(btndate, white, black) changed the color for me without a problem.
Will have to try it out, right now I have three buttons that use gauges to do what a toggle should do along with four toggles that use a variable so it starts off pushed in. Can I use a similar function for toggles?