The Official GreaterMUD Forums

GreaterMUD Discussion => GreaterMUD => Topic started by: Vitoc on Jan 31, 2006, 08:44 PM

Title: Things that need fixing in the Engine
Post by: Vitoc on Jan 31, 2006, 08:44 PM
Ok, if you could all please list the items that need fixing in the engine in this thread.? My Mega convo window doesn't seem to like the way I'm doing my wordwrapping so I miss about 50% of every message.? I'm addressing all these issues just as fast as I can.? I appreciate any time you put into this.? Thanks!

List of (hopefully)working options:
            Look,
            Get,
            Drop,
            Attack,
            Move,
            Exit,
            Inventory,
            Experience,
            Who,
            Stat,
            Gossip,
            Give,
            Equip,
            List,
            Buy,
            Break,
            Party,
            Invite,
            Disband,
            Follow,
            Leave,
            Rest,
            Train,
            Read,
            Use,
            Spells,
            Top,
            Set,
            Open,
            Close,
            Bash,
            Disarm,
            Sys (for ops),
            Search,
            Stash,
            Sneak,
            Hide,
            BackStab,
            Sell,
            Remove
Title: Re: Things that need fixing in the Engine
Post by: proteus on Jan 31, 2006, 09:16 PM
There's something odd with the buy option. It's not a big thing, but if you go to the boring shop, and type "buy ves" to buy a boring vest, it says you need to clarify because it's confusing it with the boring gloves.

Plus the game currently doesn't seem to recognize capital letters in gossip.

And a way to "kick" yourself out by relogging would be cool too.
Title: Re: Things that need fixing in the Engine
Post by: proteus on Jan 31, 2006, 09:33 PM
From my perspective:

