OpenBOR

OpenBOR 4.0 4.0 Build 7735

No permission to download
Overview Updates (5) Reviews (8) History Discussion
I'm trying to make a "@cmd friendly" changeentityproperty that takes two parameters: "PropName" and "PropValue" and adds value the the property's current value.

example:
@cmd ModProperty "mp" 2
Click to expand...
would add 2 to the character's MP, but instead it's setting the character's MP to 2.
 
danno said:
@Ianyer The way the engine is assigned is different now, think of it as a much better and new way to create instead of an updated version, what you create with Unreal engine 4 is not going to be compatible with Unreal engine 5, so choose what version of the engine you want to use and stick with that.

I'm not going to look at OpenBor engine 4 until all my projects with OpenBor engine 3 are finished and if I do decide to create with OpenBor engine 4 I'll be starting from a bare bones new project.

Going forward try to consider that OpenBor engine 4 has nothing to do with OpenBor engine 3.
Click to expand...
Actually... alot of Unreal Engine 4 stuff is drop-in compatible with Unreal Engine 5. :) but what *is* missing is the fancy "convert UE4 project to UE5" thing that unreal engine also has.
 
devshark said:
Actually... alot of Unreal Engine 4 stuff is drop-in compatible with Unreal Engine 5. :) but what *is* missing is the fancy "convert UE4 project to UE5" thing that unreal engine also has.
Click to expand...

....and that's exactly how OpenBOR works. Which is why we used the Unreal/Unity example. Almost everything works the same in 4.0 as 3.0 and that's not changing.

The only difference is previously the community demanded absolute 100% backward compatibility across the board, and that's what we tried to do. Which frankly, is stupid. It's just not sustainable.

Now, the policy is we will try to maintain backward compatibility, but not as a dogma. If something has to changed to fix a bug or extend functionality, then so be it.

You know... just like every other engine.

DC
 
Can anybody help me out and test OpenBOR 4.0 - 7533 wii port is working: WII

I don't have a system I can test on right now.
 
  • Locking/Compiling - If OpenBOR has a flaw, it's that it is too open and too easy for its own good. I am working on a setup for creators to compile their game data into a closed form without resorting to third party tools. This should open the door for cretors interesed in professional work or projects with original content and cut back a bit (though never fully eliminate) the proilferation of "EXs", "XXXs", "super-ultimate-whatever" hacks from outside the community that have caused some of our best creators to depart.
Click to expand...

Has there been any update on this?
 
Aerisetta said:
Has there been any update on this?
Click to expand...

Not a lot to be honest. My graduate work went insane this semester, so I'm kind of on halt for major coding until early May. However, recently, our previous lead coder (@SX) returned to work on some Mac ports, and has also been modernizing the compiling process. One of the obstacles to a locking system was that the compiling tools were very much a black box. So while I haven't directly coded a lock system yet, part of the foundation work is being done as we speak.

DC
 
Aerisetta said:
Has there been any update on this?
Click to expand...
@DCurrent This sounds a lot like SecurePAK. Back in the day we had this functionality baked into limited runs when a OpenBOR creator wanted to lock down their resources because they either had heavily modified artwork or created artwork from scratch and did not want others to manipulate the resources.

I had then created an encrypted version of the PAK format which required a unique key in order to be able to unlock it and provided a custom version of OpenBOR. I had called this new PAK structure "SecurePAK" and the extension was "spk". BonusJZ was the only one who ever requested this from me and we agreed to unlock the SecurePAK after 1 year because even though it was heavily modified it was still based on Capcom/SNK derivatives.

An only 2 people have access to SecurePAK... myself and @DCurrent. @DCurrent has anyone used this feature since then? I would have to dig up the source code and tool which encrypts an existing PAK file if you need it. That's a good way to fund OpenBOR..... for creators that want their PAK files secured, you can offer this as service.... which will provide them a SecurePAK file and a variant of OpenBOR which supports it.

This is where the new build tools will shine.... you can automatically regenerate all targets for them.... Then they can take those targets and do as they wish (Sell them on Steam, etc....).... just make sure to put a disclaimer to protect yourself if in the future if the SecurePAK did get compromised.... just like anything else in this world.... nothing is 100% guaranteed.
 
Last edited:
SX said:
This sounds a lot like SecurePAK. Back in the day we had this functionality baked into limited runs when a OpenBOR creator wanted to lock down their resources because either 1 they heavily modified existing artwork or created artwork from scratch and did not want others to manipulate the resources.
Click to expand...

Oh good lord why did you say the name SecurePAK. Dude, I've fought more battles over that @#*@() thing since you left than you could possibly imagine. Just ask @Kratus and @O Ilusionista. Believe me, I know what it is and what it did - the problem is that nobody else does, nor do they believe me when I explain I don't have it and never did. Technically you left me access, but I didn't actually have a copy at any point, and AFAIK it stopped getting updates long before even you left. I can almost guarantee the peanut gallery will arrive in force now that you brought it up...

Besides that, I don't want to bring it back as it was, because it requires our intervention, which in turns requires judgement over what does and doesn't deserve to be secured. The only 100% fair way to do that is require 100% original content and IP.

Instead I'm looking into a way creators can encode and secure games on their own. That way I can wash my hands of any involvement.

DC
 
LOL....

Fair enough... I guess I never shared the code because I didn't want anyone to compromise future PAKS...

Then I guess the answer to that question is NO... OpenBOR has not have plans for locking down PAKS. However, you could still provide a service where you can sell that source code (If you want it, just let me know), fund this website and once a unified build system is in place they can manage it on their own.
 
SX said:
Then I guess the answer to that question is NO... OpenBOR has not have plans for locking down PAKS.
Click to expand...

I'd like to, I just want it to be independent of our (meaning staff) intervention. I was looking at a bit shift cypher of sorts salted from user generated passphrase, but there's obviously some technical hurdles to that.

DC
 
DCurrent said:
I'd like to, I just want it to be independent of our (meaning staff) intervention. I was looking at a bit shift cypher of sorts salted from user generated passphrase, but there's obviously some technical hurdles to that.

DC
Click to expand...
That's what it did originally.... but unless you employ an asynchronous encryption model (Public [read]/Private [write] Keys) it can always be hacked. Asynchronous encryption is the only REAL solution to ensure integrity and have the responsibilities fall under the creator. From a technical perspective it should be feasible, lock and sign the PAK and when read... openbor can unlock with public key and load into memory and work from there (minimizes performance it but makes it vulnerable to memory attacks) or (unlock the data being loaded per call (most secure but comes with a performance hit).

Here is a thought.... maybe I should start a service.... oh wait!!! I'm starting to remember how everyone wanted me to decrypt BonusJZ mod prior to the 1 year expiration.... it was a headache!
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom