MS4

[Matt]

ERROR!

Admin text does not remove the =.

I type =Test!

I see (admin) =Test!

>_>

At least it's an easy fix. Lol.

[Clu]

Is this the latest version of Mirage with the most optimizations or is that in the 3.78 topic?

[Jacob]

This version has all the fixes that were needed to 3.78 and I added byte array packets.

One person has said it lags for them, so let's see if it lags for anyone else.

[Clu]

Im trying to used to the byte arrays, does anybody know any good sites, or any tips they can give me on what to read/do to get accustomed to them?

[Jacob]

The best way to learn how to use my system is to look at the other packets and try to emulate them.

Once I'm 1000% sure there are no more bugs, I will be writing a full "How-To" guide.

[deathknight]

I think I have found a bug in the logout packet (not sure). I posted about it here.

viewtopic.php?f=136&t=5923

[ExoShox]

After reading about the logout bug i found an even weirder bug. i dont remember this happening the last time I did this with 3.79 but i have compiled and source code version. i log into admin/Admin on the source version and test/Test on the compiled version and then sometimes when i was moving one character, both characters moved, in the EXACT same pattern (if i move one character 1 left the other moved one left, 2 up, 2up etc.) I'll think it may just be a glitch because i know i already was using two characters source and compiled like 2 days ago and this didnt happen, and also this wasnt happening every time i moved either.

Edit: This only occurs IF the window you do not currently have selected is NOT minimized. Otherwise this bug does not occur.

[Matt]

It's not a bug, it's because the handle movement code and what not was moved outside of the form. Really bad on DFA's part, imo.

[deathknight]

After reading about the logout bug i found an even weirder bug. i dont remember this happening the last time I did this with 3.79 but i have compiled and source code version. i log into admin/Admin on the source version and test/Test on the compiled version and then sometimes when i was moving one character, both characters moved, in the EXACT same pattern (if i move one character 1 left the other moved one left, 2 up, 2up etc.) I'll think it may just be a glitch because i know i already was using two characters source and compiled like 2 days ago and this didnt happen, and also this wasnt happening every time i moved either.

Edit: This only occurs IF the window you do not currently have selected is NOT minimized. Otherwise this bug does not occur.

Yeah, I noticed this too while I was testing out a blank server. There is a REALLY easy fix. Make it so you can only open 2 clients at once .

Also I didn't test the logout bug on one computer, so it may not work if you have 2 clients running on the same computer, not sure. I used my 2nd computer (based on the fact that having one character follow the other around was annoying) so I'll check that part out later.


Edit: A few more things about the bug I found. On login, it does something similar, it doesn't show the logged on character. Pretty much, the map is not updating for the other members when they leave or enter the server until they do something that updates the map (drop an item, pick up an item. Maybe cast a spell, unable to test that one because NPC's automatically update the map.) It doesn't seem like a big issue, but small things like this annoy me Also, it does still happen if you have 2 clients opened on the same computer.

Edit: Was messing around with the party system, so I found another place the map isn't updating. When you kill an NPC, you don't get the xp, it doesn't respawn, and the NPC's freeze. This only happens if you have more than one person on the map, and the NPC's only freeze for the attacker (doesn't need to be in a party or anything, just 2 players on the same map)

[Jacob]

I will take a look at these issues shortly.

[ExoShox]

It's not a bug, it's because the handle movement code and what not was moved outside of the form. Really bad on DFA's part, imo.

It's still a bug. Maybe not with the program but with DFA 's logic for moving it, right? XD

[Beres]

I wouldnt think so. He intended to put it like that.

[Matt]

It's not a bug, it's because the handle movement code and what not was moved outside of the form. Really bad on DFA's part, imo.

It's still a bug. Maybe not with the program but with DFA 's logic for moving it, right? XD

No, not a bug. Beres is right.

[Acruno]

How are things actually going with this? Is Jacob even alive anymore?

[Jacob]

I'm alive!

This is why I do the set = new.

Don't Dim .. As New

Dim obj As MyClass
Set obj = New MyClass
Why write 2 lines when you can just say Dim obj As New MyClass?

Never Dim anything As New if you're concerned about speed. VB6 will treat such a variable as an auto-instantiated variable. Every time you use it, VB will check if it should be instantiated. This will cost you some extra CPU cycles.

http://www.aivosto.com/vbtips/not-optimize.html

One of these days, I'm going to rewrite it all so there's a 'global' outgoing buffer to make sending packets even faster.