"giant rat hits Proteus, but the swing glances off!"
Title: Re: Things that need fixing in the Engine
Post by: proteus on Jan 31, 2006, 09:55 PM
Another weird one... I tried picking up silver and copper, you have to type the full name, like if there's 1 silver, you have to type "get 1 silver". But if you just type "get" and the number, in that case, "get 1", it seems to lock you out of doing ANYTHING else. None of my commands even showed up on the screen.
Title: Re: Things that need fixing in the Engine
Post by: SoWN on Jan 31, 2006, 10:07 PM
i got hungup in pvp.. and am now ghosted for an extended period of time.  can't logon, says i am already logged on.
Title: Re: Things that need fixing in the Engine
Post by: ZLemur on Jan 31, 2006, 10:16 PM
Training doesn't charge any money
HP gain/level is nuts. (222hp @ lv5)
Monsters follow out of the arena
If the room below arena is supposed to spawn mobs...it's not.
Typing 'g' or 'get' followed by a space and a number will lock your input.
Closing a gate closes the gate on the opposite side you close it on. It remains open on your side.
Titles aren't changing. Still 'apprentice' at level 5
Exp to level is not increasing - always 1000 exp each level (human warrior)
AC is really bad...can't hit other players...even with 4 levels on em.
Heard a report that encumberance isn't affecting swings/movement etc.
'bash' works only to open doors. The attack version doesn't do anything.
When I (finally) killed proteus, he dropped a death pile. When I went up and looked at him, he was still fully clothed.
You may not hide items, only stash them.
Inviting someone to a party makes them follow by default (they don't need to 'fol <user>')
Not only does it auto-follow, if party members are in another room, they 'teleport' to the room the leader moves to. Being mortally wounded does not change this.
Can't disband a party or leave a party.
Can give stuff to NPCs (monsters)
When giving/stashing/dropping an item, items that are equipped go first, before loose items in your inventory.
Rolling via death is the same as typing reroll (less than 200 exp from testing the 'can i trail lv 11 here' thing. sigh.)
unable to 'set palet <n>'

more as I find em.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Jan 31, 2006, 10:45 PM
when pc and npcs walk in and out of the room.

It should be yellow for the name and green for the rest of the sentance.
Backstab damage is way high at level 1 I shouldn't be bsing for 71
steath doesn't seem to be working well way more fails then normal
same thing with hide but was able to bs while hiding.

TCA
Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Jan 31, 2006, 11:32 PM
Thanks for all the feedback everyone.  All that stuff will make fixing those bugs that much easier.  Will let it run for the night, just to see if it crashes.  Will work on fixes tomorrow night.
Title: Re: Things that need fixing in the Engine
Post by: ZLemur on Jan 31, 2006, 11:47 PM
Looks like crashage around 145am EST. Crap got rolled from dying too many times. Wasn't quite able to test training lv 11. So close it's irritating lol
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Jan 31, 2006, 11:53 PM
HP/Ma should be defaultly white not light blue

TCA
Title: Re: Things that need fixing in the Engine
Post by: ZLemur on Feb 01, 2006, 01:07 AM
Thats just an issue with 'set palet <n>' not being there yet. I'll add it to my above list.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 01, 2006, 01:33 AM
I figured that was a simple thing.


Title: Re: Things that need fixing in the Engine
Post by: proteus on Feb 01, 2006, 06:28 AM
Quote from: Psycho on Jan 31, 2006, 10:16 PM

When I (finally) killed proteus, he dropped a death pile. When I went up and looked at him, he was still fully clothed.


It should be mentioned that "proteus" at the time of his death, was not connected to the realm, and apparently, it still re-spawned me. Neat.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 01, 2006, 10:41 AM
I forgot to add in that I did manage to get a few backstabs in while sneaking. so it does work just fails too much even at level 1. The highest damage I saw doing bs was around 81 with a club.

TCA
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 01, 2006, 11:21 AM
I should really log on during one of these events.. :p

Wouldn't that be nice.

Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 01, 2006, 11:26 AM
grin I was wondering where you were both times..

TCA
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 01, 2006, 11:34 AM
The bar... :p  Well..i assume..what time is he generally starting this? 

Right now I'm in the process of creating a blank database so I can start putting stuff together for the realms content.  Maybe I'll have something for him by tonight :p

And maybe the game will just explode..who knows!
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 01, 2006, 11:38 AM
It looked like 9pm ish but I wasn't around when it started up yesterday.

TCA
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 01, 2006, 11:47 AM
oo..k So for my next trick... hurm..Ok so I'm making something for tonights bruhaha.  But wa we'll see.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 01, 2006, 11:53 AM
We still don't have any spells in there I don't know if that functions working yet but it could be tested if it was. I also posted about 2 pages of item discriptions too for you to make use of.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 01, 2006, 12:34 PM
one more thing you forgot to add the basic aid <user> command in.
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 01, 2006, 12:37 PM
No spells yet..well spells should work..but there are no ability tags..so there is no way to learn spells..
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 01, 2006, 12:53 PM
hmm what else could be tested.

the read command
mana regen could be if the spell just echoed a testing message for the cost of say 3 mana or something.

Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 01, 2006, 01:03 PM
Reading scrolls works, but casting spells needs a crap load of work.  Only healing spells work, but they give generic messages.

I'm about 50% finished fixing the combat model, so # of swings and crit % should be almost spot on by tonight.  I plan on fixing it so rerolling (or being rerolled) doesn't crash the board.  Tonight I will definitely also fix the HPs per level gain, and the exp / level (I swear I had it right at one point).  Depending on how much time I have left over I will start going down the list of the other miscellaneous issues people have posted in here.

I get home around 5pm pst, so look for it go up around 7-8pm or so.
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 01, 2006, 01:04 PM
there are not textblocks, so no read, nor speaky speaky.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 01, 2006, 01:11 PM
One more thing to check on I noticed that even after I had given a few things away I still had multiples of the object in my inventory. I'm not shure if this was just me missing someone giving me the same object and I would have checked this better but it crashed before I could finish testing it.

Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 01, 2006, 08:19 PM
Ok, it's back up.

Rerolling *should* work without crashing the realm.  HPs per level is fixed (sorry nottyger ;) ) and so is exp per level.  Caps should work in gossips and other communication.  # of swings should be spot on.
Title: Re: Things that need fixing in the Engine
Post by: Valentine on Feb 01, 2006, 08:23 PM
...and.....*stupid question alert*...how does one reroll, exactly?

See, this is why someone needs to show me how this freaking thing works...
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 01, 2006, 08:50 PM
one would type "reroll" and it would kill the character and any remaining lives.
Title: Re: Things that need fixing in the Engine
Post by: Valentine on Feb 01, 2006, 09:02 PM
Merci...someone should publish a gmud for dummies e-book. Ah well...most the commands I tried worked...I just couldn't talk much....maybe that was on purpose?

Since logs are being generated, perhaps a tag for users to put in whenever they encounter a bug would be useful...like just typing "bug" so there's an easy way for those in charge to find them.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 01, 2006, 09:04 PM
To talk in a room right now you have to put a "." in front of what you want to say.
or type gos "message" to gossip it.
Title: Re: Things that need fixing in the Engine
Post by: ZLemur on Feb 01, 2006, 09:05 PM
I'm pretty sure that's settable. It is in MMud. Should make it that way for gmud too.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 01, 2006, 09:06 PM
Right now it is forced. but in mmud you can type set talk fast or set talk slow.
Title: Re: Things that need fixing in the Engine
Post by: Valentine on Feb 01, 2006, 09:07 PM
Hmm...someone (DC) failed to mention the detail of the "." to me...instead being kind enough to advise me on the location of the Enter key.
Title: Re: Things that need fixing in the Engine
Post by: proteus on Feb 01, 2006, 09:44 PM
I wish metro's beta testing was like this.

