I dont like that Death occurs at the moment.. and that the battle may not complete. So I made sure the code has it that in the end of a aggro update, it does a death update. So everyone can do a round.
Eliminates instant kills without fighting back. I like a round robin scheme.. and disagree with your event driven idea. If you are to understand that everything takes X amount of time and then the entire game is sliced into time then events happen in order as well. The laggier systems, means the base timeslice is slower. ack.. wife is pouting.. will maybe continue more later. ----- Original Message ----- From: "Davion Kalhen" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, November 16, 2004 3:54 PM Subject: ROM > Well, I figure this list has been quiet long enough! I might as well > start up a discussion. > > What do you people think are the major design flaws of ROM? What do > you think -should- be improved? > > > I've seen alot of codebases out there that are based off this > wonderful codebase, but almost all ove them have the same > fundimentals. A few things I don't like, is first off the Update > system. Its something I feel should be switched to an event-driven > system. The aggro check should not take up as much CPU as it does. I > even think Combat should be come event-driven. It could add really > neat features, like storing the etire battles data. How much damage to > each player, the skills/spells they used, the damage they caused. Such > info could add more stratagy to the game. > > Wait State. This thing bugs me, and I have stripped it from my > codebase. Event-que systems seem to work much nicer, and less > confusing for the player. It can add features such as RP commands only > lagging the input of other RP commands and not OOC, and such. This > isn't really a design flaw, its more of a preference. > > The way they load area's. I think Pfiles where done beautifully, but > area's are ridged little beggers, that don't like to be tampered with > :P. I think a pfile-like loading is much more idealistic for some > offline editing, and stability. > > Positions! POS_FIGHTING is the -biggest- problem with the positions. > Its prevents people from being tripped, bashed, knocked out cold, etc. > Just limits the system from doing some features that would be > interesting to see. > > > These comments are simply my opinion on ROM. What do you think about > the codebase and its flaws? > > Davion > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom > >
