It's an alpha build. Lots of things in the program are unfinished, including the icon. I'll get to it eventually.

 

-----signature-----

Thanks for the suggestion!

Like I told Buffsteria above, I'd like to avoid injecting text into the game's chat line.

If I understand you correctly, you're suggesting that we use the game chat line as a telephone through which the customer sends information to the crafter. But we don't need to involve the game in the transmission of information between the two people. The info can get sent from one person's Mojo to the other person's Mojo.

Off the top of my head, I can think of a few ways to do this. I'll think about it some more.

 

-----signature-----

Well, go ahead and choose. I started writing the manual-entry stuff and it turns out to be more interesting than I expected because it's hard to find a really ergonomical design.




I wrote a paperdoll builder with drop-and-drag pictures of items a few years ago for a template-building program that I never finished. Maybe I'll put it in Mojo.




I definitely agree, the user would have to check a box to opt in.




I think one of the two types of delves includes realm but I'm not sure. I agree, every scrap of info should be preserved.

 

-----signature-----

I thought it over. Here's my suggestion.

1. Customer enters a list of gems into Mojo using a new window that makes this easy.

2. Mojo shows the the customer a code that looks something like this:

UX3N2

3. Customer tells the crafter the code.

4. Crafter types code into Mojo.

5. Crafter's copy of Mojo automatically populates the crafter's hotbars with the gems.

--------------------------

That's what the two people see. Behind the curtain, it's implemented using Mojo's server as the communications medium. After the customer enters the list, his or her copy of Mojo sends the list to Mojo's server. Later the crafter's copy of Mojo retrieves it from the server.

What do you think?

 

-----signature-----

lol, hello Mr. Pot, meet Mr. Kettle!

You're really showing a terrible lack of character here Exp_Tristan, dissing another programmer who spends his free time making free apps for an old almost defunct game.

Totally uncool!

Robbie is a very talented programmer, and I wouldn't be trying to match wang-size when comparing Mojo to your own contributions.

As much as your program was very useful and appreciated when you created it, the basis of Mojo is fundamentally different and far more professionally implemented. That he's now extending an already popular app with new (IMO obvious) features that make it a "one stop shopping" experience for DAoC players, is both natural and very much welcomed. (Just look at Charplan! Where they the first to do what it does? Nope. They just did it right and added lots of other existing utilities and sources of information into one app! Look at the credits to see all the people involved in evolving Charplan!) You seem to think this is about you, but it's about the user! The only reason anyone used your program was because it made life easier for them, and now another tool --that also makes life easier for them-- is adding your minor utility to it's repertoire. Live with it, or make a competing app if you think you can do it better!

Does anyone here doubt that it's more difficult to make a networked version of "DAoC_chatfixer" (nice name btw! lol), then it is to make the plain old version? lol!

Ridiculous.

Jumping on another programmer for building on what is hardly a genius idea, is a terrible display of professionalism. If everyone got as pissy about this as you, we wouldn't have Open Source software at all, or any free software for that matter. You may think you've developed something new and exciting when you create a piece of software that people enjoy using, but you're only fooling yourself if you think you weren't "standing on the shoulders of giants" while doing it. Every form of engineering relies on this concept of evolution, rather then creation.

In short, lay off Robbie he's good people!


P.S. Any programmer worth a lick can make a char-file copier utility in one evening of free time. It's not rocket science to do a little file handling. Mojo is leaps and bounds more involved, and if you had a clue you'd recognize that and not try to diss someone for spending many hours of free time making FREE software!

I used ChatLogFixer a handful of times over the past few years, and I thank you for taking the time to do something that I easily could have done myself in an evening of spare time programming; but I didn't! That much credit is due and I thanked you in the past for creating this useful little utility. However, it doesn't buy you the right to diss other programmers creating free software for this community. Your idea was nothing if not for the existence of DAoC, obviously, and everyone was already doing the same thing manually anyway! You simply automated a manual process. Good work! Thanks! Now lay off thinking you're some kinda programming genius for having done a rather minor utility, and that someone else is infringing on your "genius ideas" by extending a rather old minor utility with a pretty significant upgrade. (Networking)

Thanks robbie for this Mojo update and your continued sacrifices of your free time to create free tools for this community!

 

-----signature-----

Thanks, I really appreciate your comments.




I wasn't going to get into this subject because I don't want to sound like I'm bragging. But maybe I should say something. You're obviously a professional programmer so you understand the difference between commercial-quality software and something we put together quickly for our own use. But most people here probably don't know how big the difference is.

I know you know what I'm about to say. I'm writing this in large part for the people looking over your shoulder.

Let's look at this one small piece of Mojo. This one little "file copying" feature. Like you say, somebody can write a program to copy files in a few hours. But is that what Mojo does? In a way yes -- but in a way no. It's more complicated.

First of all, when you use Mojo's interface to import settings, you don't see any files. You aren't told about files. You don't have to know about paths or directories or files. The program deals with all of that for you. It simply asks you, "Which toon's settings do you want to copy?" Why is this important? Because, for example, it happens to be the case that DAOC uses different paths for Pendragon and regular servers, but you don't need to know that -- Mojo deals with it automatically.