Anyway.. good night.
Title: Re: Things that need fixing in the Engine
Post by: ZLemur on Feb 01, 2006, 11:03 PM
Keep posting your bugs - no matter if you've gossip'd them. I'm making a complete list.
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 02, 2006, 01:18 AM
ok my goal...an exp table
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 02, 2006, 01:20 AM
honestly...so yall know.. when im in the realm..i just wanna interact with the engine...stop attacking me...btw im immortal now.
Title: Re: Things that need fixing in the Engine
Post by: ZLemur on Feb 02, 2006, 01:54 AM
only reason I attacked you was my promise in the owl thread. I'm done, honest :p
Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 02, 2006, 07:35 PM
Sorry for the late notice.  I'm not going to be able to get the realm running tonight.  I will definitely have time to work on it tomorrow and should get it running by tomorrow night.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 02, 2006, 10:37 PM
well at least I didn't miss anything :)
Title: Re: Things that need fixing in the Engine
Post by: Faceless thing on Feb 03, 2006, 03:03 PM
I can't wait to see what it looks like missed the test other day  :o
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 03, 2006, 03:15 PM
I somehow doubt I'll be around for tonight run, but I hope it goes well.
Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 03, 2006, 08:52 PM
Ugh... ok, fixed rerolling again.  (third time's a charm?) Doors should close properly.

Spacing will be all messed up.  I fixed all that were obvious, but there will undoubtedly be extra line breaks.  A list of all the messages that suffer from this would be nice.  On the bright side, at least now all messages should show up instead of deleting themselves halfway through (couldn't notice it on my local machine).

I'm adding in the aid command right now.  What's the message given when you aid someone?  What does the person being aided see? 

Also going to let people kick off their account if they get ghosted.  Will be bringing it up after these quick changes.
Title: Re: Things that need fixing in the Engine
Post by: ZLemur on Feb 03, 2006, 09:04 PM
woah.
read the time wrong. nevermind.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 03, 2006, 09:15 PM
I can't remember what the text was for aid but I think it was something along the lines of:

room message:
<player> has aided <targets>'s wounds.
targets message:
<player> has aided you, your wounds have begun to heal.
players message:
You have aided <target>.

I don't know if this is exactly correct but it sounds ok to me.
Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 03, 2006, 09:18 PM
Ok, thanks.  I'll probably verify it before changing it.  I have something that resembles that loosely right now.

Server is up.  Aiming to keep it up all night... umm.... that doesn't sound right but oh well.
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 03, 2006, 09:43 PM
I need to know, arena type rooms on down path, or lair.
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 03, 2006, 10:10 PM
Exp:   52 k/hr
Cash:  0 copper/hr
Miss:  4%
Hit:   61%   Rng:16-49    Avg:32
Extra: 0%    Rng:0-0      Avg:0
Crit:  35%   Rng:98-224   Avg:159
BS:    ---   Rng:0-0      Avg:0
Pre:   N/A   Rng:0-0      Avg:0
Cast:  N/A   Rng:0-0      Avg:0
Round:       Rng:28-275   Avg:119
Sneak: 0%   
Dodge: 0%   

245988 years-245989 years to level.  ROFL. megamud even says that.
Title: Re: Things that need fixing in the Engine
Post by: proteus on Feb 03, 2006, 10:26 PM
Last names need some work. Currently you can add ascii (is that the term?) to them, and the length makes the top list funky of you use all the spaces. Top list can probably be spaced out more to accomodate, but the ascii might be a problem.

edit - scratch high ascii, it turns symbols into ? but it does allow the weird symbol from the delete key to be used in last names.

Also, rerolling your character while dropped puts your new character created right into the exact same place with the same number of negative hps.

And resting doesn't break when something attacks you.

Logging off via the menu doesn't actually end your session.

Characters are still showing up multiple times in the top list, for an unknown reason.

"set" does nothing that I can see.

Entering the realm after training generates a "User walks into the room from nowhere." message.

You can give items to yourself.
Title: Re: Things that need fixing in the Engine
Post by: proteus on Feb 03, 2006, 11:27 PM
Fun with parties - it gets its own post.

Inviting someone to a party still makes them auto-accept, no "invited" status. However, it no longer makes them automatically "physically" follow you.

Inviting someone, disconnecting completely from the realm, and logging back on does not make the invite go away.

When you invite someone, and then disconnect from the realm after they follow you, and they're still in the same room when you leave, if they don't move, they don't get kicked from the party until you reenter. This also generates a "User walks into the room from nowhere."? (from them) message when you reenter.

If they move, they get booted from the party.

If you invite someone and they accept, but then later are removed from the party by whatever means, you still have a party screen listing only yourself.

When you invite someone, and they accept, if they exit the game and sit in the menu screen, and you move, they see the movement, and inside the game, you see them following you. They are however still in the menu, and no longer actually in the party listing.

I could not seem to make "disband" work, and didn't test "leave". Hope this helps more than causes headaches.

"disband party" causes a pause in my connection, like a message is trying to be there but isn't being accessed.

There is no apparent party size limit, which may be intentional (good!). Multiple invites to the same person result in that person being listed in the party that many times.


As a related aside, it's also apparent that disconnecting from the realm/interface is not working right, or I should say, not working completely, which might explain some of the exiting/reentering bugs.
Title: Re: Things that need fixing in the Engine
Post by: Faceless thing on Feb 04, 2006, 12:08 AM
when u reroll u dont lose any of your gear its all still on person
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 04, 2006, 03:09 AM
rofl....when i was like 12 metro called my parents home and threatened to sue me because of a high ascii bug i used on there bbs...rofl..my dad made them refund the 240 bucks i had spent on time on their bbs....lesson...dont threaten a 12 year old if you dont have any proof.
Title: Re: Things that need fixing in the Engine
Post by: Valentine on Feb 04, 2006, 03:27 AM
Whatever, you are 12.

It's 4:27 on this side of town.
Title: Re: Things that need fixing in the Engine
Post by: proteus on Feb 04, 2006, 08:56 AM
heh, high ascii is the bane of everything.

Is the board up, or down? I'm connecting but not getting to the login screen.
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 04, 2006, 08:57 AM
it crashed around 4 am, blame thesifer.
Title: Re: Things that need fixing in the Engine
Post by: Core on Feb 04, 2006, 10:28 AM
Bad Thesifer, no donut!
Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 04, 2006, 02:17 PM
Ok, # of swings is working.  Accuracy is a lot closer (just need to find out how stats like str or agil affect it, if at all). Added a couple doors to the east and west.  Ascii characters above 126 aren't recognized now.

I turned off the word wrap function completely.  The good news is MegaMUD now shows messages properly in the convo window.  The bad news is words aren't wrapping.  I put together a client to show me how WG and Major MUD handle it and I'm baffled.  I don't see what's telling the next word to go to the next line.  Maybe there's a special IAC command I have to send in the initial handshaking when someone connects to make the client handle word wrapping? 

Anyway, realm is up.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 04, 2006, 02:40 PM
If I remember correctly most telnet clients can only handle 80 characters in width per line. So you might just have to force a line break after the 80th character including spaces. I'm not a programer though so I couldn't tell you how to go about doing that.

TCA
Title: Re: Things that need fixing in the Engine
Post by: ZLemur on Feb 04, 2006, 02:43 PM
What'd Thesifer do to crash the board?
Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 04, 2006, 02:45 PM
Quote from: The Crazy Animal on Feb 04, 2006, 02:40 PM
If I remember correctly most telnet clients can only hand 80 characters in width per line. So you might just have to force a line break after the 80th character including spaces. I'm not a programer though so I couldn't tell you how to go about doing that.

TCA
See, that's the thing. ?If I force a line break, Mega doesn't recognize the next line as a continuation of the line above. ?If I don't, the word isn't wrapped to the next line if it is too long to fit on the current line. ?I logged on to a real realm and with a custom client captured the actual bytes being sent from the server. ?I never would have guessed, but there don't appear to be any forced line breaks in the real thing as far as word wrapping goes, the words just seem to wrap magically.
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 04, 2006, 02:50 PM
ROFL..magical!
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 04, 2006, 03:16 PM
Well looking at the data files in mmud they used to be forced into 6 lines that were 56 characters long. I don't know if that might help a little. I'm not sure though how that would work with say talking and other communication text though.

TCA
Title: Re: Things that need fixing in the Engine
Post by: ZLemur on Feb 04, 2006, 03:56 PM
Quote from: DeathCow on Feb 04, 2006, 02:50 PM
ROFL..magical!

So...do we need a +2 magical keyboard to delete stuff or what?
Title: Re: Things that need fixing in the Engine
Post by: proteus on Feb 04, 2006, 09:56 PM
Quote from: Vitoc on Feb 04, 2006, 02:17 PM
Ok, # of swings is working.? Accuracy is a lot closer (just need to find out how stats like str or agil affect it, if at all). Added a couple doors to the east and west.? Ascii characters above 126 aren't recognized now.

east/west doors appear to be opening/closing correctly.

Coins have no weight.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 05, 2006, 11:49 AM
One thing that we were missing was the ability to lock doors after closing them. I don't know if you had put that in yet though.


Search bug: When in the room with an attacking creature you can't search. This should be can't search if you are engaging in combat not just being attacked.

Train stats mistake: It doesn't tell you when you don't have enough CPs to raise a stat.

Look bug: When looking at yourself it shouldn't tell you that you are looking at yourself.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 06, 2006, 01:55 AM
Give command: Lets you give items to yourself: should report: "Why would you want to give to that?"

Telepath: lets you send messages to yourself: should report: "Cannot find user!"
Title: Re: Things that need fixing in the Engine
Post by: Hurion on Feb 06, 2006, 03:12 AM
If you equip something, then sell it, it stays in your inventory untill you unequip it then it poofs. Tried it with longsword, club and quarterstaff. The command aa doesn't work (used to bash monsters and I think doors).
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 06, 2006, 10:09 AM
Search Direction: creates a slight pause but it should report on a fail, "You notice nothing different to the (direction). "above and below is used in place of up and down"

Searching (object, or NPC, Player): should report, "Why would you want to search that?"

Follow (NPC), should report: "Following a monster - Not implemented yet."

Invite (NPC). should report: "You don't see (NPC) here!"

par when not in a party should look like this:
You are not in a party at the present time.
? Abram X? ? ? ? ? ? ? ? ? ? ? ? (Warrior)? ? ? ? ? ? ?[H:100%]? ?- Midrank

The who list should be in alphabetical order.

Number of swings is still off:
A Level 12 neko missionary with 70 agil, 60 str at 490 enc with a longsword should be swinging straight 3s not 3,4,4,4,4,4....

Just noticed this when in the lower areana:

cage and myself were in there with 2 ho's.
cage died one of the ho's stopped swinging.
when cage returned the 2nd ho started swinging again.

Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 06, 2006, 08:59 PM
Ok.  Fixed a crashing issue.  Fixed first name starting with a capital letter, no spaces or numbers in a name now, length limitations (although I think I still have it too long).  Selling an item should now unequip the item properly.  That's it for the night.  Little by little... we're getting there.  I will be tackling the numerous issues with parties over this next week.  Thanks for everyone's patience and all the feedback.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 07, 2006, 11:48 AM
Got a strange error today:

[Telnet Error 00002745 (Receive)]
[Software caused connection abort.]
[Session ended (01:11 pm)]

I then went to log in about 30 minutes after and when putting my user name in got this:
That user is already logged in!

I think this is just being caused from normal old lag.
Title: About word wrapping...
Post by: interchange on Feb 07, 2006, 02:11 PM
I'm sure I can figure out their custom word wrapping so it works with megamud.

I'm 99% positive they're using cursor control to do a word wrap rather than sending a line feed character.

If you could dump the ascii characters to a file and open it up with a hex editor, you'll see the ASCII character codes.

I'm guessing it would be something like <ESC>[{ROW};0f to wrap to the next line.

You can also turn on line wrap <ESC>[7h ... but I'm not sure how exactly that works (wraps by words or wraps by character?).

Does it automatically detect settings for a different screen width, e.g. 100 columns?  I don't think there's a query for that.  You can query cursor position, so maybe there's a way to autodetect it.
Title: Re: Things that need fixing in the Engine
Post by: ZLemur on Feb 07, 2006, 04:50 PM
Not sure if this crash was me or scheduled...
I went to the first arena, tested the 'g xxx s' thing then the 'g #' thing. Neither crashed. I picked up some silver and copper and went to second arena. I was able to type 'g ' (that's "g <space>") and then it all ended there.
Title: Re: Things that need fixing in the Engine
Post by: proteus on Feb 07, 2006, 05:16 PM
I think I might have just crashed it by logging in. Unless someone else did something funky.

Are there any new abilities added in to muck around with?
Title: Re: Things that need fixing in the Engine
Post by: proteus on Feb 07, 2006, 05:39 PM
Training stats appears to be completely broken.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 07, 2006, 06:24 PM
I'm not sure if it was crashing but earlier I kept getting knocked off and was getting really bad lag.
Title: Re: Things that need fixing in the Engine
Post by: proteus on Feb 07, 2006, 07:20 PM
Add another one to the list, I don't remember seeing this anywhere before.


Monsters aren't healing.
Title: Re: Things that need fixing in the Engine
Post by: ZLemur on Feb 07, 2006, 07:37 PM
Consider it done.
Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 07, 2006, 09:03 PM
Quote from: proteus on Feb 07, 2006, 05:39 PM
Training stats appears to be completely broken.
This has been fixed now.
Title: Re: About word wrapping...
Post by: Vitoc on Feb 07, 2006, 09:10 PM
Quote from: interchange on Feb 07, 2006, 02:11 PM
I'm sure I can figure out their custom word wrapping so it works with megamud.

I'm 99% positive they're using cursor control to do a word wrap rather than sending a line feed character.

If you could dump the ascii characters to a file and open it up with a hex editor, you'll see the ASCII character codes.

I'm guessing it would be something like <ESC>[{ROW};0f to wrap to the next line.

You can also turn on line wrap <ESC>[7h ... but I'm not sure how exactly that works (wraps by words or wraps by character?).

Does it automatically detect settings for a different screen width, e.g. 100 columns?? I don't think there's a query for that.? You can query cursor position, so maybe there's a way to autodetect it.

Ok, here's a cap of what I'm seeing:
- aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Broadcast from Vitoc " aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
[HP=54/MA=32]:[HP=54/MA=32]:

Here's a cap of every byte received (the byte value is in parentheses, the actual character precedes it):
-(45) (32)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97) (32)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97) (32)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97) (32)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97) (32)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97) (32)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)
(13)
(10)(27)[(91)0(48);(59)3(51)7(55);(59)4(52)0(48)m(109)(27)[(91)7(55)9(57)D(68)(27)[(91)K(75)(27)[(91)1(49);(59)3(51)3(51)m(109)B(66)r(114)o(111)a(97)d(100)c(99)a(97)s(115)t(116) (32)f(102)r(114)o(111)m(109) (32)V(86)i(105)t(116)o(111)c(99) (32)"(34) (32)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97) (32)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97) (32)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97) (32)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97) (32)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97) (32)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)a(97)"(34)
(13)
(10)(27)[(91)7(55)9(57)D(68)(27)[(91)K(75)(27)[(91)0(48);(59)3(51)6(54)m(109)[(91)H(72)P(80)=(61)(27)[(91)1(49);(59)3(51)6(54)m(109)5(53)4(52)(27)[(91)0(48);(59)3(51)6(54)m(109)/(47)M(77)A(65)=(61)(27)[(91)1(49);(59)3(51)6(54)m(109)3(51)2(50)(27)[(91)0(48);(59)3(51)6(54)m(109)](93):(58)(27)[(91)7(55)9(57)D(68)(27)[(91)K(75)(27)[(91)0(48);(59)3(51)6(54)m(109)[(91)H(72)P(80)=(61)(27)[(91)1(49);(59)3(51)6(54)m(109)5(53)4(52)(27)[(91)0(48);(59)3(51)6(54)m(109)/(47)M(77)A(65)=(61)(27)[(91)1(49);(59)3(51)6(54)m(109)3(51)2(50)(27)[(91)0(48);(59)3(51)6(54)m(109)](93):(58)

I'm not seeing any ansi codes that move the cursor for word wrap in that lengthy broadcast.

Here's a listing of the initial handshaking:
?(255)?(251)(3)?(255)?(251)(1)?(255)?(251)A(65)u(117)t(116)o(111)-(45)s(115)e(101)n(110)s(115)i(105)n(110)g(103).(46).(46).(46)
(13)
(10)(1)(1)(1)(1)(1)(1)(1)(1)(1)(8)(8)(8)(8)(8)(8)(8)(8)(8)?(255)?(251)(3)?(255)?(252)(27)[(91)0(48)m(109)

Oh yeah, and yes, there is a way for the server to request the client's screen size in characters.
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 07, 2006, 09:23 PM
I could try to summon some more coder type peoples if you need more assistance..this one over my head.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 08, 2006, 08:45 AM
Heres a good one whats the handshake look like when connecting to worldgroups. I'm just curious how different it looks, It might yeild some answers.
Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 08, 2006, 09:22 AM
Quote from: The Crazy Animal on Feb 08, 2006, 08:45 AM
Heres a good one whats the handshake look like when connecting to worldgroups. I'm just curious how different it looks, It might yeild some answers.
Here's a listing of the initial handshaking:
?(255)?(251)(3)?(255)?(251)(1)?(255)?(251)A(65)u(117)t(116)o(111)-(45)s(115)e(101)n(110)s(115)i(105)n(110)g(103).(46).(46).(46)
(13)
(10)(1)(1)(1)(1)(1)(1)(1)(1)(1)(8)(8)(8)(8)(8)(8)(8)(8)(8)?(255)?(251)(3)?(255)?(252)(27)[(91)0(48)m(109)

That was from wg.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 08, 2006, 12:41 PM
Ok this might go past just the handshake. What standard did you code your terminal to emulate? I know that WG used ANSI, RIP and supported VT100/ANSI as well as straight ACCII mode.

I'm fairly sure that megamud uses VT100/ANSI because If I remember correctly it never shows ANSI art correctly which is commonly based on ANSI.sys emulation for MS-DOS. However, If you ever logged in to a WG system with procomm you'll remember that the ANSI art worked correctly.. This is because they are two different ANSI standards.

Now from what I understand line wrap is partialy handled by the client side and partialy handled by the host side. On the client side: Auto Wrap is done when a character extends past the max col set by the client program. On the host side: forced wrap is done by forcing a return, newline character, or by specifing the screen size. So the problem might really be not having the correct cursor control for megamud to understand whats going on.

Even though I understand a fair bit of this I'm unfortunatly not a programmer so I can't tell you how to fix it but I did some reasearch this morning to give you some more material to work with.

The other thing you might try is to build a decect terminal type in then you could have the core engine serve out the proper Ansi control codes.

VT100/ANSI terminal Control: - This is from the DEC terminal Family
http://www.graphcomp.com/info/specs/ansi_col.html
http://gershwin.ens.fr/vdaniel/Doc-Locale/Outils-Gnu-Linux/Kde/konsole/techref.html

ANSI Terminal Control, AKA - ANSI-BBS
http://enterprise.aacc.cc.md.us/~rhs/ansi.html
http://www.delmar.edu/Courses/CIS415L/ANSIsys.htm
http://bbs.ee.ntu.edu.tw/boards/Programming/17/13.html
http://www.bbsdocumentary.com/library/PROGRAMS/GRAPHICS/ANSI/

Host Command Summary:
http://www.wyse.com/products/winterm/quickstart/TermEm/wcn17ac.htm

General Terminal Info:
http://www.cs.utk.edu/~shuford/terminal/

You might be able to try posting to these news groups to get an answer:
comp.terminals
alt.folklore.computers

You could also look for ANSI x3.64 terminal emulation controls "ISO 6429??" which ANSI.SYS is based on.

Hope some of this might help.

TCA
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 08, 2006, 08:08 PM
 
  Here's the "That was from wg." post telnet-ized--

?(255)     IAC
?(251)     WILL
(3)     #3     SUPPRESS-GO-AHEAD
?(255)     IAC
?(251)     WILL
(1)     #1     ECHO
?(255)     IAC
?(251)     WILL
A(65)u(117)t(116)o(111)-(45)s(115)e(101)n(110)s(115)i(105)n(110)g(103).(46).(46).(46)(13)(10)
(1)(1)(1)(1)(1)(1)(1)(1)(1) (8) (8) (8) (8) (8) (8) (8) (8) (8)
?(255)     IAC
?(251)     WILL
(3)     #3
?(255)     IAC
?(252)     WON'T
(27)[(91)0(48)m(109)
 


Is that there's an instance where there's an "IAC" "WILL" followed by no option code
And another instance at the bottom that has "IAC" "WON'T" and no option code

I'm just posting this so i dont lose it, or forget about it after my night of drinking..I got a little more work i need to do..
Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 08, 2006, 09:11 PM
Quote from: DeathCow on Feb 08, 2006, 08:08 PM

? Here's the "That was from wg." post telnet-ized--

?(255)? ? ?IAC
?(251)? ? ?WILL
(3)? ? ?#3? ? ?SUPPRESS-GO-AHEAD
?(255)? ? ?IAC
?(251)? ? ?WILL
(1)? ? ?#1? ? ?ECHO
?(255)? ? ?IAC
?(251)? ? ?WILL
A(65)u(117)t(116)o(111)-(45)s(115)e(101)n(110)s(115)i(105)n(110)g(103).(46).(46).(46)(13)(10)
(1)(1)(1)(1)(1)(1)(1)(1)(1) (8) (8) (8) (8) (8) (8) (8) (8) (8)
?(255)? ? ?IAC
?(251)? ? ?WILL
(3)? ? ?#3
?(255)? ? ?IAC
?(252)? ? ?WON'T
(27)[(91)0(48)m(109)
?


Is that there's an instance where there's an "IAC" "WILL" followed by no option code
And another instance at the bottom that has "IAC" "WON'T" and no option code

I'm just posting this so i dont lose it, or forget about it after my night of drinking..I got a little more work i need to do..

FWIW the very first thing I do when someone connects to the server is send will SGA and will ECHO.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 08, 2006, 11:28 PM
Translation:
IAC, WILL, 3
IAC, WILL, 1
IAC, WILL, Send: "Auto-sensing..., CR LF, (9x) SOH, (9x) BS"
IAC, WILL, 3
IAC, WONT, ESC[0m

IAC, WILL, 3 Means:
The sender of this command requests permission to begin suppressing transmission of the TELNET GO AHEAD (GA) character when transmitting data characters, or the sender of this command confirms it will now begin suppressing transmission of GAs with transmitted data characters.

IAC, WILL, 1 Means:
The sender of this command REQUESTS to begin, or confirms that it will now begin, echoing data characters it receives over the TELNET connection back to the sender of the data characters.


NOTES:
IAC - Interpret as command
WILL - Starting preformance or now preforming
WONT - Denial of
3 - SUPPRESS-GO-AHEAD
1 - ECHO = Return Sent Characters to Sender
(13)(10) = CR LF Sequence - new line function
SOH - Start of Heading
BS - Backspace

Now the thing I find interesting is that I stil don't see any negotiates for screen size or terminal type...

More Usefull Stuff:
Ancii table codes 0 thru 127: http://www.lookuptables.com/
RFC Index: http://www.process.com/techsupport/pmdf/rfc/rfc-index.html
Telnet protocol: http://www.scit.wlv.ac.uk/~jphb/comms/telnet.html


Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 09, 2006, 02:31 AM
you guys only captured what WG sent, not what mega sent back.
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 09, 2006, 02:32 AM
mmud lets the client handle all of the word wrap..
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 09, 2006, 09:01 AM
Forgot to define a line: ESC[0m = Reset all previous text attributes

So what did mega send back?

What I'd expect to see is something like a set video mode in the start atleast, however; it is possible that WG & Megamud just assumes these standards or ignores the non-supported fuctions.

More ANSI sequences
http://www.robvanderwoude.com/index.html


Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 09, 2006, 11:55 AM
Ugh... after a couple hours of frustrating googling last night I came up with nothing.  Doing searches on telnet and iac commands results in a sea of RFCs and obsolete standards ranging from the very first terminal to the very latest.  99% of it is useless to me and finding that one page that spells it out for me has eluded me thus far.  Whatever the answer is I know I shouldn't be manually adding line feeds if the length is too long, because that's what was causing mega to cut off the messages last week.  I think I'm going to progress without word wrap for now and put that issue on the backburner.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 09, 2006, 01:45 PM
Can you tell me what terminal type megamud uses for its emulation?

TCA
Title: Re: Things that need fixing in the Engine
Post by: proteus on Feb 09, 2006, 04:54 PM
For whatever it's worth, I think the word wrap had an effect on the descriptions of things. Of course, I don't remember ever looking at anything before this issue came up, so I can't be sure. But descriptions look bad now.
Title: Re: Things that need fixing in the Engine
Post by: DeathCow on Feb 09, 2006, 05:44 PM
I talked to locke and he said

Locke: MajorMUD just spits out text, no fancy word wrapping at all. It lets the client handle that. It only sends a linefeed when the line is actually finished.

I tend to think he knows his stuff.
Title: Re: Things that need fixing in the Engine
Post by: Vitoc on Feb 09, 2006, 08:36 PM
Quote from: DeathCow on Feb 09, 2006, 05:44 PM
I talked to locke and he said

Locke: MajorMUD just spits out text, no fancy word wrapping at all. It lets the client handle that. It only sends a linefeed when the line is actually finished.

I tend to think he knows his stuff.
Then there must be something the server is telling the client to have it handle word wrapping, because mega in our realm isn't doing it.
Title: Re: Things that need fixing in the Engine
Post by: The Crazy Animal on Feb 09, 2006, 09:38 PM
Have you tried ansi codes to set the video mode to 80x25 color text.

<Esc>[=3h
<Esc>[=3l

From what I've read it might be sent in the handshake like
IAC,DO,ESC[=3h
IAC,DO,ESC[=3l

but i'm not the authority on this soo.

Assuming that megamud is emulating VT100 word wrap might need to be set with the set mode function:

Auto wrap to new line is:
ESC[?7h

Auto wrap off is:
ESC[?7l

might be worth a try, I'd find better info If I knew exactly what term emulation megacrud was doing..

Edit:

I just spotted this one too:

Set terminal to 80 column mode:
ESC[?3h

TCA