Leaderboard

A little progress today, have the battle system engaging properly, this particular mode chooses who gets first strike randomly. Other modes will use stats or other values to determine first strike. Setting up the "battle panel" which will appear and disappearon the left as needed, as well as switch between the attack turn controls and the defense turn controls. Also idle battle animation code is done and loops properly without losing GUI response. I think I'm also going to move the text display over to the right so that it fits nicely under the GDI canvas, and moving the stuff on the right over to the opposite side. Also thinking I may do away with the user and friend list boxes and instead use a treeview.

I don't chat much on IRC, anymore just idle. I'll chat with a few people, most of the time that I am active I'm chatting in the espernet minecraft channel with a few of the other regulars there. Out of all the networks I idle or visit, the espernet minecraft channel is one of the most active I've seen lately. Aah, you get that with the younger generations, even my own! You know, I've call it Autoit and refer to it like that in speech, but several tech/programming people I've conversated with in person say it like Auto-IT and I guess when I'm typing the muscle memory to the shift key is just there lol

Thanks... that is indeed the log I want to look. Will likely be able to do some checking on Wednesday at the earliest and follow the steps you have done to see if I can replicate it.

TheDcoder and I along with Xandy, and occasionally a few others, used to chat regularly on the AutoIt channel on freenode, then at his recommendation we moved from freenode to OTFC. But I eventually decided I was wasting too much time on such chats, had too many other better things to do, and it had just devolved to TheDcoder and I, and we mostly argued about all sorts of things, which grew tiresome in the end ... and now he argues with me all the time here ... there is no escape. He is young and contrary ... you have been warned. By the way, it is AutoIt not AutoIT ... as in automate it, not an IT department ... especially not one for Autos. P.S. Actually the channel we use/used was #AutoIt4Life. P.S.S. I was born in 1959, so yes I am old, and my head has nearly fallen off, due to all the negatory shaking that TheDcoder causes me to do ... not to mention the eye-rolling.

Managed to figure out how to get the SSL working thru the *.000webhostapp.com so now there is at least one link that is SSL. Looking at Linode for hosting, also looking at Uberspace.de. Also here's a couple sprites that I've converted to GIF. The animation I may not use in the actual program, just something I drew while practicing this art style I've managed to develop. Being able to use GDI+ in the script is very helpful.

Champak, mistersquirrle kindly pointed at my UDF - here it is in action: #include <Array.au3> #include "ArrayMultiColSort.au3" ; Set required sort list $sList = "3-6M,3-9M,12M,12-18M,2,2T,3,3T,12,3 US,4 US,12 US" ; Get an array $aList = StringSplit($sList, ",", 2) ; Shuffle it _ArrayShuffle($aList) ; Make 2D (min required) _ArrayColInsert ($aList, 1) ; And here is the result _ArrayDisplay($aList, "Shuffled", Default, 8) ; Set list in correct format for the UDF Global $aSortData[][] = [[0, $sList]] ; Sort the array using the required sort date _ArrayMultiColSort($aList, $aSortData) ; And here it is _ArrayDisplay($aList, "Sorted", Default, 8) Good enough? M23

Value Meaning MB_APPLMODAL 0x00000000L The user must respond to the message box before continuing work in the window identified by the hWnd parameter. However, the user can move to the windows of other threads and work in those windows. Depending on the hierarchy of windows in the application, the user may be able to move to other windows within the thread. All child windows of the parent of the message box are automatically disabled, but pop-up windows are not. MB_APPLMODAL is the default if neither MB_SYSTEMMODAL nor MB_TASKMODAL is specified. MB_SYSTEMMODAL 0x00001000L Same as MB_APPLMODAL except that the message box has the WS_EX_TOPMOST style. Use system-modal message boxes to notify the user of serious, potentially damaging errors that require immediate attention (for example, running out of memory). This flag has no effect on the user's ability to interact with windows other than those associated with hWnd. MB_TASKMODAL 0x00002000L Same as MB_APPLMODAL except that all the top-level windows belonging to the current thread are disabled if the hWnd parameter is NULL. Use this flag when the calling application or library does not have a window handle available but still needs to prevent input to other windows in the calling thread without suspending other threads.