In other words, under the hood, this feature copies files. But on the screen, in the interface, it doesn't copy files. It imports settings. This makes the program easier to use.

Second. When Mojo copies a file, it doesn't just copy it. First it backs up the original destination file. Then it does a CRC (a kind of mathematical check -- of course you know this, I'm explaining for others) on the source file. Then it loads the file into a data structure in memory for transmission and does a hash checksum (a similar kind of check). Then it sends the data over TCP/IP (which has error correction built in) to the other computer. Then it does another hash checksum on the received data to make sure nothing got damaged. Then it writes the file to the destination directory under a temporary unique name. Then it does a CRC on the newly written file and compares it to the original CRC to make sure the newly written file is exactly the same as the original. At this point, Mojo is 99.9999999% sure that the new file, which is already written in its final place on the hard disk, is exactly correct, and only now does Mojo change the names of the two versions of the destination file so the new one replaces the old one. If at any point in this process, anything goes wrong, the process aborts and the original destination file is left untouched. I would have liked to use Windows transacted file stuff but I couldn't because Mojo's minimum OS requirement is XP SP2. I can't wait for XP to die.

These kinds of safeguards are normal (or supposed be normal) in commercial-quality software. These measures ensure (as much as possible) that the user's data won't get corrupted.

Third. Every little thing that Mojo does, it checks to see if it took place correctly. If anything goes wrong, Mojo notices and prints a red error message on the Geeky Stuff tab. Programmers have various names for this -- tracing, error logging. Usually the output goes into files that the user never sees, but I've found in open alpha tests like this, it's helpful to have the message easily visible where the user can report them to me.

In case anybody is wondering why I'm bothering to put so much work into a freebie program for a half-dead game, it's because I'm thinking that maybe eventually, down the road, I'll turn Mojo into a commercial program (one that I sell) for World of Warcraft. Anything I put into the program for DAOC now may end up getting used later for WoW. I find it much easier to write code from scratch than change it later, so anything I want to use later, I try to put into polished form at the beginning.

 

-----signature-----

Maybe the best example is Dark Age of Camelot.

Exp_Tristan wants us to live in a world where nobody is allowed to write a program that does something an earlier program did.

If we lived in that world, Mythic could not have published DAOC, because DAOC wasn't the first 3D MMO RPG.

If we lived in his world, there would be only one MMO in existence today -- Meridian 59 from 1996 -- and that's what we'd all be playing.

Harsh, I know, but those are Exp_Tristan's rules!

 

-----signature-----

2 small questions before i give this program a try. i have 2 pc's and i duallog on both Q1: as long as i don't use any of the "allow the user to log more than 2 accounts" feature is the program ok with ToS and EULA? Q2: can i be sure that the "encrypted passwords" will not be keylogged when i input them and sent to someone else?

it looks like something handy for me to use because i got two 4-man groups i use for farming afrits and aurulite and pl'ing my own characters(in pve).

 

-----signature-----

I don't believe "run more than two" violates Mythic's rules, and so far as I know, Mythic has never said it does. However there is one option in Mojo that may be a violation of the rules: large-address awareness. This option is off by default. In order to use it, you have to check a box, and whenever you check the box, Mojo displays a warning about the possible rule violation, so you don't have to worry about breaking the rules by accident. You can read more about this on Mojo's website. See the red text at the bottom of the page:

http://mojoware.org/p/instructions.set_daoc_options.html

Nothing else in Mojo violates the rules, so far as I know.




I assume you mean keylogged by Mojo.

Unless you are a highly skilled programmer and more precisely a "reverser", somebody who reverse-engineers executable code, no, there is no way you can be sure. You just have to trust the publisher, namely, me.

I think you just have to ask yourself: does this Rob guy strike me as somebody who would spend his time writing this program in order to steal my DAOC accounts?

By the way, the reason why Mojo could steal your passwords has nothing to do with the fact that it asks you to enter your passwords. Mojo could log your keystrokes and steal your passwords even if it didn't ask you to type your passwords.

The real reason Mojo could log your keystrokes and steal your passwords is that it runs as administrator.

Any program that runs as administrator can log your keystrokes and send them to a server. Or do anything else it wants to your computer.

Why does Mojo run as administrator? It needs to do this to launch DAOC; to look for system handles when it deletes mutexes; to set which window is in the foreground (an upcoming feature); and lots of other ordinary, non-threatening things.

I don't know if this will make you feel better or worse, but that's the situation.

 

-----signature-----

From a crafter PoV. I like 2-5 quite a bit and if kort/loki/gearbunny output could be substituted as input for 1 !manual_work I would be a happy camper from a customer pov.

Now for the feature creep...

I can imagine people who want to work with a crafter who don't want to use mojo locally so what about a web app version that could either import a file from your program (or other sc programs) or let folks do that nasty manual work online. If you are capturing whole templates you could use the non-crafted items to build up that item db discussed, and if if you have templates and a web server with them you could give the option to publish them for the community.

 

-----signature-----