Quote:
"But blah blah this blah blah that, everyone is wrong but me" Whatever you may say, he seems passionate about getting whatever he is doing to work. So sit back, shut the fuck up and just watch and see where it goes, or help out. Maybe it won't go anywhere, but in all actuality it COULD go somewhere. So what, he may be wasting his time on this over something else. Luckily that's not for you to decide. |
Get back on subject please.
I realize noport has some weird fascination with clients that become outdated quickly. I also realize he doesn't really speak english, but when I have to come in threads to where people outright call him stupid though it's not okay. |
trevius I don't known how to tell you where correct i had my opcode in the wrong place i didn't want to listen to you because i thought i was right. I wasn't now i have to make new opcode notes 0/8 Chararters
I'm very sorry and i'll take it like a man and suck it up i apologize for getting mad at you. This was a great learning experince for me lesson learned from my mistake. |
My Post in English after being translated to Chinese and then back to English (using Google Translator):
noport, I know your intentions are good, I can tell you always try to help people. I have no problem with your attitude, there is no reason to apologize, I did. The only problem I am with you, I have a hard time understanding what you want to say almost every time you do post. In addition, I do not know that you understand that you are not completely answer. I know that English is not your primary language, I believe it is very difficult to express in their own language correctly, you are still learning. It is particularly complex, because you want to convey the information is very technical, I think the translation is not clear, because it may give you seem to. To all English-speaking people (not just me), it is difficult to understand what you posted about. I hope this post does not offend you, because this is not the intention. I just tried to explain that people have a difficult time, you're talking about. A recent example is that in this thread: http://www.eqemulator.org/forums/sho...253#post207253 Where you set up an operation code to solve the script / source code is not related to the machine code was to try. You did not even say which client operation code should be tried. I do not need a direct response to this case one of your posts. I just give one thing, I makes no sense to most recent example, perhaps it's significance. Almost all the jobs you do is very difficult for me to understand. Because it is, I still do not know you have been to do as the "Voice of America client compatibility, I have seen that your information is not consistent, as far as possible I can understand, for example, you say you have my server play on the Voice of America client, then a few posts above, you say you have the UF client eqgame.exe If this is the case, then you are actually playing We believe that the UF client, regardless of all of your other files Voice of America or not. I have seen the only thing you the refernce update source code is the opcode itself. Although the opcode is important, they are actually an easy thing to do we do now, especially if we have the opportunity to get that we are for customers EQLive collection efforts. May be the hardest part of a new client work is the structure of the packet, I can not think of any I've seen you refer to their time. In order to allow you to use the Voice of America client to log on to EQEmu complete, you will certainly need to adjust multiple data packet structure, encoding / decoding. Collected again from EQLive to make this process easier than trying to get an old client work, we do not have access to these packets to identify the structure (for example, when I started the special forces of the client placed in the first place). I'm sure I could probably get the Voice of America client to log on to perhaps an hour or in the character selection screen. As far as I can tell you, this is how far you have used from the Voice of America eqgame.exe can get. The most difficult part is to get all the way in the game, but the use of ridicule hot work has been completed, it may not be too hard, working too hard. After that, it will take a very long time to test each system and see what is working and what is not, and then fix everything opcode and packet structure, not the right to work. This is why I do not want to start Live / Voice of America customers until we have things will not change the main reason. Once the great work of the customers, because in hour t, on-site repair and if we want people to be able to use a fully patched client, we will start updating again. Do not make me wrong, although I think this is a great attempt, a new customer for EQEmu. I was the beginning of SOF placed in the first EQEmu past titanium. If not, we can almost certainly still be able to use the titanium today. I do not know anything about the operation code or packet structure, my first time can be, but I learned a lot, Denisov, superoxide dismutase (SOD), UF is now quite a lot of other developers such as Kowloon south help laughing at the (main). I live peristent, and kept working until I have real results, other developers can see the upgrade EQEmu past the actual potential of the titanium. This is basically how do I become a part of the development team in the first place. Therefore, for any progress can be made to new customers for EQEmu. I just do not want to "chase" them to do so, this will become a full-time work, to maintain EQEmu latest frequent changes. You might think that DEVS is too lazy or busy work in new customers, but is not the case. Yes, we are busy and may be lazy, but a new customer came along, there is a reliable source legally get it, it will not be repaired like Live monthly, and then we will begin to update it EQEmu (or at least I know). I definitely do not want anyone in any way work in EQEmu, detur. If you can submit the changes, you can get the Voice of America is working perfectly, then I believe we can add it to the source. If you are not willing to share your changes that you, as well. However, if you do not intend to share your changes, then I do not know why you would bother them to publish or find help our development staff and community to make it work here. Again, I mean any offense without this position. I just want to you and society, why EQEmu on DEVS work is not yet on the Voice of America customer side must be clear. However, I almost want to start working, so I can compare my results so far have been provided. I also hope it is clear, it is difficult to understand your position, even though they may make perfect sense to you. My original Post in Chinese after being translated from English (using Google Translator): noport, 我知道你的意图是好的,我可以告诉你总是试图帮助人们。我与你的态度有没有问题,没有理由你道 歉,我什么。 我与你的唯一的问题是,我有一个很难理解它是什么你想说的几乎每一次你做什么职位。另外,我不知道你明白你 是不是完全的答复。我知道英语不是你的主要语言,我相信这是很难正确表达自己的语言,你还在学习。它特别复 杂,因为你想传达的信息是非常技术性的,我觉得翻译不清晰的信息,因为它可能给你似乎。向所有讲英语的人( 不只是我),这是很难理解你所张贴有关。 我希望这个职位没有得罪你,因为这是不是我们的原意。我只是试图解释说,人有困难的时间后,你 在说什么。 最近的一个例子是,你在这个线程后: http://www.eqemulator.org/forums/sho...253#post207253 在那里,你建议设置一个操作码来解决脚本/源代码的问题是不相关的机器码在有人尝试。你还甚至没有说哪个客户端,操作码是应该受到审判。我不需要直接 响应这个例子您的文章之一。我只是给一个东西,我是没有意义的,最近的例子时,也许它的意义。几乎所有你做 的职位是我很难了解。 因为它是,我仍然不知道你一直在为“美国之音客户端兼容性做的事情。我已经看到你的信息是不是一致的,尽量 我可以理解。例如,你说你有我的服务器上播放美国之音客户端,那么上面这几个职位,你说你提出的用友客户端 eqgame.exe。如果是这样的话,那么你实际上是玩我们认为用友客户端,无论你的所有其他文件美国之 音或不。 我曾经见过你refernce更新源代码的唯一的事情是操作码本身。虽然操作码是重要的,他们实际上是一个 容易的事我们现在要做的,尤其是如果我们有机会得到我们正在努力为客户EQLive收集。可能得到一个新的 客户端工作中最难的部分是数据包的结构,我想不出任何我见过你引用它们的时间。为了让您能够使用美国之音客 户端登录到EQEmu完全,你肯定会需要调整多个数据包结构,编码/解码。再次收集,从EQLive使这个过程更容易比试图让一个旧的客户端工作的地方,我们并没有对这些数据 包的访问,找出结构(例如,当我开始对特种部队的客户端工作摆在首位) 。 我敢肯定,我大概可以得到美国之音客户端登录到也许一个小时或工作中的字符选择屏幕。至于我可以告诉大家, 这是多远,你已经使用从美国之音eqgame.exe,而能够得到。最困难的部分是能够得到所有的方式在游 戏中,但使用的嘲笑热已经完成的工作,它可能不会过于辛苦,工作压力太大。之后,它会花费很长的时间来测试 每一个系统,并看到什么是工作的,哪些不是,然后修复操作码和数据包结构的每一件事,不工作的权利。这是我 为什么不想要启动的Live /美国之音客户的工作,直到我们有东西是不会改变的主要原因。因为一旦把伟大的工作得到客户,因为我们在小时 吨,现场将修补和如果我们希望人们能够使用一个完全补丁的客户,我们便开始更新一遍。 不要让我错了,虽然我认为这是伟大的尝试,有新客户为EQEmu。我是一开始SOF工作摆在首位获得EQE mu过去钛。如果不,我们几乎可以肯定仍然可以使用钛今天。我不知道任何有关操作码或包结构,当我第一次开 始就可以了,但我学到了很多东西,索夫,超氧化物歧化酶(SOD),用友现在相当多的与其他开发商如九龙南 的帮助下,嘲笑(主要)。我住peristent,并不停地工作,直到我有真正的结果,其他开发者可以看到 升级EQEmu过去钛的实际潜力。这基本上是我如何成为摆在首位的开发团队的一部分。 因此,我对任何可以向新客户为EQEmu方面所取得的进展。我只是不希望“追”,他们这样做,这将成为一个 全职工作,保持EQEmu最新的频繁变动。你可能会认为DEVS是太懒惰或忙碌的工作在新的客户,但情况并 非如此。是的,我们都很忙,可能懒惰,但如果一个新的客户来到沿,有可靠的来源合法得到它,它不会像Liv e每月进行修补,然后我们将开始更新它EQEmu (或至少我知道)。 我绝对不希望任何人以任何方式在EQEmu工作detur。如果你能提交的变化,可以得到美国之音工作完美 ,那么我相信我们可以得到它添加到源。如果你是不是愿意分享你的变化,那是你的,以及。但是,如果你不打算 分享您的更改,然后我不知道你为什么会打扰他们在这里发布或寻找帮助我们的开发人员和社区,使 其工作。 再次,我的意思是没有这个职位的任何罪行。我只是想向你和社会,为什么EQEmu DEVS工作目前还没有对美国之音客户端要明确。不过,我几乎要开始工作,就这样我可以比较一下我的结果你 迄今已提供。我也希望它是明确的,这是很难理解你的职位,即使他们可能给你作出完美的感。 My original Post in English before any translation (using Google Translator): Noport, I know that your intentions are good, and I can tell that you are always trying to help people. I have no problems with your attitude and there is no reason for you to apologise to me for anything. My only problem with you is that I have a very hard time understanding what it is you are trying to say almost every time you make a post about anything. Also, I am not sure you understand everything you are reply to either completely. I know English isn't your primary language and I am sure it is hard to express yourself properly in a language that you are still learning. It is especially complicated because you are trying to convey information that is very technical, and I think the translation is not making your information as clear as it may seem to you. To all English speaking people (not just me), it is hard to understand what you are posting about. I hope that this post does not offend you, as that is not the intention. I am simply trying to explain that people have a hard time following what you are saying. One recent example is your post in this thread: http://www.eqemulator.org/forums/sho...253#post207253 There, you advised someone to try setting an opcode to resolve a scripting/source code issue that is not related to opcodes at all. You also did not even say which client that opcode was supposed to be tried for. I don't need a response directly about this example of one of your posts. I am just giving one recent example of something that makes no sense to me, when maybe it does make sense to you. Almost all posts you make are this hard for me to understand. As it is, I still don't know anything about what you have been doing for the VoA client compatibility. The information I have seen from you is not consistent as far as I can understand. For example, you say you have played on my server with the VoA client, then a few posts above this, you said you moved the eqgame.exe from the UF client. If that is the case, then you are actually playing on what we consider the UF client, whether all of your other files are from VoA or not. The only things I have ever seen you refernce in updating source code are the opcodes themselves. While opcodes are important, they are actually one of the easier things for us to do now, especially if we have access to get EQLive collects for the client we are working on. Probably the hardest part of getting a new client working are the packet structures, and I can't think of any time I have ever seen you reference them. In order for you to be able to use the VoA client to log completely into EQEmu, you will definitely need to adjust multiple packet structures and encodes/decodes. Again, having collects from EQLive makes this process considerably easier than trying to get an older client working where we don't have access to those packets to figure out the structures (such as when I started working on the SoF client in the first place). I am pretty sure that I could probably get the VoA client to log into the Character Select screen in maybe an hour or 2 of work. As far as I can tell, that is how far you have been able to get while using the eqgame.exe from VoA. The hard part is being able to get all of the way in-game, but using the work that Derision had already done for HoT, it probably wouldn't be overly hard to get that working too. After that, it would take a long time to test every system and see what is working and what is not and then fix opcodes and packet structures for each thing that isn't working right. That is the main reason why I don't even want to start working on a Live/VoA client until we have something that isn't going to change. Because as soon as we put in tons of hours to get a client working great, Live would patch and we would have to start updating it all again if we want people to be able to use a fully patched client. Don't get me wrong though, I think it is great to try to have newer clients for EQEmu. I was the one that started the work on SoF in the first place to get EQEmu past Titanium. If it wasn't for that, we would almost certainly still be using Titanium today. I didn't know anything about opcodes or packet structures when I first started on it, but I learned a lot and have done it quite a bit now with SoF, SoD, and UF, with the help of the other developers such as KLS and Derision (primarily). I stayed peristent and kept working at it until I had real results that the other devs could see actual potential in for upgrading EQEmu past Titanium. That is basically how I became part of the dev team in the first place. So, I am all for any progress that can be made toward newer clients for EQEmu. I just don't want to "chase Live" with the frequent changes that they do which would become a full time job to keep EQEmu up to date. You may think the Devs are just too lazy or busy to work on newer clients, but that is not the case. Yes, we are busy and probably lazy too, but if a new client came along that had a reliable source to get it legally and it wasn't going to be patched monthly like Live, then we would get started working on updating EQEmu for it (or at least I I know would). I would definitely not want to detur anyone from working on EQEmu in any way. If you are able to submit a change that can get VoA working perfectly, then I am sure we can get it added to the source. If you are not willing to share your changes, then that is up to you as well. But, if you aren't planning to share your changes, then I don't know why you would bother posting about them here or looking for help from our Devs and community to make it work. Again, I mean no offense in any of this post. I just want to be clear to you and to the community why the EQEmu Devs are not currently working on a VoA client. Though, I almost want to start working on one just so I can compare my results to what you have been providing so far. I also wanted it to be clear that it is hard to understand your posts even if they may make perfect sense to you. I made the 3 different versions of this post to show how everything does not always translate as it is intended. Though, Google Translator does a pretty damn good job! |
Well good news made it past Create a Character. How many Eq Emulator users would be interested in my precompiled server files Rev2103? Supports Clients listed below.
Code:
[02.18. - 00:00:00] [NET__IDENTIFY] Registered patch 6.2 |
It means we will have working VOA and HOT and will be able to build houses?
If yes i can't wait for it ! |
if its a fully working server then ya there might be people interested in a download to try out
|
He just got a character created, shit like houses dont code themselves. We still don't have features from Gates of Discord and before(expeditions, shared tasks, etc). Just connecting with a client doesnt make all the cool things of that client work.
|
Even if it was just logging in and playing with the VoA client, I would like to. Just so I can be playing on the latest client.
|
I'll keep you all updated i'm updating more opcodes at the same time trying to support others with there server settings. The more opcodes i have on Voa makes it a better client.
|
I spent a day working on VoA just to have something prepared in case Steam gets a new VoA client sometime soon.
I wrote a couple of scripts that make updating our patch_<expansion>.conf files a bit easier based on some other opcode info we have. It still requires some manual work to get all of the opcodes, but not nearly as much work as before. Here is the March 21 2012 client .conf file I made using these new scripts with a few adjustments I made manually while working on the client: Code:
# ShowEQ Import Notes: Code:
struct PlayerProfile_Struct Code:
static const uint32 MAX_PP_MEMSPELL = 12; Also, here are the character select struct changes that are required to see characters properly: Code:
struct CharacterSelectEntry_Struct { Other than that, I think the only other thing I had to do was add 37 bytes to the spawn struct and I was able to get all of the way in-game. Unfortunately, the game closes immediately after you completely zone in. I found a few other struct size changes that were required, but still haven't figured out what is causing the client to close. My best guess is that it is due to me setting the inventory opcode to 0x0000 to prevent the packet from crashing the client completely. Maybe if I can figure out the item struct changes it will work, but that is probably the biggest change required for Live clients to work and I don't think it will be easy due to how slots were changed around. I may work on it a bit more if I get time, but figured I would share the info I have so far in case anyone else wants to work on it. If Steam doesn't release a functional client that we can use for EQEmu, we will need some way for the community to get a compatible client legally. Maybe there is a way we can do an update every 6 months or so to work with Live clients, but that still leaves out anyone that tries to join between those times after a new patch is in place that breaks compatibility. I just don't want to have to do this type of thing every month as it takes quite a bit of time. At least with the new scripts I made, it should make filling in 90% of the opcodes much quicker. There may be a chance that Steam isn't getting a new client just because SOE knows that is where we have been getting our clients. If they were smart, they would just put a good VoA client on Steam and not a F2P HoT client or maybe the HoT client would be a different download to get just the patcher, since it still costs money to buy VoA (only up to HoT is free). Then, at least they would still make money off of EQEmu players vs forcing us to try to use Live patched clients which are free to everyone. If they want to stop EQEmu, there are much easier ways to do it, though I don't want to give them any ideas lol. I imagine they don't really care as much as you might think they would. So, hopefully EQ1 isn't on Steam right now just because Steam is always slow to get EQ client updates put up on their site. |
(Built Mar 21 2012 14:32:08)
Now have 0/10 characters you need too swap opcode like this OP_LogServer=0x5b0b with OP_GuildsList=0x1497 trevius Feel free take over Code:
|
VoA and HoT are using the same opcodes same client we can make opcode changes and have the latest client VoA. I have access to both HoT and VoA on sony
|
Noport, that is because HoT and VoA are the same client on Live. No matter what expansions you own or do not own, there is no difference in clients when you are fully patched to Live. If you are referring to the clients that are compatible with EQEmu, then HoT and VoA are 2 different build dates and use different opcodes and packet structures.
Anyway, I got the issue with it crashing out fixed. Now, the Live/VoA client can log in and quite a bit is functional, but there is still quite a bit that needs to be done to make it even playable. I will probably try to get what I have done up on the SVN soon and just comment out the patch registration for VoA until it is more finalized. That way, people can work on it or test it out in the meantime. |
Thank you trevius that sounds like a great plan
|
All times are GMT -4. The time now is 04:20 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.