Sorry for not posting any recent updates, I have been experiencing a little problem with loading rooms. Screen just goes black. Also, got school to worry about in a week or so means getting my things prepared.
Ok so, things haven't gone as planned recently... PC went out on me. Fortunately for me the store can replace it with replica + authentic parts (screen, and body) so it'll be in the shops for god knows how long and until then I'll have to refrain from working on this.
Other news (good):
Doing sum cool stuff n assembly so we'll see wut I come up wid
Back with more gangsta stuff, started working on this again and I'll post more in-game screenies soon.
Can't wait to do plugins/scripting though, which will be done later in development!
2 months and only one picture of the in-game client with an alert? GG m8
>already stopped
Development was active daily until school started? Which happens to be the only thing holding me back. The emulator itself I'd say is pretty much easy sailing from here. "already" is an understatement of the time and work I've put into this emulator if you're unaware of how much progress has been made.
>waste of time
Waste of who's time? How can you assume I don't have the time nor patience to work on an emulator when you're unaware of my schedule.
Let's skip the personal bullshit regarding what I do what my time, let's stay focused on code. Any comments on that? No? Cool.
@Quackster stalking my thread because some people just can't compete #IFeelTheEnvy #NegativeEnergyIsJealousy
Pardon the conflict.
Begun working on an emulator in C, still working on it atm.
As for Revolution, encountered a DI error while updating Guice dep. still working on running and testing out epolling on a Linux system so yeah :)
Gotta work on more packets, this will be done soon... when I get a to a stopping point with my C emulator I'll prioritize on what I shall work on more.
So you're saying that the Revolution Server is ended?
- - - Updated - - -
Observation.: I would not recommend to try to do an Emulator in C. C doesn't ever have strings. Doesn't ever is Object Oriented. Also you need do the Socket System from the scratch.
How you're thinking to code this?
Last edited by Taiga; 14-10-16 at 10:52 PM. Reason: Snip
Revolution Server is no where near ended, the development has just been going slower due to school, and other interests (C), so naw I'm still working on bits and pieces, I'll post an update log when I update the packet id's from January maybe I'll get some progress done after that.
I'll post a thread on the C emulator when it's far enough in development, right now I've been focused on getting the sockets in order then everything else comes after.
And to briefly answer your question, I'll code it "THE RIGHT WAY". Get it? The way people used to code before the OOP paradigm was introduced everything was either functional or procedural-- so it's definitely not impossible.
"THE RIGHT WAY" = What many programmers tell me how they program.
Last edited by Taiga; 14-10-16 at 10:56 PM.
Nobody has to understand this, right?
(more code here: https://github.com/jadenmitchell/Red...r/src/buffer.c)
I hope you know you can make a method returning a void, right?
A booleans value is always true or false => 1 or 0, so its size is always 1. ¯\_(ツ)_/¯
Last edited by pel; 15-10-16 at 11:41 PM.